# module-rebuild list ** Packages which I will emerge are: =x11-drivers/nvidia-drivers-1.0.8774 =x11-drivers/nvidia-drivers-1.0.9625 =x11-drivers/nvidia-drivers-1.0.9626 =app-emulation/vmware-modules-1.0.0.15-r1 =x11-drivers/nvidia-drivers-100.14.09 # equery list nvidia-drivers [ Searching for package 'nvidia-drivers' in all categories among: ] * installed packages [I--] [ ~] x11-drivers/nvidia-drivers-100.14.09 (0) # module-rebuild del =x11-drivers/nvidia-drivers-1.0.8774 ** =x11-drivers/nvidia-drivers-1.0.8774 not found in moduledb.
Another proof that storage format of linux-mod.eclass is bad. I suggest doing similar to vdr-plugin.eclass, and using one file for one package. That can then be installed by src_install, and gets under controll of portage.
ping, please change format of moduledb.
Still the same problem with =sys-kernel/module-rebuild-0.5: # module-rebuild list ** Packages which I will emerge are: =x11-drivers/nvidia-drivers-1.0.8774 =x11-drivers/nvidia-drivers-96.43.07 =media-video/gspcav1-20071224 # qlist -Iv nvidia-drivers x11-drivers/nvidia-drivers-96.43.07 # module-rebuild del =x11-drivers/nvidia-drivers-1.0.8774 ** =x11-drivers/nvidia-drivers-1.0.8774 not found in moduledb.
I don't think this requires a change of format, surely we just need to find and fix the bug in the code that removes an entry from the database? Or do you know more about this issue than I do?
And, as a FYI, this is "fixed" in portage-2.2, where the current existence of module-rebuild is replaced with: emerge @module-rebuild leaving this bug open until portage-2.2 is stable and we have released a transitionary module-rebuild package (or until we change the DB format or fix this bug otherwise)
Not a fix, just noting a lame workaround is to delete /var/lib/module-rebuild/moduledb and re-run "module-rebuild populate".
# Samuli Suominen <ssuominen@gentoo.org> (28 Dec 2013) # Replaced by 'emerge @module-rebuild' set in Portage itself. # Removal in 30 days, see http://bugs.gentoo.org/410739 sys-kernel/module-rebuild
