emerge alsa-driver puts it in a wrong slot. It should have been 2.4.20. No idea where this 2.4.23-grsec-1.9.13 comes from No other kernel than 2.4.20 has ever been tried on this box. # 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) [ I] media-sound/alsa-driver-0.9.8 (2.4.20) [ ~I] media-sound/alsa-driver-1.0.0_rc1 (2.4.23-grsec-1.9.13)
I think this comes from the SLOT value being read in cache. And cache entries are those that comes in metadata when you rsync, meaning they have not been generated on your machine: /usr/portage/metadata/cache/media-sound/alsa-driver-1.0.0_rc1 A "touch" of the ebuild should be enough to force cache update. Anyway, you can also simply ignore this issue, because the SLOT value used by emerge will be correct whatever is in cache. See bug #30166 for a similar issue (this time with SLOT set to apache version and not kernel version).
"Anyway, you can also simply ignore this issue, because the SLOT value used by emerge will be correct whatever is in cache." Are you sure about that? I'd say emerge did use 2.4.23-grsec-1.9.13, which also means it did not unmerge version 0.9.8 which is still slotted in 2.4.20. It's no big deal to explicitely remove 0.9.8 but I do not want to check and do it every time alsa-driver gets an update and most users will be annoyed by that.
> Are you sure about that? Yes. But you can check your /var/db/pkg/media-sound/alsa-driver-1.0.0_rc1/SLOT to also convince yourself. I think that your 0.9.8 version has not been removed because it is in slot 0.9, which was the one used in before the move to $KV. (cf. the Changelog). Again, don't trust etcat for the slot of installed package, because he trusts the cache, which can differ from what is in the real db...
Not a bug.
