1 |
On Monday 22 Sep 2014 14:38:19 Alan McKinnon wrote: |
2 |
> On 22/09/2014 13:41, Nikos Chantziaras wrote: |
3 |
> > When I run: |
4 |
> > emerge -uDNl --with-bdeps=y @world |
5 |
> > |
6 |
> > I get this: |
7 |
> > WARNING: One or more updates/rebuilds have been skipped due to a |
8 |
> > dependency conflict: |
9 |
> > |
10 |
> > x11-base/xorg-server:0 |
11 |
> > |
12 |
> > (x11-base/xorg-server-1.16.0.901:0/1.16.0.901::gentoo, ebuild |
13 |
> > scheduled for merge) conflicts with |
14 |
> > |
15 |
> > x11-base/xorg-server:0/1.15.1= required by (x11-drivers/xf86- |
16 |
> > input-evdev-2.8.4:0/0::gentoo, installed) |
17 |
> > |
18 |
> > and xorg-server is not updated at all. I didn't even know that there's |
19 |
> > newer versions in portage. I'm on 1.15.1 and been running that for a |
20 |
> > |
21 |
> > long time now, but there's 1.15.2, 1.16.0 and 1.16.1 available. If I do: |
22 |
> > emerge -1 =xorg-server-1.16.1 |
23 |
> > |
24 |
> > then it works just fine and it gets updated. But with a @world update, |
25 |
> > nope. |
26 |
> > |
27 |
> > What's causing this? |
28 |
> |
29 |
> It gets stranger. I was getting the same results as you and did some |
30 |
> experiments running emerge -p and --backtrack. |
31 |
> |
32 |
> And suddenly, emerge -avuND world now works as expected. How's that for |
33 |
> non-deterministic? I can only assume those weird magic dynamic depends |
34 |
> are somehow involved and as such is worthy of a bug report. |
35 |
> |
36 |
> You can also resync as xorg-server-1.16.0.901 is now gone from the tree. |
37 |
|
38 |
Interesting! I also got this on an x86 box, except that the problem was not |
39 |
with xorg but with chromium. I'll try with --backtrace to see what I get. |
40 |
|
41 |
Thanks for the suggestion Alan. |
42 |
-- |
43 |
Regards, |
44 |
Mick |