

mantas
Members-
Content Count
4 -
Joined
-
Last visited
About mantas
-
Rank
Newbie
Recent Profile Visitors
154 profile views
-
Just to report, one funtoo system here (KDE desktop) succesfully updated to 1.3, big thanks to dev team for their hard work on Funtoo linux.
-
Can you updated only portage initially?
-
System update fails on the last package - gnome-base/dconf-0.30.1 with error: vala-0.42.3 is installed Don't know if 1.3 bugs should be already reported on bug tracker.
-
OK, so I am following upgrade instructions, so far so good. Currently updating system. A couple of points: I wanted to stay on perl 5.28 which was available some time ago from a kit, so had to unmask perl and ~20 perl virtuals, don't know if there is a file somewhere with such a list already Had to unmerge a number of xorg proto packages which had file collisions with one updated xorg proto package.
-
This was fixed by updating to recent ego
-
Well, apparently there are other issues:
-
Is is enough to set [global] release = 1.3 in ego.conf and resync to update to 1.3 or are there any steps or issues to pay attention to?
-
-
oh, didn't know that commands where moved
-
mantas started following ego 2.6 testing?
-
I got the same error, did you solve it? Thought maybe I should accept_keyword a newer boot-update as well, but core-kit is updated and 1.9.0 is the newest version there.
-
Slot conflicts when trying to upgrade portage
mantas replied to anaxamander's question in Portage Help
I think these -r1000 ebuilds are from progress overlay, which has been recently removed. They use different python variable (python_abis) than current ebuilds (python_targets) and it seems portage got lost between them. As suggested you could try to update packages giving troubles: emerge -av1 markdown2 pygments numpy setuptools If that doesn't work I would remove these packages, update portage and world and install them again if they would have not already be installed by world update. -
Yes, everytime.
-
You should post /var/log/Xorg.0.log, but, generally, did your run emerge @module-rebuild after building new kernel? Regarding the booting of other OS you should probably make new thread and post your /etc/boot.conf