On Fri, Sep 18, 2015 at 10:58:22AM +0200, Justin (jlec) wrote: > Hello, > > there are quite a number of Manifest still not containing one or more of the > three hashes. I would like to update them as far as we can download the > sources. 540 of 17841 Manifest files have the problem, about 3%. Quick way to find them: find -name Manifest |xargs egrep -v '^DIST .* [0-9]+ (SHA256|SHA512|WHIRLPOOL)' |cut -d: -f1|uniq
> Procedure would be: > 1. Download package > 2. verify current hashes match > 3. Calculate new > 4. commit > > Following question need to be answered first: > > Does anybody have any general objections, remarks or ideas on that? Good luck finding some of them; there are fetch-restricted packages in that set. > 2. > Any suggestion how to do this? repoman has a manifest-check function but that > is > not functioning (bug filed). Any other tool around? Perhaps using pkgcheck? > > Ugly hack would be, tampering the downloaded sources and run repoman manifest > which would redownload the tarball and check again. I tested, and this worked: ebuild ... fetch ebuild ... manifest tested with dev-scheme/hop/hop-2.0.1.ebuild. The distfile was downloaded, verified, and the Manifest got updated correctly. > 4. > What do you think is the best commit mode? PKG based, Cat based or repo based? repo-based means less commits, but I don't know if the portage changelog generation will handle it correctly. -- Robin Hugh Johnson Gentoo Linux: Developer, Infrastructure Lead E-Mail : robb...@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
