| 1 |
On 22/09/2014 13:41, Nikos Chantziaras wrote: |
| 2 |
> When I run: |
| 3 |
> |
| 4 |
> emerge -uDNl --with-bdeps=y @world |
| 5 |
> |
| 6 |
> I get this: |
| 7 |
> |
| 8 |
> WARNING: One or more updates/rebuilds have been skipped due to a |
| 9 |
> dependency conflict: |
| 10 |
> |
| 11 |
> x11-base/xorg-server:0 |
| 12 |
> |
| 13 |
> (x11-base/xorg-server-1.16.0.901:0/1.16.0.901::gentoo, ebuild |
| 14 |
> scheduled for merge) conflicts with |
| 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 |
> long time now, but there's 1.15.2, 1.16.0 and 1.16.1 available. If I do: |
| 21 |
> |
| 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 |
|
| 30 |
It gets stranger. I was getting the same results as you and did some |
| 31 |
experiments running emerge -p and --backtrack. |
| 32 |
|
| 33 |
And suddenly, emerge -avuND world now works as expected. How's that for |
| 34 |
non-deterministic? I can only assume those weird magic dynamic depends |
| 35 |
are somehow involved and as such is worthy of a bug report. |
| 36 |
|
| 37 |
You can also resync as xorg-server-1.16.0.901 is now gone from the tree. |
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
Alan McKinnon |
| 42 |
alan.mckinnon@×××××.com |
Archives