From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David_W_Noon@f38.n261.z1
From: David W Noon <dwnoon@spamtrap.ntlworld.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 03 Jul 2007 11:27 in article <f6d8aq$esv$1@snic.vub.ac.be> of
alt.os.linux.gentoo, Wim Cossement(a@b.c) wrote:
> After syncin' a few moment ago I get a bad digest for pyxml 0.8.4, has
> anyone noticed this as well?
Yes, the same package gave me a bad file size too, this morning.
These occur regularly, if you emerge sync frequently.
> Calculating world dependencies |!!! Digest verification failed:
> !!! /usr/portage/dev-python/pyxml/pyxml-0.8.4.ebuild
> !!! Reason: Filesize does not match recorded size
> !!! Got: 1120
> !!! Expected: 1126
>
> I know it's possible to recalculate these hashes and stuff, but could
> anyone tell me how it works?
Firstly, you have actually inherited the corruption from rsync server. If you
emerge sync again it will likely go away.
Each package has a list of MD5, SHA1, SHA256 and whatever hash values for each
file in the package: the ebuild, any tarballs, etc. Each file also has a
specified size, so that the checksum(s) and the file size must all match with the
downloaded resource files.
The above message is telling you the ebuild is 6 bytes too large for the file
size, or the file size is 6 bytes too small for the ebuild file. If you examine
the ebuild file, with less or the like, and it looks valid, you can have the file
size and has values recalculated using:
ebuild /usr/portage/dev-python/pyxml-0.8.4.ebuild digest
[You will need to be root to do this.] If a tarball has a wrong hash value or
size, use tar -tjf <tarball> to test its validity before you have the hashes
recalculated for the ebuild.
- --
Regards
Dave [RLU#314465]
================================================== ====
dwnoon@spamtrap.ntlworld.com (David W Noon) Remove spam trap to reply via
e-mail.
================================================== ====
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFGimY79MqaUJQw2MkRAtT8AJ4xJR/lzz3QLBaCK757L3sthSHVDQCcDWhA
DFzypA6IfdwiJJluHT2pIVI=
=MDDF
-----END PGP SIGNATURE-----