These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] sys-boot/grub-0.97-r16::gentoo [0.97-r14::gentoo] USE="ncurses -custom-cflags -netboot -static" 1,034 KiB Total: 1 package (1 upgrade), Size of downloads: 1,034 KiB Would you like to merge these packages? [Yes/No] >>> Verifying ebuild manifests !!! A file listed in the Manifest could not be found: /usr/portage/sys-boot/grub/grub-0.97-r15.ebuild This has been visible for about 12h now.
*** Bug 567842 has been marked as a duplicate of this bug. ***
This is infra's problem; devs do not commit EBUILD entries in the Manifest. It seems to process to thinken the Manifest missed the rename here.
Yeah but why did that happen, for grub? usually it's due to another issue in the Manifest, that causes aborts.. my commits were done with repoman, they shouldn't've failed... :/
Seems I forgot to check the "reset assignee to default" box. Giving this to infra for real now.
For the record if anyone still has this issue the solution is below (brought from the gentoo forums) cd /usr/portage/sys-boot/grub rm Manifest ebuild grub-0.97-r16.ebuild digest
(In reply to Marius Stoica from comment #5) > For the record if anyone still has this issue the solution is below (brought > from the gentoo forums) > > cd /usr/portage/sys-boot/grub > rm Manifest > ebuild grub-0.97-r16.ebuild digest You don't even have to 'rm Manifest' , just 'ebuild grub-0.97-r16.ebuild digest' will suffice.
As of today, remains faulty still!
if you have a .git dir in the root of your portage repo, make sure you delete it. there were some broken syncs in the past which would cause updates to stall.
Still visible. "ebuild grub-0.97-r16.ebuild digest" workaround is ok.
This has been fixed on the official mirrors for many days now. If you did not get the fix, that means your client was not using --checksum. Portage's algorithm to thicken manifests uses the last mtime in a directory for the new mtime of the manifest. If an ebuild is REMOVED after the last addition, that means the manifest will have a DIFFERENT content, but the same mtime. Bug #567920 has a related case (renaming of ebuild).
