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