1 |
On Wed, Dec 21, 2016 at 2:20 PM, <Meino.Cramer@×××.de> wrote: |
2 |
> |
3 |
> 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 |
4 |
> |
5 |
> These are the packages that would be merged, in reverse order: |
6 |
> |
7 |
> Calculating dependencies... done! |
8 |
> [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 |
9 |
|
10 |
Hmm, do you have openrc in accept_keywords or something? You look |
11 |
like you're using stable keywords in general, but openrc is pulling in |
12 |
an unstable version. I suspect this is the root of your problem. |
13 |
|
14 |
> [nomerge ] sys-apps/openrc-0.23::gentoo [0.22.4::gentoo] USE="ncurses netifrc pam unicode -audit -debug -newnet (-prefix) (-selinux) -static-libs -tools" |
15 |
> [ebuild N ~] virtual/tmpfiles-0::gentoo 0 KiB |
16 |
> [nomerge ] virtual/tmpfiles-0::gentoo |
17 |
> [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)" |
18 |
|
19 |
So, openrc-0.23 is pulling in tmpfiles, which is pulling in systemd. |
20 |
Well, there you go, just unmerge openrc and you won't have it pulling |
21 |
in systemd any longer. |
22 |
|
23 |
JUST KIDDING!!! Don't do that... |
24 |
|
25 |
But, the first sentence is accurate. The problem is that you've |
26 |
unmasked openrc 0.23, but you probably haven't unmasked |
27 |
sys-apps/opentmpfiles. |
28 |
|
29 |
So, the solution is one of two things: |
30 |
|
31 |
Remove openrc from package.keywords and stay on 0.22.4. I'm not sure |
32 |
why you were running unstable openrc in the first place, so I'm not |
33 |
sure if this solution is acceptable to you. |
34 |
|
35 |
Or, add opentmpfiles to package.keywords so that it can be installed. |
36 |
Then portage should install that instead of systemd. The reason it is |
37 |
trying to pull in systemd is that opentmpfiles is masked, and systemd |
38 |
is stable, so it is going to go with the package that is stable. |
39 |
|
40 |
|
41 |
In general you're running into this issue because you're running mixed |
42 |
keywords. I do that, but keep in mind that this configuration is not |
43 |
tested for consistency by our internal QA tools, so you're going to |
44 |
sometimes run into issues like these. If you stick with all-stable or |
45 |
all-testing then you won't run into these kinds of inconsistences. |
46 |
Or, if you do that QA team that got mentioned in the other thread will |
47 |
probably have already sent a nasty-gram to the devs involved. :) |
48 |
|
49 |
|
50 |
> The following USE changes are necessary to proceed: |
51 |
> (see "package.use" in the portage(5) man page for more details) |
52 |
> # required by kde-plasma/kwin-5.8.3::gentoo |
53 |
> # required by kde-plasma/plasma-workspace-5.8.3-r4::gentoo |
54 |
> # required by net-p2p/ktorrent-5.0.1::gentoo[shutdown] |
55 |
> # required by @selected |
56 |
> # required by @world (argument) |
57 |
>>=media-libs/mesa-12.0.1 wayland |
58 |
|
59 |
|
60 |
I suggest ignoring this for the moment and see if the info above |
61 |
resolves your systemd issues. I'm not sure why kwin has the |
62 |
dependency that it does, but it looks to me like it is set up as a |
63 |
hard dependency that you can't avoid without modifying the ebuild. |
64 |
I'll see if I can figure out more. The changes above should at least |
65 |
get rid of whatever is pulling in systemd. |
66 |
|
67 |
Installing wayland shouldn't actually hurt anything. I noticed that I |
68 |
have it installed likely for the same reason, and it isn't like it |
69 |
will start running on its own. But, I'm not sure yet whether you can |
70 |
avoid it. |
71 |
|
72 |
-- |
73 |
Rich |