Mailing List Archive: emerge samba md5sum help(fix?) me

If this has already been posted please disregard.

What happened:

# emerge samba

Calculating dependencies ...done!

>>> emerge (1 of 1) net-fs/samba-3.0.7-r1 to /

!!! File is corrupt or incomplete. (Digests do not match)

>>> our recorded digest: a3e74c3cbb3303dcc92f037fdb35ff20

>>> your file's digest: 5906341429e64214909865a4be92e4ab

!!! File does not exist: /usr/portage/distfiles//samba-3.0.7.tar.gz

What I did:

# rm /usr/portage/distfiles/samba-3.0.7.tar.gz

Changed my ftp site and tried to emerge x3. (I guess I'm insane since I repeated myself expecting a different result.)

# emerge samba

Calculating dependencies ...done!

>>> emerge (1 of 1) net-fs/samba-3.0.7-r1 to /

!!! File is corrupt or incomplete. (Digests do not match)

>>> our recorded digest: a3e74c3cbb3303dcc92f037fdb35ff20

>>> your file's digest: 5906341429e64214909865a4be92e4ab

!!! File does not exist: /usr/portage/distfiles//samba-3.0.7.tar.gz

# cd /usr/portage/distfiles/samba-3.0.7.tar.gz

# md5sum samba-3.0.7.tar.gz

5906341429e64214909865a4be92e4ab samba-3.0.7.tar.gz

I went to a ftp site and confirmed that the recorded digest md5sum shown above is correct. On a windows xp machine with cygwin, went to www.samba.org and downloaded samba-3.0.7.tar.gz and:

> md5sum samba-3.0.7.tar.gz

5906341429e64214909865a4be92e4ab *samba-3.0.7.tar.gz

> gpg --import samba-pubkey.asc

gpg: key 2F87AF6F: public key "Samba Distribution Verification Key

<samba-bugs@samba.org>" imported

gpg: Total number processed: 1

gpg: imported: 1>

> gunzip samba-3.0.7.tar.gz

> gpg --verify samba-3.0.7.tar.asc

gpg: Signature made Sat Sep 11 21:05:57 2004 PST using DSA key ID 2F87AF6F

gpg: Good signature from "Samba Distribution Verification Key

<samba-bugs@samba.org>"

gpg: checking the trustdb

gpg: no ultimately trusted keys found

gpg: WARNING: This key is not certified with a trusted signature!

gpg: There is no indication that the signature belongs to the owner.

Primary key fingerprint: 3275 F01D 6565 3A81 AE7B 320C D779 0A5F 2F87 AF6F

> md5sum samba-3.0.7.tar

551236047f41aa65fa97960ff6c29b30 *samba-3.0.7.tar

back on the gentoo box...

# gunzip samba-3.0.7.tar.gz

# md5sum samba-3.0.7.tar

551236047f41aa65fa97960ff6c29b30 samba-3.0.7.tar

# gzip samba-3.0.7.tar

# md5sum samba-3.0.7.tar.gz

6bb3e2611055ffac3e66035eab4d7cb5 samba-3.0.7.tar.gz

ok, I think I know the problem... how can it be fixed?

Stu

_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!

--
gentoo-user@gentoo.org mailing list

Stuart Nolan wrote:
> If this has already been posted please disregard.
>
>
>
> What happened:
>
>
>
> # emerge samba
>
> Calculating dependencies ...done!
>
> >>> emerge (1 of 1) net-fs/samba-3.0.7-r1 to /
>
>
>
> !!! File is corrupt or incomplete. (Digests do not match)
>
> >>> our recorded digest: a3e74c3cbb3303dcc92f037fdb35ff20
>
> >>> your file's digest: 5906341429e64214909865a4be92e4ab
>
> !!! File does not exist: /usr/portage/distfiles//samba-3.0.7.tar.gz
>
>
>
> What I did:
>
>
>
> # rm /usr/portage/distfiles/samba-3.0.7.tar.gz
>
>
>
> Changed my ftp site and tried to emerge x3. (I guess I'm insane since I repeated myself expecting a different result.)
>
>
>
> # emerge samba
>
> Calculating dependencies ...done!
>
> >>> emerge (1 of 1) net-fs/samba-3.0.7-r1 to /
>
>
>
> !!! File is corrupt or incomplete. (Digests do not match)
>
> >>> our recorded digest: a3e74c3cbb3303dcc92f037fdb35ff20
>
> >>> your file's digest: 5906341429e64214909865a4be92e4ab
>
> !!! File does not exist: /usr/portage/distfiles//samba-3.0.7.tar.gz
>
>
>
> # cd /usr/portage/distfiles/samba-3.0.7.tar.gz
>
>
>
> # md5sum samba-3.0.7.tar.gz
>
> 5906341429e64214909865a4be92e4ab samba-3.0.7.tar.gz
>
> I went to a ftp site and confirmed that the recorded digest md5sum shown above is correct. On a windows xp machine with cygwin, went to www.samba.org and downloaded samba-3.0.7.tar.gz and:
>
<very thorough testing procedure snipped>
>
> ok, I think I know the problem... how can it be fixed?
>
>
>
> Stu
>

Wait a couple of hours (which have maybe already passed), emerge sync
again and see if the problem is fixed on the mirrors. The digest
apparently needs to be updated, but since Samba is a fairly important
package, the mismatch should be caught and corrected fairly quickly (if
in fact the problem was not that the mirrors were being rsynced at the
time you downloaded).

Alternatively, you can redigest the ebuild yourself (only do this if you
are sure you know a legitimate reason that the MD5 sum is wrong, such as
you editing the tarball's contents, or as in this case, you have checked
the md5 sum independently and you **know** that the "new" one is correct):

ebuild /usr/portage/net-fs/samba/samba-3.0.7-r1.ebuild digest

to redigest the files, and then emerge normally.

Hope this helps,
Holly

--
gentoo-user@gentoo.org mailing list