After emerge --sync, using http://mirror.hamakor.org.il, and a few other mirrors as reported by users in http://forums.gentoo.org/viewtopic-t-370211-start-0- postdays-0-postorder-asc-highlight-.html, gcc's Manifest in the portage tree lists two files that are not in the tree. Namely, gcc-4.1.0_beta20050730.ebuild and files/digest-gcc-4.1.0_beta20050730 I have circumvented the problem temporarily by switching my rsync mirror, but I am unsure how many mirrors are out of date; it appears that only the manifest is out of date, the ebuilds listed are correct. Reproducible: Always Steps to Reproduce: 1. Using certain mirrors, certainly from rsync://rsync.namerica.gentoo.org/ gentoo-portage issue a emerge --sync 2. emerge gcc Actual Results: >>> emerge (16 of 98) sys-devel/gcc-3.4.3-r1 to / !!! Files listed in the manifest do not exist! gcc-4.1.0_beta20050730.ebuild files/digest-gcc-4.1.0_beta20050730 Expected Results: Expected results: Manifest should list all current hashes and files in the gcc branch, and even compile nicely :)
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" SERVER OUT OF DATE: rsync://147.91.8.58/gentoo-portage SERVER OUT OF DATE: rsync://194.97.4.250/gentoo-portage SERVER OUT OF DATE: rsync://134.147.32.57/gentoo-portage SERVER OUT OF DATE: rsync://140.105.134.102/gentoo-portage SERVER OUT OF DATE: rsync://82.129.5.25/gentoo-portage Hmm, almost impossible to emerge sync.... :(
*** Bug 102597 has been marked as a duplicate of this bug. ***
*** Bug 102570 has been marked as a duplicate of this bug. ***
libIDL suffers from a similar problem.
*** Bug 102609 has been marked as a duplicate of this bug. ***
*** Bug 102653 has been marked as a duplicate of this bug. ***
*** Bug 102684 has been marked as a duplicate of this bug. ***
*** Bug 102793 has been marked as a duplicate of this bug. ***
Just synced against rsync12.de.gentoo.org, my timestamp was Fri Aug 19 00:36:57 UTC 2005 then. Syncing against other rsync.de.gentoo.org said i was up to date. so i synced against rsync.gentoo.org (which was 134.68.220.97 in my case) and got a new timestamp: Fri Aug 19 09:06:45 UTC 2005
*** Bug 103067 has been marked as a duplicate of this bug. ***
Note to bug wranglers: While the original bug report related to gcc, there are a bunch of "duplicate" bugs attached to this one that relate to other packages; they are only duplicate in terms of being a digest mismatch. That means that just fixing the gcc issue is no longer sufficient to close this bug - the "duplicates" also need to be fixed. (Personally, I would have left them as separate bugs so that they could be closed as each individual case was fixed, thus avoiding confusion.)
(In reply to comment #11) > While the original bug report related to gcc, there are a bunch of "duplicate" > bugs attached to this one that relate to other packages; they are only duplicate > in terms of being a digest mismatch. That means that just fixing the gcc issue > is no longer sufficient to close this bug - the "duplicates" also need to be > fixed. This bug isn't gcc-specific anyway. All the manifests are perfectly fine in the main tree; it's the mirror problems that are causing people to end up with broken copies. When the mirrors are fixed, all the problems will go away simultaneously.
Is this still an issue? Our hosting provider for rsync1.us has upgraded a few machines in that rotation in the last week.
*** Bug 104352 has been marked as a duplicate of this bug. ***
(In reply to comment #13) > Is this still an issue? Our hosting provider for rsync1.us has upgraded a few > machines in that rotation in the last week. Unfortunately it still seems to be broken w/ some ebuilds (e.g. Bug 104352). :(
*** Bug 104528 has been marked as a duplicate of this bug. ***
Looks like this problem was solved when we added multiple machines to our rsync rotation. Re-open if this is still an issue, I have not heard any problems recently.
