On my system I have # cat /var/db/pkg/media-video/nvidia-kernel-1.0.4363-r2/SLOT 2.4.20-yel-5 However when I do # emerge -pv nvidia-kernel These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild U ] media-video/nvidia-kernel-1.0.4349-r2 [1.0.4363-r2] I.e. the downgrade is shown as an upgrade. I would not be able to see that the nvidia-kernel package would be downgraded if I do an "emerge -pv world". Adding the -U option works around the problem, but this is not the expected behaviour anyway.
It is installed in a different slot.
Actually it's not... I have since upgraded my kernel, and here is the situation again: root@ols-yel linux # head -4 /usr/src/linux/Makefile VERSION = 2 PATCHLEVEL = 4 SUBLEVEL = 21 EXTRAVERSION = -yel-2 root@ols-yel linux # uname -r 2.4.21-yel-2 root@ols-yel linux # cat /var/db/pkg/media-video/nvidia-kernel-1.0.4363-r2/SLOT 2.4.21-yel-2 root@ols-yel linux # emerge -pv nvidia-kernel =media-video/nvidia-kernel-1.0.4349-r2 nvidia-kernel These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] media-video/nvidia-kernel-1.0.4363-r2 [ebuild U ] media-video/nvidia-kernel-1.0.4349-r2 [1.0.4363-r2] I hope I haven't overlooked what the slot of the "upgrade" would be, but it certainly says SLOT="${KV}" in both ebuilds.
Can you post the output of "etcat -v nvidia-kernel" ?
I don't have nvidia-kernel installed on any of my machines anymore, but here is the output on serveral of them anyway: $ for i in ols-yel ols-whi tiger lion; do echo "---- $i ----"; ssh $i 'uname -r; head -1 /usr/src/linux/include/linux/version.h; etcat -v nvidia-kernel'; done ---- ols-yel ---- 2.4.21-yel-4 #define UTS_RELEASE "2.4.21-yel-4" [ Results for search key : nvidia-kernel ] [ Applications found : 1 ] * media-video/nvidia-kernel : [ ] media-video/nvidia-kernel-1.0.2880-r1 (2.4.20) [ ] media-video/nvidia-kernel-1.0.2960-r1 (2.4.20) [ ] media-video/nvidia-kernel-1.0.3123-r2 (2.4.20) [M ] media-video/nvidia-kernel-1.0.4180 (2.4.20) [ ] media-video/nvidia-kernel-1.0.4191-r2 (2.4.20) [ ] media-video/nvidia-kernel-1.0.4349-r2 (2.4.20) [ ] media-video/nvidia-kernel-1.0.4363-r3 (2.4.20) [M~ ] media-video/nvidia-kernel-1.0.4496-r3 (2.4.20) ---- ols-whi ---- 2.4.20-whi-2 #define UTS_RELEASE "2.4.20-whi-2" [ Results for search key : nvidia-kernel ] [ Applications found : 1 ] * media-video/nvidia-kernel : [ ] media-video/nvidia-kernel-1.0.2880-r1 (2.4.20) [ ] media-video/nvidia-kernel-1.0.2960-r1 (2.4.20) [ ] media-video/nvidia-kernel-1.0.3123-r2 (2.4.20) [M ] media-video/nvidia-kernel-1.0.4180 (2.4.20) [ ] media-video/nvidia-kernel-1.0.4191-r2 (2.4.20) [ ] media-video/nvidia-kernel-1.0.4349-r2 (2.4.20) [ ] media-video/nvidia-kernel-1.0.4363-r3 (2.4.20) [M~ ] media-video/nvidia-kernel-1.0.4496-r3 (2.4.20) ---- tiger ---- 2.4.22-s2 #define UTS_RELEASE "2.4.22-s2" [ Results for search key : nvidia-kernel ] [ Applications found : 1 ] * media-video/nvidia-kernel : [ ] media-video/nvidia-kernel-1.0.2880-r1 (2.4.20) [ ] media-video/nvidia-kernel-1.0.2960-r1 (2.4.20) [ ] media-video/nvidia-kernel-1.0.3123-r2 (2.4.20) [M ] media-video/nvidia-kernel-1.0.4180 (2.4.20) [ ] media-video/nvidia-kernel-1.0.4191-r2 (2.4.20) [ ] media-video/nvidia-kernel-1.0.4349-r2 (2.4.20) [ ] media-video/nvidia-kernel-1.0.4363-r3 (2.4.20) [M~ ] media-video/nvidia-kernel-1.0.4496-r3 (2.4.20) ---- lion ---- 2.4.22-x1 #define UTS_RELEASE "2.4.22-x2" [ Results for search key : nvidia-kernel ] [ Applications found : 1 ] * media-video/nvidia-kernel : [ ] media-video/nvidia-kernel-1.0.2880-r1 (2.4.20) [ ] media-video/nvidia-kernel-1.0.2960-r1 (2.4.20) [ ] media-video/nvidia-kernel-1.0.3123-r2 (2.4.20) [M ] media-video/nvidia-kernel-1.0.4180 (2.4.20) [ ] media-video/nvidia-kernel-1.0.4191-r2 (2.4.20) [ ] media-video/nvidia-kernel-1.0.4349-r2 (2.4.20) [ ] media-video/nvidia-kernel-1.0.4363-r3 (2.4.20) [M~ ] media-video/nvidia-kernel-1.0.4496-r3 (2.4.20)
Same problem on my box, I think. the relevent line from: # emerge -Up world [ebuild U ] media-video/nvidia-kernel-1.0.4363-r3 [1.0.4496-r1] No "D". then from: # etcat -v nvidia-kernel [ Results for search key : nvidia-kernel ] [ Applications found : 1 ] * media-video/nvidia-kernel : [ ] media-video/nvidia-kernel-1.0.2880-r1 (2.4.20) [ ] media-video/nvidia-kernel-1.0.2960-r1 (2.4.20) [ ] media-video/nvidia-kernel-1.0.3123-r2 (2.4.20) [M ] media-video/nvidia-kernel-1.0.4180 (2.4.20) [ ] media-video/nvidia-kernel-1.0.4191-r2 (2.4.20) [ ] media-video/nvidia-kernel-1.0.4349-r2 (2.4.20) [ ] media-video/nvidia-kernel-1.0.4363-r3 (2.4.20) !!! aux_get(): ebuild for 'media-video/nvidia-kernel-1.0.4496-r1' does not exist at: !!! /usr/portage/media-video/nvidia-kernel/nvidia-kernel-1.0.4496-r1.ebuild !!! aux_get(): ebuild for 'media-video/nvidia-kernel-1.0.4496-r1' does not exist at: !!! /usr/portage/media-video/nvidia-kernel/nvidia-kernel-1.0.4496-r1.ebuild [M I] media-video/nvidia-kernel-1.0.4496-r1 (?) [M~ ] media-video/nvidia-kernel-1.0.4496-r3 (2.4.20) The (?) question mark might be because I re-installed nvidia-kernel after changing over to experimental kernel 2.6.0_beta4 (i couldn't resist taking it for a spin ;) and then re-installed nvidia-kernel again when I went back to 2.4.20. So maybe I confused it. Probably not the proper way of doing it, but it worked.
oops, wait, I'm running kernel 2.4.22 So disregard my speculation about the meaning of 2.4.20 and the question mark. It was apparently just silliness on my part. :-)
Problem identified. Who's gonna fix it? It seems that the problem lies in /var/cache/edb/dep. This is why for example I get: root@lion root # emerge sync .... root@lion root # etcat -v alsa-driver [ Results for search key : alsa-driver ] [ Applications found : 1 ] * media-sound/alsa-driver : [ ] media-sound/alsa-driver-0.5.12a (0.5) [ ] media-sound/alsa-driver-0.9.0_rc2 (0.9) [ ] media-sound/alsa-driver-0.9.2 (0.9) [ ] media-sound/alsa-driver-0.9.8 (2.4.20) [ ~ ] media-sound/alsa-driver-1.0.0_rc1 (2.4.23-grsec-1.9.13) [ ~I] media-sound/alsa-driver-1.0.0_rc2 (2.4.23-grsec-1.9.13) root@lion root # for i in /var/cache/edb/dep/media-sound/alsa-driver-*; do printf "%-25s %s\n" `basename $i` `head -3 < $i | tail -1`; done alsa-driver-0.5.12a 0.5 alsa-driver-0.9.0_rc2 0.9 alsa-driver-0.9.2 0.9 alsa-driver-0.9.8 2.4.20 alsa-driver-1.0.0_rc1 2.4.23-grsec-1.9.13 alsa-driver-1.0.0_rc2 2.4.23-grsec-1.9.13 root@lion root # rm -rf /var/cache/edb/dep/media-sound/alsa-driver-* root@lion root # etcat -v alsa-driver [ Results for search key : alsa-driver ] [ Applications found : 1 ] * media-sound/alsa-driver : [ ] media-sound/alsa-driver-0.5.12a (0.5) [ ] media-sound/alsa-driver-0.9.0_rc2 (0.9) [ ] media-sound/alsa-driver-0.9.2 (0.9) [ ] media-sound/alsa-driver-0.9.8 (2.4.23-x1) [ ~ ] media-sound/alsa-driver-1.0.0_rc1 (2.4.23-x1) [ ~I] media-sound/alsa-driver-1.0.0_rc2 (2.4.23-x1) root@lion root # for i in /var/cache/edb/dep/media-sound/alsa-driver-*; do printf "%-25s %s\n" `basename $i` `head -3 < $i | tail -1`; done alsa-driver-0.5.12a 0.5 alsa-driver-0.9.0_rc2 0.9 alsa-driver-0.9.2 0.9 alsa-driver-0.9.8 2.4.23-x1 alsa-driver-1.0.0_rc1 2.4.23-x1 alsa-driver-1.0.0_rc2 2.4.23-x1 It would be good if someone can give this bug a better subject.
*** This bug has been marked as a duplicate of 32367 ***
