| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA512 |
| 3 |
|
| 4 |
On 20/09/15 19:41, Robin H. Johnson wrote: |
| 5 |
> On Fri, Sep 18, 2015 at 10:58:22AM +0200, Justin (jlec) wrote: |
| 6 |
>> Hello, |
| 7 |
>> |
| 8 |
>> there are quite a number of Manifest still not containing one or |
| 9 |
>> more of the three hashes. I would like to update them as far as |
| 10 |
>> we can download the sources. |
| 11 |
> 540 of 17841 Manifest files have the problem, about 3%. Quick way |
| 12 |
> to find them: find -name Manifest |xargs egrep -v '^DIST .* [0-9]+ |
| 13 |
> (SHA256|SHA512|WHIRLPOOL)' |cut -d: -f1|uniq |
| 14 |
> |
| 15 |
>> Procedure would be: 1. Download package 2. verify current hashes |
| 16 |
>> match 3. Calculate new 4. commit |
| 17 |
>> |
| 18 |
>> Following question need to be answered first: |
| 19 |
>> |
| 20 |
>> Does anybody have any general objections, remarks or ideas on |
| 21 |
>> that? |
| 22 |
> Good luck finding some of them; there are fetch-restricted packages |
| 23 |
> in that set. |
| 24 |
> |
| 25 |
|
| 26 |
yeah, I know. I will try what I can get and will put some information |
| 27 |
up on the remaining packages. When we have an overview, we can act. |
| 28 |
|
| 29 |
>> 2. Any suggestion how to do this? repoman has a manifest-check |
| 30 |
>> function but that is not functioning (bug filed). Any other tool |
| 31 |
>> around? Perhaps using pkgcheck? |
| 32 |
>> |
| 33 |
>> Ugly hack would be, tampering the downloaded sources and run |
| 34 |
>> repoman manifest which would redownload the tarball and check |
| 35 |
>> again. |
| 36 |
> I tested, and this worked: ebuild ... fetch ebuild ... manifest |
| 37 |
> tested with dev-scheme/hop/hop-2.0.1.ebuild. |
| 38 |
> |
| 39 |
> The distfile was downloaded, verified, and the Manifest got |
| 40 |
> updated correctly. |
| 41 |
|
| 42 |
thanks for confirming. I will do an extra check that the present |
| 43 |
sha256 sum didn't change. |
| 44 |
|
| 45 |
|
| 46 |
thanks for the comment, |
| 47 |
|
| 48 |
Justin |
| 49 |
-----BEGIN PGP SIGNATURE----- |
| 50 |
Version: GnuPG v2.0 |
| 51 |
|
| 52 |
iQJ8BAEBCgBmBQJV/vY1XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w |
| 53 |
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0QUU0N0I4NzFERUI0MTJFN0EyODE0NUFF |
| 54 |
OTQwMkE3OUIwMzUyOUEyAAoJEOlAKnmwNSmiZb8QAKhAGKo1gKZxILFyhU+Az5l3 |
| 55 |
VsJeJF6F0ZnclgUQSDKaqY06VxTjsG1W9SUDx0VYrqfJcSkIODZ55RjCio22f+tP |
| 56 |
6DA5z6sTwcBOcRIunWjjWD4rHrSgHj/HodzShFnTdSt8R6hzFumZWRaFXfN1DUj8 |
| 57 |
nibH3n1o6flAm8eV7ZxbypZ5Y1QOtFqxJc6fuHLeeSsJwu1iph/OnNagdx3ZCU29 |
| 58 |
RsiKxIjjWDLtew2BWCSSNTD7ORLNmogTis5xRAuQXevvwZ+wtXGhUNQmb9tlWkHW |
| 59 |
O0ndCVtH3+yiEPn+s+2TRbnYE0KE2Ce4vnGsmq1zuf0zzwXhKmgPNBLVihHU83nF |
| 60 |
M0bWPvqM7bdIGKZmdhfG4HOY0TE/9HZ7SHgr7u3OTgy+cqvouDoQf3XROKO9cgRQ |
| 61 |
iVMsNwjWJe4wZs5LAfgq0ancNZKHN0iorp0nDbE/cvkMUf5MkB/v3fz/C7XnYcFg |
| 62 |
54f7uluO2NQDv6852iGE4usYECQByHdZ+eU0ZPyPw/elrGbhaaBN+h4SBoVd6G4d |
| 63 |
vgpUTBCO1pVSZV2Rwx2AeDEin0An9r4+s2wHi0IXI/p0yQbLQ+rHCQpOpK72HrdH |
| 64 |
5O8dVr7zNiI96Qd5iN04Q0gNyTrmaSAevsNdhnLxouwlclKhtRY7tirlcEZQ7t4V |
| 65 |
Tlv5pykl8ITH9g5IS1yf |
| 66 |
=dwyV |
| 67 |
-----END PGP SIGNATURE----- |
Archives