I think a piece might be missing from Portage. I'll depict my workflow as an example.
I'm preparing to upgrade: # emerge --sync # emerge -Dp world [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libXinerama-1.0.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libXi-1.0.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libXrandr-1.1.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/randrproto-1.1.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-misc/makedepend-1.0.0) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking media-libs/mesa-6.5-r3) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libdrm-2.0.1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/xf86vidmodeproto-2.2.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/glproto-1.4.7) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/xf86driproto-2.0.3) ... etc, lots of blockers ... Ok, let's try and find why it wants to downgrade to xorg-x11-6.9: # equery d xorg-x11-6.9 [ Searching for packages depending on xorg-x11-6.9... ] <none found> # Ok, no reason, apparently. Maybe it's already merged then? # emerge -C xorg-x11-6.9 --- Couldn't find 'xorg-x11-6.9' to unmerge. Nope. Now I'm getting uncertain. Don't I have xorg-x11 at all? # emerge -C xorg-x11 x11-base/xorg-x11 selected: 7.0-r1 protected: none omitted: none
'Selected' packages are slated for removal. 'Protected' and 'omitted' packages will not be removed.
Waiting 5 seconds before starting... (Control-C to abort)... Unmerging in: 5 4 3
<CTRL-C> Exiting on signal 2 Whoops. Yep, it's there. Ok, so status is that I have xorg-x11-7.0, I don't have 6.9, no packages actually wants xorg-x11-6.9, but whenever I use "emerge -D world", Portage sees it as a blocker anyway. Is there a piece missing in this puzzle, in particular the one that will tell me why on earth Portage thinks version 6.9 is a blocker? Or is the piece in place but I'm not looking hard enough? -- gentoo-dev@gentoo.org mailing list