[gentoo-user] Digest verification failed!

[gentoo-user] Digest verification failed!

[Michael Sullivan]

A long time ago I was having problems with mailman.  I posted a question
to this list and someone told me that I would have to change the MAILGID
in the ebuild to whatever the gid of daemon was.  Back then I did that
and re-emerged mailman and everything worked.  Now I'm facing a similar
situation, but I can't apply the same solution because of portage
security.  I opened the ebuild for mailman and changed the MAILGID
variable.  I then attempted to re-emerge mailman, but I got this error:

bullet files # emerge mailman
Calculating dependencies ...done!
>>> emerge (1 of 1) net-mail/mailman-2.1.5-r4 to /
>>> md5 files   ;-) mailman-2.1.6_beta1-r1.ebuild
>>> md5 files   ;-) mailman-2.1.5-r2.ebuild
>>> md5 files   ;-) mailman-2.1.5-r3.ebuild

!!! Digest verification Failed:
!!!    /usr/portage/net-mail/mailman/mailman-2.1.5-r4.ebuild
!!! Reason: Filesize does not match recorded size

>>> Please ensure you have sync'd properly. Please try 'emerge sync' and
>>> optionally examine the file(s) for corruption. A sync will fix most
cases.


I can't figure out how to get past it.  I am syncing my portage tree as
I type this, but I don't see how it will help since I meant to change
the value of that variable.  Any hints?

-- 
gentoo-user@gentoo.org mailing list

RE: [gentoo-user] Digest verification failed!

[Dave Nebinger]

> I can't figure out how to get past it.

After changing the ebuild, type "ebuild mailman-xxx.ebuild digest".  This
fixes the digest values.

You should then be able to emerge mailman w/o resync.


-- 
gentoo-user@gentoo.org mailing list

RE: [gentoo-user] Digest verification failed!

[Nick Rout]

On Mon, 2005-10-03 at 14:29 -0400, Dave Nebinger wrote:
> > I can't figure out how to get past it.
> 
> After changing the ebuild, type "ebuild mailman-xxx.ebuild digest".  This
> fixes the digest values.
> 
> You should then be able to emerge mailman w/o resync.
> 
> 

or type emerge --digest mailman


-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Digest verification failed:

[David Relson]

Greetings,

In the last few days I've been encountering lots of "Digest
verification failed" messages indicating SHA256 verification
problems (see below).

Searching the web, I've found the "generate your own" digest solution,
i.e.  "ebuild ...package...ebuild digest".  Since the checksums are
present to ensure integrity, this seems like a bad idea.

Is it a bad idea to generate my own digest values?

If so, what are the alternatives?

Thanks.

David

... emerge gettext

 Calculating dependencies ... done!

>>> Emerging (1 of 1) sys-devel/gettext-0.15 to /
>>> Downloading
>>> 'http://distfiles.gentoo.org/distfiles/gettext-0.15.tar.gz'
--20:18:41--  http://distfiles.gentoo.org/distfiles/gettext-0.15.tar.gz
           => `/usr/portage/distfiles/gettext-0.15.tar.gz'
Resolving distfiles.gentoo.org... 216.165.129.135, 156.56.247.195,
64.50.238.52, ... Connecting to
distfiles.gentoo.org|216.165.129.135|:80... connected. 
HTTP request sent, awaiting response... 200 
OK Length: 8,081,941 (7.7M)
[application/x-gzip]

100%[====================================>] 8,081,941    142.51K/s
ETA 00:00

20:19:36 (144.45 KB/s) - `/usr/portage/distfiles/gettext-0.15.tar.gz'
saved [8081941/8081941]

 * checking ebuild checksums ;-) ... [ ok ]
 * checking auxfile checksums ;-) ... [ !! ]

!!! Digest verification failed:
!!! /usr/portage/sys-devel/gettext/files/gettext-0.12.1-without_java.patch
!!! Reason: Failed on SHA256 verification
!!! Got:
6dfefe191bc9435a957f7f6ff0658a771cf6ccffbaf169cae79ce7017a0421ee 
!!! Expected:
c5a6a223c8be6ba11f1c180c7f381914abe127c0dffb0ec91d2e0a8e06892c92
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Digest verification failed:

[Dale]

