| 1 |
On Sun, 14 May 2006 22:49:59 -0500, Harry Putnam wrote: |
| 2 |
|
| 3 |
> I've started an update after a couple of mnths of not keeping updated. |
| 4 |
> After emerge sync and installing latest portage I run: |
| 5 |
> emerge -v uDp world |
| 6 |
> I see this in the output... only showing a couple of dozens of lines |
| 7 |
> like this (wrapped for mail): |
| 8 |
> |
| 9 |
> [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking |
| 10 |
> x11-drivers/xf86-input-elographics-1.0.0.5) |
| 11 |
> |
| 12 |
> [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking |
| 13 |
> x11-proto/xproto-7.0.5) |
| 14 |
> |
| 15 |
> Ok ... so uninstall xorg-x11-6.9 right? |
| 16 |
|
| 17 |
Wrong, unmerge xorg-x11 |
| 18 |
|
| 19 |
> But wait, there is no xorg-x11-6.9 installed. My latest xorg stuff |
| 20 |
> is: |
| 21 |
> |
| 22 |
> xorg-x11-6.8.2-r6 |
| 23 |
> |
| 24 |
> So what gives...? any clues? |
| 25 |
|
| 26 |
Check further down the output and you'll see portage wants to update xorg |
| 27 |
to 6.9 as well, either because some package explicitly depended on |
| 28 |
xorg-6.x or because that is what currently satisfies virtual/x11. |
| 29 |
|
| 30 |
Unmerge xorg-x11, then run emerge -u world again. If it still shows |
| 31 |
these blockers, add --tree to see what is trying to pull in 6.x. |
| 32 |
|
| 33 |
BTW, use qukickpkg to build a binary package of xorg-x11 if you don't |
| 34 |
already have one. That way you can get X back quickly if something goes |
| 35 |
wrong. |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
Neil Bothwick |
| 40 |
|
| 41 |
When there's a will, I want to be in it. |
Archives