When trying to emerge module-init-tools, the ebuild fails not finding any sources. Possibly all servers have moved to a new version? Reproducible: Always Steps to Reproduce: 1.emerge module-init-tools 2. 3. Actual Results: !!! Couldn't download module-init-tools-0.9.13-pre2.tar.bz2. Aborting. Expected Results: Install the latest version
They have been moved to an "old" directory, so just expand the path in the ebuilds to .../rusty/modules/old/${MYP}.tar.bz2
I suffered from the same problem. I was doing a clean install, and got halted to the point where I wanted to installed the mm-sources kernel. It wants to download module-init-tools-0.9.12.tar.bz2 among others, which gives me 404 not found on about the 6 or 7 servers it tries. Ah well, I'll try tonight again to emerge. You'd better got it fixed by then! ;-) Anyway - I really hope so :-)
Ok, cool.....looks like this is fine now
*** Bug 28939 has been marked as a duplicate of this bug. ***
Yep, it got moved to old/ as it was a prerelease and the final release came out. 0.9.14 is out [and in Portage] so you shouldn't have any problems with that. Resolving as such.