On Wed, Dec 21, 2016 at 2:20 PM, <meino.cra...@gmx.de> wrote:
>
> emerge -t --update --newuse --deep --with-bdeps=y --tree --keep-going
> --backtrack=30 --exclude media-video/nvidia-settings --exclude
> app-misc/screen --exclude app-misc/ytree --exclude dev-python/sip --exclude
> app-shells/bash @world -v
>
> These are the packages that would be merged, in reverse order:
>
> Calculating dependencies... done!
> [ebuild U ~] sys-apps/openrc-0.23::gentoo [0.22.4::gentoo] USE="ncurses
> netifrc pam unicode -audit -debug -newnet (-prefix) (-selinux) -static-libs
> -tools" 206 KiB
Hmm, do you have openrc in accept_keywords or something? You look
like you're using stable keywords in general, but openrc is pulling in
an unstable version. I suspect this is the root of your problem.
> [nomerge ] sys-apps/openrc-0.23::gentoo [0.22.4::gentoo] USE="ncurses
> netifrc pam unicode -audit -debug -newnet (-prefix) (-selinux) -static-libs
> -tools"
> [ebuild N ~] virtual/tmpfiles-0::gentoo 0 KiB
> [nomerge ] virtual/tmpfiles-0::gentoo
> [nomerge ] sys-apps/systemd-226-r2:0/2::gentoo USE="acl kdbus kmod
> lz4 pam seccomp ssl (-apparmor) -audit -build -cryptsetup -curl -elfutils
> -gcrypt -gnuefi -http -idn -importd -lzma -nat -policykit -qrcode (-selinux)
> -sysv-utils {-test} -vanilla -xkb" ABI_X86="(64) -32 (-x32)"
So, openrc-0.23 is pulling in tmpfiles, which is pulling in systemd.
Well, there you go, just unmerge openrc and you won't have it pulling
in systemd any longer.
JUST KIDDING!!! Don't do that...
But, the first sentence is accurate. The problem is that you've
unmasked openrc 0.23, but you probably haven't unmasked
sys-apps/opentmpfiles.
So, the solution is one of two things:
Remove openrc from package.keywords and stay on 0.22.4. I'm not sure
why you were running unstable openrc in the first place, so I'm not
sure if this solution is acceptable to you.
Or, add opentmpfiles to package.keywords so that it can be installed.
Then portage should install that instead of systemd. The reason it is
trying to pull in systemd is that opentmpfiles is masked, and systemd
is stable, so it is going to go with the package that is stable.
In general you're running into this issue because you're running mixed
keywords. I do that, but keep in mind that this configuration is not
tested for consistency by our internal QA tools, so you're going to
sometimes run into issues like these. If you stick with all-stable or
all-testing then you won't run into these kinds of inconsistences.
Or, if you do that QA team that got mentioned in the other thread will
probably have already sent a nasty-gram to the devs involved. :)
> The following USE changes are necessary to proceed:
> (see "package.use" in the portage(5) man page for more details)
> # required by kde-plasma/kwin-5.8.3::gentoo
> # required by kde-plasma/plasma-workspace-5.8.3-r4::gentoo
> # required by net-p2p/ktorrent-5.0.1::gentoo[shutdown]
> # required by @selected
> # required by @world (argument)
>>=media-libs/mesa-12.0.1 wayland
I suggest ignoring this for the moment and see if the info above
resolves your systemd issues. I'm not sure why kwin has the
dependency that it does, but it looks to me like it is set up as a
hard dependency that you can't avoid without modifying the ebuild.
I'll see if I can figure out more. The changes above should at least
get rid of whatever is pulling in systemd.
Installing wayland shouldn't actually hurt anything. I noticed that I
have it installed likely for the same reason, and it isn't like it
will start running on its own. But, I'm not sure yet whether you can
avoid it.
--
Rich
