mantas
-
Posts
4 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Posts posted by mantas
-
-
Can you updated only portage initially?
-
System update fails on the last package - gnome-base/dconf-0.30.1 with error:
QuoteNo installed vala in || ( dev-lang/vala:0.40 dev-lang/vala:0.38 dev-lang/vala:0.36 dev-lang/vala:0.34 dev-lang/vala:0.32 dev-lang/vala:0.30 dev-lang/vala:0.28 dev-lang/vala:0.26 )
vala-0.42.3 is installed
Don't know if 1.3 bugs should be already reported on bug tracker.
-
On 12/5/2018 at 7:09 AM, drobbins said:
Upgrade instructions are here:
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.
-
3 hours ago, mantas said:
Well, apparently there are other issues:
This was fixed by updating to recent ego
-
Well, apparently there are other issues:
QuoteWARNING: Could not find core-kit branch None; using default kit None instead.
ERROR: Fatal: branch cannot be None.
-
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?
-
5 hours ago, palica said:
since the commands from boot-update moved to ego you need to remove boot-update first.
oh, didn't know that commands where moved
-
On 2018-09-28 at 5:44 AM, savasten said:
I created a /etc/portage/package.accept_keywords file:
# ego
=app-admin/ego-2.6.0 **I tried to emerge and hit a hard block that I need to work through.
[ebuild U *] app-admin/ego-2.6.0::core-kit [2.4.2::core-kit] USE="-zsh-completion" PYTHON_SINGLE_TARGET="python3_6 -python3_4 -python3_5 -python3_7" PYTHON_TARGETS="python3_6 -python3_4 -python3_5 -python3_7" 158 KiB
[blocks B ] sys-boot/boot-update ("sys-boot/boot-update" is blocking app-admin/ego-2.6.0)Total: 1 package (1 upgrade), Size of downloads: 158 KiB
Conflict: 1 block (1 unsatisfied)* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.(sys-boot/boot-update-1.9.0:0/0::core-kit, installed) pulled in by
sys-boot/boot-update required by @selected(app-admin/ego-2.6.0:0/0::core-kit, ebuild scheduled for merge) pulled in by
app-admin/ego required by @system
ego
>=app-admin/ego-1.1.3-r3 required by (sys-apps/portage-2.3.47:0/0::core-kit, installed)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.
-
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.
-
Thanks i run emerge @module-rebuild and now it works with the nvidia driver, do i have to do that everytime a build a new kernel?
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

Testing 1.3
in General Discussion
Posted
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.