Users have started reporting geting 404 or file not found when emerging packadges. It seams some, and many, of the mirrors are broken. See the following tread http://forums.gentoo.org/viewtopic.php?p=452140 for details.
A list with files that were not found and when they were not found on which mirror would quite likely be helpful.
that's why I posted a link to the tread. I don't have the full list.
That's why I added the comment. Would be nice if some forum user (no, I am none) would collect such a list.
I was the one who originally posted the problem on forums.gentoo.org. I would love to give you a list of the servers not working with which files, but it would be an endless list. The only servers that actually had the packages that I was attempting to download were those hosted by KDE. Almost every package that I have attempted to emerge runs through the list of 100 servers without any luck. The error being given (ERROR 404: Not Found) is correct, as scanning the servers on my own proves that the packages are indeed not there. It seems that emerge sync is either giving me a list of files that does not apply to the standard mirrors, or that the mirrors (just about 100 of them) are not getting the updated files. I would love to help troubleshoot this problem, but I have finally (after a lot of manual package downloading) running an up to date system. As such emerge world doesn't give me any of the errors that would be helpfull to you. If there is anything I can do to help, please let me know.
- the list can't be endless since our list of source mirrors is definitely finite. :-) To find out which kind of files aren't there but should be there at least a filename, a date and a mirror (and the package which requires the file) would be helpful.
It may not be a problem with the mirror system at all. With each package, portage checks each mirror listed in GENTOO_MIRRORS for the package. If it is not found in any of the mirrors, it results to the SRC_URI listed in the ebuild script. This is generally the "source" location of the package, and in the case of KDE, would be kde.org. This happens often with packages that were recently added/updated to portage but have not been submitted to the mirror system yet, as the rsync (portage) mirrors are updated 8 times as often as the source mirrors due to the volume of the mirrors. Cheers! leaving this assigned for now, however with no other stats or data this can be resolved.
The only specific file mentioned in that entire thread is libid3tag. That ebuild is currently masked. Regardless, I was able to successfully download it using 'emerge -f libid3tag'. It is not on our mirrors at the moment, but it does download from the SRC_URI location. I have added that file to our mirrors so it should show up within the next ~24 hours or so. As for the other reported problems, without specific package names, we cannot reproduce this bug. For now, closing as cantfix. If someone can post specific package names, we will look at the issue further.
I recently fixed the autofetch script to correctly handle mirror:// and weird bashisms in SRC_URI. That means that any files that were missing that can still be fetched from the original location will be fetched into distfiles properly, whereas before many mirror:// cases would bork.
