Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


biocyberman last won the day on June 27 2017

biocyberman had the most liked content!

About biocyberman

  • Rank

Recent Profile Visitors

1,094 profile views
  1. I setup an overlay, and currently `#ego sync` does not update this overlay. I had to do manual git pull at the overlay's directory: cd /var/git/overlays/myov && git pulll origin master Is there a better way to achieve the same thing?
  2. This is working: 1. Downloaded the latest stage3 file of the same characteristics as the stage3 I used to install funtoo. 2. Create a dir: /root/2018stage3 3. Cd to the dir: cd /root/2018stag3/ and save the latest stage3 there. 4. Untar: tar xpf lateststage3.tag.xz. Waring for future readers: Untar the stage3 directly to root file system cause you to lose all customized files in /etc (including passwd, group) and also list of installed packages. Be careful not to make this mistake. 5. Follow the "Chroot into Funtoo" section in this guide: https://www.funtoo.org/In
  3. Yeah, it went like this: I feel stomachache. What's inside, why is it causing pain? Stab, grab, pull.... Hey I pulled off my gut, what do I do? I was also reading this https://wiki.gentoo.org/wiki/Fix_My_Gentoo and I am inclined to do follow it rather than the Funtoo's guide. This is a dead end: # cd /tmp # wget https://www.python.org/ftp/python/3.6.1/Python-3.6.1.tar.xz # tar -xJf Python-3.6.1.tar.xz # cd Python-3.6.1 # ./configure --enable-shared --with-fpectl --with-system-expat --with-system-ffi # make make is complaining that it can't find crt1.o file.
  4. More log: /usr/portage/distfiles # /tmp/portage-2.3.8/bin/emerge -1k glibc !!! Repository name or alias 'gentoo', defined for repository 'core-kit', overrides existing alias or repository. !!! Repository 'gentoo' is missing masters attribute in '/usr/portage/metadata/layout.conf' !!! Set 'masters = core-kit' in this file for future compatibility portage: 'portage' user or group missing. For the defaults, line 1 goes into passwd, and 2 into group. portage:x:250:250:portage:/var/tmp/portage:/bin/false portage::250:portage *** WARNING *** For security reasons, only
  5. Found the "wrong" version of glibc installed (version 2.26-r6) which does not have xlocale.h. I was ignorant to remove glibc because I did not see any way to downgrade to version 2.25-r11. Now portage does not work, all vital system commands stop working: id uid=1000 gid=1000 groups=1000,10,27,35,100,106,993,994 sudo su sudo: unknown uid 1000: who are you? wget from root terminal fails: /tmp/portage-2.3.8 # /tmp/portage-2.3.8/bin/emerge -1k sys-apps/portage !!! Repository name or alias 'gentoo', defined for repository 'core-kit', overrides existing alias or repository. !!! Reposit
  6. There were two other problems that I luckily could solved: First problem: no ebuilds to satisfy xyz This command emerge -auDN --newrepo @system complains something like "emerge: there are no ebuilds to satisfy "=x11-libs/gtk+-3.22*:3". This is very unexpected error to me. At first I download the ebuild file manually and put it in my local overlay. Then another error appeared for another package. Somehow I remember to add `--backtrack=50` option like this: emerge -auDN --newrepo @system --backtrack=50 This prevented some packages from being upgraded. Therefore it solved
  7. Well after x11-proto problem, I have many other problems with package conflicts. I took the opportunity to setup Funtoo 1.2 following Robbin's guide here: This did not solve the conflicts directly, but it gives an idea of working from the gcc up. I then have to manually unmerge or update some conflicts packages with `emerge -uv1 <packagenames>` For example, I have to upgrade many dev-qt packages and their downstream packages. I see this pattern: Package A is scheduled for merge with version A2. Package B which is installed wants package A version A1 (older than A2). Then th
  8. I found out that `app-editors/emacs-26.1_rc1:26/26::editors-kit` is asking to install `x11-base/xorg-proto-2018.4:0/0::xorg-kit`. I mask the two packages in `/etc/portage/package.mask`: =app-editors/emacs-26.1 >=x11-base/xorg-proto-2018.4 And then running emerge with `--autounmask-keep-masks` emerge -auDN @world --with-bdeps=y --autounmask-keep-masks This helped me to solve the problem and the emerge process could continue.
  9. After following instructions to migrate to meta-repo here: https://github.com/funtoo/meta-repo I did this command: emerge -auDN @world --with-bdeps=y --verbose-conflicts --backtrack=50 This brought up many conflicts and blocked package problems. I solved the conflicts packages by removing, manually upgrading. I am still stuck with the blocked packages as following. What do I do to get my system up to date? I have tried unmerge all blocking packages (i.e. x11-proto/*) and emerge x11-base/xorg-proto-2018.4. After that I re-ran the command above. I still get the same errors. T
  10. I am baffled. This happens after I switch to "meta-repo" from "ports-2012". I tried several packages, euse can't see packages flag. For example, the following is for xorg-server: # euse -p "x11-base/xorg-server" -E "xephyr" ERROR: USE flag "xephyr" does not exist # equery u xorg-server [ Legend : U - final flag setting for installation] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE f
  11. Found it! The trick is "# emerge -auDN --newrepo @world". The '--newrepo' option is crucial. Update 19 Oct 2017: The command above works for more than 1000 packages I have installed, except the qt* packages. For these stubborn qt* packages I had to do the following: emerge -Cav "dev-qt/qt*" * This action can remove important packages! In order to be safer, use * `emerge -pv --depclean <atom>` to check for reverse dependencies before * removing packages.
  12. I asked about a problem with upgrade to meta repo here: I got most of the things to work now, but the following issue of ebuild source conflicts keeps bugging me: # emerge -av "=dev-qt/qtwebengine-5.9.2:5/5.9::kde-kit" "=dev-qt/qtgui-5.9.2:5/5.9::kde-kit" "=dev-qt/qtwidgets-5.9.2:5/5.9::kde-kit" !3940 Password: !!! Repository 'x-portage' is missing masters attribute in '/usr/local/portage/metadata/layout.conf' !!! Se
  13. Holy cow, I have a local version of dev-libs/glib-2.50.3-r1. Moved that out of place and the update could start. Wonder why I created the most challenging upgrade for myself. Lesson learned: When there is a conflict, check , really check where it comes from. I was assuming that both gdbus-codegen and dev-libs/glib come from the same repo, but later found out that dev-libs/glib comes from another repo.
  14. @Oleg: Thanks for the pointer. It solved the problem with pythong_tagrgets. However, I came to another problem: version conflict between dev-util/gdbus-codegen-2.50.3 and dev-libs/glib-2.50.3-r1: # emerge -av "dev-libs/glib"
  15. Ok found this one and reading: http://forums.funtoo.org/topic/1176-how-to-migrate-from-ports-2012-to-meta-repo/ Still can't find the answer to "what should I do with stage3 files?" Running this: emerge -auDN @world --with-bdeps=y --verbose-conflicts --backtrack=30 gives error messages for one package after another: These are the packages that would be merged, in order: Calculating dependencies / !!! Problem resolving dependencies for sys-apps/file from @system ... done! !!! The ebuild select
  • Create New...