~ # cat /var/tmp/portage/dev-libs/libgaminggear-0.11.1/temp/build.log !!! Fetched file: libgaminggear-0.11.1.tar.bz2 VERIFY FAILED! !!! Reason: Insufficient data for checksum verification !!! Got: !!! Expected: MD5 RMD160 SHA1 SHA256 SHA512 WHIRLPOOL * Fetch failed for 'dev-libs/libgaminggear-0.11.1', Log file: * '/var/tmp/portage/dev-libs/libgaminggear-0.11.1/temp/build.log' ~ # cat /usr/portage/dev-libs/libgaminggear/Manifest DIST libgaminggear-0.10.1.tar.bz2 101415 SHA256 1e2626a81b41b74f26ac422c19cdafe858aeb2a572e53c0b2212064e69f14254 SHA512 60f30e1b05c31fb6072f5bd74d7edcd2039fe632c18183e122625bf5f16563e77599e22fc4926e7e6c43d985b3d8840ba9e5cc16b6cb8fb0986c9d49244b3e7c WHIRLPOOL 75e4759d0a2895f7bec0c17a490fbd2c2880fb575e8cdea116d229bab51e747db158c3a90bfb111bebf74bf650438b4c97463ea890592b3984eb77b934dc511e
Fixed with the go ahead from hwoarang on IRC
Oh thanks a ton Brian, was just about to fix it but you're faster. Apologise for the mistake, it seems repoman full doesn't check manifests...
(In reply to Dmitry Pisklov from comment #2) > Oh thanks a ton Brian, was just about to fix it but you're faster. > Apologise for the mistake, it seems repoman full doesn't check manifests... I'll disagree on that one: (Before the commit) grknight@akame /usr/portage/dev-libs/libgaminggear $ repoman full RepoMan scours the neighborhood... digest.missing [fatal] 1 /usr/portage/dev-libs/libgaminggear::libgaminggear-0.11.1.tar.bz2 Note: use --include-dev (-d) to check dependencies for 'dev' profiles Please fix these important QA issues first. RepoMan sez: "Make your QA payment on time and you'll never see the likes of me."
OK stupid question then... Does repoman check main portage or the one you're running it in? My git repo for portage is not my main portage tree, so I ran it from that directory... And it said everything is great. Now I'm thinking if it just checked main portage tree?..
repoman did the right thing. It was our (yours and mine) mistake because commit a21411140a64ca2e06e341985312b61fcbfecd2c only committed the ebuild and not the manifest file. So you had generated the correct manifest of that file but you didn't make it part of the git patch ie you forgot to do 'git add Manifest'