Sometimes, you want to emerge a Package from the unstable tree - Portage doesn't allow that, and that is Ok. But if you emerge an ebuild from unstable tree manually and then run an "emerge -pu world" portage reports the packages you just updated manually from unstable tree and wants to downgrade them. I think this has to be fixed. Example : the NVidia drivers; I updated them because of a better support for my GF4TI by manually emerging the ebuild. But since I "only" have the stable tree enabled, Portage now wants to downgrade them: <code> Calculating world dependencies ...done!<br> [ebuild UD] media-video/nvidia-kernel-1.0.3123-r2 [1.0.4191-r1]<br> [ebuild UD] media-video/nvidia-glx-1.0.3123 [1.0.4191-r0]<br> </code> Just an idea - but I think more users have this "problem" Greetings Benjamin "beejay" Judas
Actually, not only have I just experienced the same thing, this time it wasn't even limited to manual merging. I did an 'emerge --update world'. Later, I did an 'emerge rsync', followed by 'emerge --pretend --update world'. This is what it was planning on upgradig (pay particular attention to the currently installed versions between the brackets on the right): These are the packages that I would merge, in order: Calculating system dependencies ...done! [ebuild UD] sys-libs/glibc-2.3.1-r2 [2.3.1-r3] [ebuild UD] sys-devel/binutils-2.13.90.0.16 [2.13.90.0.16-r1] [ebuild UD] net-misc/rsync-2.5.6_pre20021105 [2.5.6_pre20021105-r1] [ebuild UD] sys-apps/groff-1.18-r3 [1.18.1-r0] [ebuild UD] sys-devel/bin86-0.16.0 [0.16.10-r0] (Actually, man-pages was in that list as well at first, but I specifically did an 'emerge --update man-pages', since that was the only one in the list actually offering an UP-grade. What's going on, here? As far as these packages are concerned, I haven't done anything with manual merging recently, as far as I can recall.
*** This bug has been marked as a duplicate of 9379 ***
