I had the ati-drivers installed, which until recently had been in the media-video category. They recently got moved to x11-drivers (and the apps to x11-apps). Unfortunately this left them in the module-rebuild list twice because the media-video versions were never unmerged, and module-rebuild didn't detect the moves/updates from portage. I'm not entirely certain how portage handles moves (although I've seen the move resolution system in action at the end of a sync), and I'm sure it will be difficult to implement, but at the moment module-rebuild stops on packages it can't find so I would call this a bug. Reproducible: Always Steps to Reproduce: 1. Wait for a driver to get moved/renamed in portage and updated. 2. Update world (so that the new package is inserted and the old one not removed) 3. Try to module-rebuild rebuild. Actual Results: It fails unable to find the old (moved) driver. Expected Results: Not had the old (moved) driver listed, or at the very least built the remaining drivers and then a large message saying it failed on certain packages. This bug is being posted from a machine other than the one that exhibited the problem. If the emerge info is necessary, please ask for it and I'll be happy to post it from the original machine.
About the only thing I can do with this is remove it from the moduledb if the package doesnt exist in portage anymore (this will include moves) and flag a warning about it. would this solve your issues?
*** Bug 112639 has been marked as a duplicate of this bug. ***
Hi, sorry I forgot to get back to you. Yep, this would cure it easily in the short term, and for the long term fix, I can't think of a way to could do it. Actually, would it be possible to maintain the list in /etc/portage, and thus have portage update it automatically? I haven't checked portage's update routines, but if they change *all* files in there, perhaps we could abuse this. Unfortunately it would be abuse, since the system was never designed to do that, but perhaps getting ferringb to check it'd be ok? Then we could go for that (assuming it all works)? Does that sound reasonable?
I cant see of anyway to safely use the updates tbh. I'll have to mull over this and check it out when I come back from my holidays!
I also noticed this problem: # module-rebuild list ** Packages which I will emerge are: =net-wireless/madwifi-driver-0.1485.20060325 =net-wireless/madwifi-ng-0.1502.20060414 ...when madwifi-driver was renamed to madwifi-ng. I had to delete madwifi-driver manually.
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
Is this fixed in 0.7?
Please try 0.7, thank you.
# 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