David Relson wrote:
> Greetings,
>
> In the last few days I've been encountering lots of "Digest
> verification failed" messages indicating SHA256 verification
> problems (see below).
>
> Searching the web, I've found the "generate your own" digest solution,
> i.e.  "ebuild ...package...ebuild digest".  Since the checksums are
> present to ensure integrity, this seems like a bad idea.
>
> Is it a bad idea to generate my own digest values?
>
> If so, what are the alternatives?
>
> Thanks.
>
> David
>
> ... emerge gettext
>
>  Calculating dependencies ... done!
>
>   
>>>> Emerging (1 of 1) sys-devel/gettext-0.15 to /
>>>> Downloading
>>>> 'http://distfiles.gentoo.org/distfiles/gettext-0.15.tar.gz'
>>>>         
> --20:18:41--  http://distfiles.gentoo.org/distfiles/gettext-0.15.tar.gz
>            => `/usr/portage/distfiles/gettext-0.15.tar.gz'
> Resolving distfiles.gentoo.org... 216.165.129.135, 156.56.247.195,
> 64.50.238.52, ... Connecting to
> distfiles.gentoo.org|216.165.129.135|:80... connected. 
> HTTP request sent, awaiting response... 200 
> OK Length: 8,081,941 (7.7M)
> [application/x-gzip]
>
> 100%[====================================>] 8,081,941    142.51K/s
> ETA 00:00
>
> 20:19:36 (144.45 KB/s) - `/usr/portage/distfiles/gettext-0.15.tar.gz'
> saved [8081941/8081941]
>
>  * checking ebuild checksums ;-) ... [ ok ]
>  * checking auxfile checksums ;-) ... [ !! ]
>
> !!! Digest verification failed:
> !!! /usr/portage/sys-devel/gettext/files/gettext-0.12.1-without_java.patch
> !!! Reason: Failed on SHA256 verification
> !!! Got:
> 6dfefe191bc9435a957f7f6ff0658a771cf6ccffbaf169cae79ce7017a0421ee 
> !!! Expected:
> c5a6a223c8be6ba11f1c180c7f381914abe127c0dffb0ec91d2e0a8e06892c92
>   

I usually delete the offender from distfiles and let it download again. 
If it still fails, try sync'ing again.  After that, wait until portage
gets updated and try again.  You could also be nice and see if there is
a bug report about the offender and file one if not so the maintainer
knows about it.

That said, it could be that the server you are getting them from is
having problems.  I have ran into that a time or two as well.  Switching
servers may help.

That's my thoughts at least.

Dale

:-)  :-)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Digest verification failed:

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]

On Sunday 01 October 2006 02:23, David Relson wrote:
> In the last few days I've been encountering lots of "Digest
> verification failed" messages indicating SHA256 verification
> problems (see below).
>
> Searching the web, I've found the "generate your own" digest solution,
> i.e.  "ebuild ...package...ebuild digest".  Since the checksums are
> present to ensure integrity, this seems like a bad idea.
>
> Is it a bad idea to generate my own digest values?

Yes. There is now a section about it in the handbook [1].

> If so, what are the alternatives?
[SNIP]
> !!! Digest verification failed:
> !!! /usr/portage/sys-devel/gettext/files/gettext-0.12.1-without_java.patch
> !!! Reason: Failed on SHA256 verification
> !!! Got:
> 6dfefe191bc9435a957f7f6ff0658a771cf6ccffbaf169cae79ce7017a0421ee
> !!! Expected:
> c5a6a223c8be6ba11f1c180c7f381914abe127c0dffb0ec91d2e0a8e06892c92

Since the offending file is in the portage tree rather than in distfiles it
doesn't make a lot of sense to delete it since only a sync will be able to
refetch it anyway. Had it been in distfiles then Dales suggestions are correct.

In this case, however, the problem isn't with the file rather it's with
dev-util/pycrypto (which calculates the hash) [2]. And wow, that bug is really
old by now! ;P The solution:

# emerge -va1 =dev-python/pycrypto-2.0.1-r5

[1] http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=2&chap=1#doc_chap4
[2] http://bugs.gentoo.org/show_bug.cgi?id=131293

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Digest verification failed:

[David Relson]

On Sun, 1 Oct 2006 03:41:39 +0200
Bo Ørsted Andresen wrote:

...[snip]...

> Since the offending file is in the portage tree rather than in
> distfiles it doesn't make a lot of sense to delete it since only a
> sync will be able to refetch it anyway. Had it been in distfiles then
> Dales suggestions are correct.
> 
> In this case, however, the problem isn't with the file rather it's
> with dev-util/pycrypto (which calculates the hash) [2]. And wow, that
> bug is really old by now! ;P The solution:
> 
> # emerge -va1 =dev-python/pycrypto-2.0.1-r5
> 
> [1]
> http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=2&chap=1#doc_chap4
> [2] http://bugs.gentoo.org/show_bug.cgi?id=131293
> 
> -- 
> Bo Andresen

Bo,

You've provided the solution!  Thanks.

David

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Digest verification failed:

[de Almeida, Valmor F.]

Hello,

Any inputs on what this problem might be? Any use of --searchdesc will
result in a similar output.

Thanks,

--
Valmor

-> emerge --searchdesc eclipse
Searching...  \!!! Digest verification failed:
!!! /usr/portage/app-backup/bacula/bacula-2.4.1-r1.ebuild
!!! Reason: Filesize does not match recorded size
!!! Got: 15696
!!! Expected: 15693
 /!!! Digest verification failed:
