| 1 |
On Sunday 01 October 2006 02:23, David Relson wrote: |
| 2 |
> In the last few days I've been encountering lots of "Digest |
| 3 |
> verification failed" messages indicating SHA256 verification |
| 4 |
> problems (see below). |
| 5 |
> |
| 6 |
> Searching the web, I've found the "generate your own" digest solution, |
| 7 |
> i.e. "ebuild ...package...ebuild digest". Since the checksums are |
| 8 |
> present to ensure integrity, this seems like a bad idea. |
| 9 |
> |
| 10 |
> Is it a bad idea to generate my own digest values? |
| 11 |
|
| 12 |
Yes. There is now a section about it in the handbook [1]. |
| 13 |
|
| 14 |
> If so, what are the alternatives? |
| 15 |
[SNIP] |
| 16 |
> !!! Digest verification failed: |
| 17 |
> !!! /usr/portage/sys-devel/gettext/files/gettext-0.12.1-without_java.patch |
| 18 |
> !!! Reason: Failed on SHA256 verification |
| 19 |
> !!! Got: |
| 20 |
> 6dfefe191bc9435a957f7f6ff0658a771cf6ccffbaf169cae79ce7017a0421ee |
| 21 |
> !!! Expected: |
| 22 |
> c5a6a223c8be6ba11f1c180c7f381914abe127c0dffb0ec91d2e0a8e06892c92 |
| 23 |
|
| 24 |
Since the offending file is in the portage tree rather than in distfiles it |
| 25 |
doesn't make a lot of sense to delete it since only a sync will be able to |
| 26 |
refetch it anyway. Had it been in distfiles then Dales suggestions are correct. |
| 27 |
|
| 28 |
In this case, however, the problem isn't with the file rather it's with |
| 29 |
dev-util/pycrypto (which calculates the hash) [2]. And wow, that bug is really |
| 30 |
old by now! ;P The solution: |
| 31 |
|
| 32 |
# emerge -va1 =dev-python/pycrypto-2.0.1-r5 |
| 33 |
|
| 34 |
[1] http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=2&chap=1#doc_chap4 |
| 35 |
[2] http://bugs.gentoo.org/show_bug.cgi?id=131293 |
| 36 |
|
| 37 |
-- |
| 38 |
Bo Andresen |
Archives