I put my own ebuild of hardened-sources into the tree, not making changes to Manifest. # emerge -f --digest hardened-sources * * The --digest option can prevent corruption from being noticed. The * `repoman manifest` command is the preferred way to generate manifests * and it is capable of doing an entire repository or category at once. * Calculating dependencies... done! >>> Fetching (1 of 1) sys-kernel/hardened-sources-3.9.2 !!! A file is not listed in the Manifest: '/usr/portage/sys-kernel/hardened-sources/hardened-sources-3.9.2.ebuild' >>> Failed to emerge sys-kernel/hardened-sources-3.9.2 But when I omit '-f', the process continues, as expected. '-f' is faultily uncooperative here. Reproducible: Always
This should fix it: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=a40bb0e8bf595d5f014b80b19d14ba52801f84bc
This patch has no effect for me. Adding FEATURES="digest" doesn't help either.
+/- "parallel-fetch" makes no difference.
Yeah, that first patch is irrelevant. This one should really fix it: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=0d22dd6b813c4b7b49b1109ce332778e0e4cfc28
Still not quite it. I rollback'd the first patch and applied the second one. # emerge -f --digest hardened-sources * * The --digest option can prevent corruption from being noticed. The * `repoman manifest` command is the preferred way to generate manifests * and it is capable of doing an entire repository or category at once. * Calculating dependencies... done! >>> Fetching (1 of 1) sys-kernel/hardened-sources-3.9.2 >>> Creating Manifest for /usr/portage/sys-kernel/hardened-sources digest.assumed 46 hardened-sources-2.6.32-r143::deblob-2.6.32 hardened-sources-2.6.32-r143::deblob-check-2.6.32 hardened-sources-2.6.32-r143::genpatches-2.6.32-48.base.tar.xz (...) hardened-sources-3.8.8::genpatches-3.8-9.base.tar.xz hardened-sources-3.8.8::hardened-patches-3.8.8-1.extras.tar.bz2 hardened-sources-3.8.8::linux-3.8.tar.xz # emerge stops there. By the way, I have FEATURES="-digest", yet emerge re-creates the Manifest. Is that intended? I'd welcome the possibility to control that with the FEATURE. Not a big deal, though. P.S.: The Manifest is re-created now; my ebuild is present in it. When I run 'emerge -f --digest hardened-sources' again, the process looks exactly as before in this comment. This is a bit of an obstacle too. The new Manifest doesn't have a GPG signature.
(In reply to comment #5) > P.S.: The Manifest is re-created now; my ebuild is present in it. When I run > 'emerge -f --digest hardened-sources' again, the process looks exactly as > before in this comment. This is a bit of an obstacle too. The new Manifest > doesn't have a GPG signature. Now I --sync'ed. I have a Manifest with a signature again now. When I manually add into it entries for my ebuild and its distfiles, emerge works without a complaint even without '--digest', despite the GPG signature being wrong. I don't know if that's a problem and I suppose I don't have the signing key laying around somewhere in the tree. Just FYI.
(In reply to comment #5) > Still not quite it. I rollback'd the first patch and applied the second one. > > # emerge -f --digest hardened-sources > * > * The --digest option can prevent corruption from being noticed. The > * `repoman manifest` command is the preferred way to generate manifests > * and it is capable of doing an entire repository or category at once. > * > Calculating dependencies... done! > > >>> Fetching (1 of 1) sys-kernel/hardened-sources-3.9.2 > >>> Creating Manifest for /usr/portage/sys-kernel/hardened-sources > digest.assumed 46 > hardened-sources-2.6.32-r143::deblob-2.6.32 > hardened-sources-2.6.32-r143::deblob-check-2.6.32 > hardened-sources-2.6.32-r143::genpatches-2.6.32-48.base.tar.xz > (...) > hardened-sources-3.8.8::genpatches-3.8-9.base.tar.xz > hardened-sources-3.8.8::hardened-patches-3.8.8-1.extras.tar.bz2 > hardened-sources-3.8.8::linux-3.8.tar.xz > # > > emerge stops there. That looks normal. Your files are fetched, right? > By the way, I have FEATURES="-digest", yet emerge re-creates the Manifest. > Is that intended? I'd welcome the possibility to control that with the > FEATURE. Not a big deal, though. The emerge --digest option temporarily enables FEATURES=digest. That's just how it works. > P.S.: The Manifest is re-created now; my ebuild is present in it. When I run > 'emerge -f --digest hardened-sources' again, the process looks exactly as > before in this comment. This is a bit of an obstacle too. The new Manifest > doesn't have a GPG signature. Well, it's normal for the GPG signature to disappear when you re-generate the Manifest. It's harmless, because emerge doesn't check the signatures. (In reply to comment #6) > Now I --sync'ed. I have a Manifest with a signature again now. When I > manually add into it entries for my ebuild and its distfiles, emerge works > without a complaint even without '--digest', despite the GPG signature being > wrong. I don't know if that's a problem and I suppose I don't have the > signing key laying around somewhere in the tree. Just FYI. It's harmless, because emerge doesn't check the signatures.
(In reply to comment #7) > (In reply to comment #5) > > Still not quite it. I rollback'd the first patch and applied the second one. > > > > # emerge -f --digest hardened-sources > > * > > * The --digest option can prevent corruption from being noticed. The > > * `repoman manifest` command is the preferred way to generate manifests > > * and it is capable of doing an entire repository or category at once. > > * > > Calculating dependencies... done! > > > > >>> Fetching (1 of 1) sys-kernel/hardened-sources-3.9.2 > > >>> Creating Manifest for /usr/portage/sys-kernel/hardened-sources > > digest.assumed 46 > > hardened-sources-2.6.32-r143::deblob-2.6.32 > > hardened-sources-2.6.32-r143::deblob-check-2.6.32 > > hardened-sources-2.6.32-r143::genpatches-2.6.32-48.base.tar.xz > > (...) > > hardened-sources-3.8.8::genpatches-3.8-9.base.tar.xz > > hardened-sources-3.8.8::hardened-patches-3.8.8-1.extras.tar.bz2 > > hardened-sources-3.8.8::linux-3.8.tar.xz > > # > > > > emerge stops there. > > That looks normal. Your files are fetched, right? Ah, you're right. Thank you for the fix.
This is fixed in 2.1.12.1 and 2.2.0_alpha176.