!!!
/usr/portage/local/layman/science/dev-cpp/growler-core/growler-core-0.3.
7.ebuild
!!! Reason: Filesize does not match recorded size
!!! Got: 793
!!! Expected: 916
emerge: search: aux_get() failed, skipping
 |!!! Digest verification failed:
!!!
/usr/portage/local/layman/science/dev-cpp/growler-link/growler-link-0.3.
7.ebuild
!!! Reason: Filesize does not match recorded size
!!! Got: 817
!!! Expected: 940
emerge: search: aux_get() failed, skipping
 /!!! Digest verification failed:
!!!
/usr/portage/local/layman/science/dev-cpp/growler-math/growler-math-0.3.
4.1.ebuild
!!! Reason: Filesize does not match recorded size
!!! Got: 695

---------------------------------
Valmor de Almeida, Ph.D.
Oak Ridge National Laboratory
1 Bethel Valley Road
PO Box 2008
Oak Ridge TN 37831-6181

url: dealmeidav.ornl.gov
tel: 865-241-2906
fax: 865-241-4829
---------------------------------

Re: [gentoo-user] Digest verification failed:

[Markos Chandras]

On Thursday 06 November 2008 19:14:57 de Almeida, Valmor F. wrote:
> Hello,
>
> Any inputs on what this problem might be? Any use of --searchdesc will
> result in a similar output.
>
> Thanks,
>
> --
> Valmor
>
> -> emerge --searchdesc eclipse
> Searching...  \!!! Digest verification failed:
> !!! /usr/portage/app-backup/bacula/bacula-2.4.1-r1.ebuild
> !!! Reason: Filesize does not match recorded size
> !!! Got: 15696
> !!! Expected: 15693
>  /!!! Digest verification failed:
> !!!
> /usr/portage/local/layman/science/dev-cpp/growler-core/growler-core-0.3.
> 7.ebuild
> !!! Reason: Filesize does not match recorded size
> !!! Got: 793
> !!! Expected: 916
> emerge: search: aux_get() failed, skipping
>
>  |!!! Digest verification failed:
>
> !!!
> /usr/portage/local/layman/science/dev-cpp/growler-link/growler-link-0.3.
> 7.ebuild
> !!! Reason: Filesize does not match recorded size
> !!! Got: 817
> !!! Expected: 940
> emerge: search: aux_get() failed, skipping
>  /!!! Digest verification failed:
> !!!
> /usr/portage/local/layman/science/dev-cpp/growler-math/growler-math-0.3.
> 4.1.ebuild
> !!! Reason: Filesize does not match recorded size
> !!! Got: 695
>
> ---------------------------------
> Valmor de Almeida, Ph.D.
> Oak Ridge National Laboratory
> 1 Bethel Valley Road
> PO Box 2008
> Oak Ridge TN 37831-6181
>
> url: dealmeidav.ornl.gov
> tel: 865-241-2906
> fax: 865-241-4829
> ---------------------------------

Try layman -S later. growler-math seems to have wrong manifest. It should be 
fixed very soon else contact the maintener. You can find maintainers e-mail 
on 

/usr/portage/local/layman/science/dev-cpp/growler-math/ChangeLog file 
-- 
Markos Chandras

[gentoo-user] Digest verification failed:

[Valmor de Almeida]

[-- Attachment #1: Type: text/plain, Size: 528 bytes --]

Hello,

I have done several

emerge --sync

today but the digest verification problem below does not go away.
Any thoughts?

Thank you.

--
Valmor

>>> Fetching (165 of 221) media-libs/mesa-11.0.6::gentoo

!!! Digest verification failed:
!!! /usr/portage/media-libs/mesa/mesa-9999.ebuild
!!! Reason: Failed on SHA256 verification
!!! Got: e2eb88ce00f4e8f37a940c982bfc7c38d5ed015477caa3397508792ca620968d
!!! Expected:
eb7a5581c6001e07d6a2a817f023cfd005ee45cda03cfca498e825bf3d3104a4

>>> Failed to emerge media-libs/mesa-11.0.6

[-- Attachment #2: Type: text/html, Size: 687 bytes --]

Re: [gentoo-user] Digest verification failed:

[Sam Jorna]

[-- Attachment #1: Type: text/plain, Size: 602 bytes --]

On Thu, Apr 07, 2016 at 06:52:20PM -0400, Valmor de Almeida wrote:
>    Hello,
>    I have done several
>    emerge --sync
>    today but the digest verification problem below does not go away.
>    Any thoughts?
>    Thank you.

This has been reported in Bug 579204 [0] and, as far as I am aware, was either
caused by bad timing between commits and rsync metadata generation or some other
factor in generating the metadata being pushed out to rsync servers; though from
what I've seen it seems to only affect some mirrors.

0: https://bugs.gentoo.org/579204

--
Sam Jorna (wraeth)
GnuPG Key: D6180C26

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 951 bytes --]