Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 27176 - mplayer 0.91: md5 digest for Blue-1.0.tar.bz2 doesn't match the actual file
Summary: mplayer 0.91: md5 digest for Blue-1.0.tar.bz2 doesn't match the actual file
Status: VERIFIED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
: 27380 28028 28724 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-08-23 07:16 UTC by jochen
Modified: 2003-09-29 13:30 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jochen 2003-08-23 07:16:49 UTC
Trying to emerge mplayer-0.91 i get the error message

!!! File is corrupt or incomplete. (Digests do not match)
>>> our recorded digest: 2cd7baa4ea60c42251c3dceaab9ae9cb
>>>  your file's digest: 64e2d18438bbef16822c141d846884f6
!!! File does not exist: /usr/portage/distfiles//Blue-1.0.tar.bz2

(Yes, I have that file:
# ls -l /usr/portage/distfiles//Blue-1.0.tar.bz2
-rw-rw-r--    1 root     portage    219130 Aug 23 15:39
/usr/portage/distfiles//Blue-1.0.tar.bz2
)

I got the file from sunsite.cnlab-switch.ch[195.176.255.9]

Reproducible: Always
Steps to Reproduce:
1.
2.
3.



Portage 2.0.49 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.20-xfs-r3)
=================================================================
System uname: 2.4.20-xfs-r3 i686 Celeron (Coppermine)
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium3 -O3 -pipe -mcpu=pentium3 -mmmx -msse -fforce-addr -fomit
-frame-pointer -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -falign-fu
nctions=4"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/confi
g /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/share/texmf/tex/generic/co
nfig/ /usr/share/texmf/tex/platex/config/"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-march=pentium3 -O3 -pipe -mcpu=pentium3 -mmmx -msse -fforce-addr -fom
it-frame-pointer -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -falign-
functions=4"
DISTDIR="/usr/portage/distfiles"
FEATURES="sandbox strict userpriv ccache distcc"
GENTOO_MIRRORS="ftp://sunsite.cnlab-switch.ch/mirror/gentoo/ http://gentoo.inode
.at/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="avi foomaticdb gif jpeg libg++ mad mmx mpeg nls pdflib png spell xml2 xmms 
xv zlib gdbm slang X sdl tcpd pam libwww perl python esd imlib oggvorbis gtk mot
if opengl xfs berkdb -3dnow -arts -qt -kde acl apm crypt dga doc dvd gphoto2 gpm
 imap ipv6 java jikes kerberos mbox oss pcmcia ncurses readline sse tetex truety
pe x86 -gnome -qtmt -quicktime -svga -mikmod tcltk mldonkeypango -afs ssl clamav
 gtkhtml xface -cups encode"
Comment 1 Martin Holzer (RETIRED) gentoo-dev 2003-08-23 09:58:17 UTC
in cvs
Comment 2 Martin Holzer (RETIRED) gentoo-dev 2003-08-27 01:55:30 UTC
*** Bug 27380 has been marked as a duplicate of this bug. ***
Comment 3 Guy 2003-09-06 19:31:54 UTC
The actual problem is demonstrated below:

fierywyrme distfiles # ls -l B*
-rw-r--r--    1 root     root       144420 Mar 29 20:37 BitTorrent-3.2.1b.tar.gz
-rw-r--r--    1 root     root        40443 May  3 06:49 BlackXMMS.zip
-rw-rw-r--    1 root     portage    219130 Sep  3 18:30 Blue-1.0.tar.bz2
-rw-r--r--    1 root     root       156764 May  3 06:49 Blue-small-1.0.tar.bz2
-rw-r--r--    1 root     root       281128 May  3 06:49 BlueHeart-1.4.tar.bz2
-rw-r--r--    1 root     root       281084 May  3 06:49 BlueHeart.tar.bz2
-rw-r--r--    1 root     root       119833 May  3 06:49 BlueIce.zip
-rw-r--r--    1 root     root       132615 May  3 06:49 BlueSteel.zip
-rw-r--r--    1 root     root       128006 May  3 06:49 BlueSteel_xmms.zip
-rw-r--r--    1 root     root       345631 May  7 21:48 Blursk-1.3.tar.gz
-rw-r--r--    1 root     root       139919 May  3 06:49 BrushedMetal_Xmms.zip
fierywyrme distfiles # emerge mplayer
Calculating dependencies ...done!
>>> emerge (1 of 1) media-video/mplayer-1.0_pre1 to /
>>> md5 src_uri ;-) MPlayer-1.0pre1.tar.bz2
>>> md5 src_uri ;-) font-arial-iso-8859-1.tar.bz2
>>> md5 src_uri ;-) font-arial-iso-8859-2.tar.bz2
>>> md5 src_uri ;-) svgalib_helper-1.9.17-mplayer.tar.bz2

!!! File is corrupt or incomplete. (Digests do not match)
>>> our recorded digest: 64e2d18438bbef16822c141d846884f6
>>>  your file's digest: ee26d46d5c52c5e3ac15164e78300b44
!!! File does not exist: /usr/portage/distfiles//Blue-1.0.tar.bz2

The file "doesn't exist" because the ownership is wrong. I suspect that many of the mirror sites also have this wrong.
Comment 4 Guy 2003-09-06 19:39:48 UTC
I forgot the 'work around'.

# rm /usr/portage/distfiles/Blue-1.0.tar.bz2
# emerge mplayer

All should be fine.

:-)
Comment 5 Joseph Nievelt 2003-09-06 23:50:58 UTC
<i>The file "doesn't exist" because the ownership is wrong. I suspect that many of the mirror sites also have this wrong.</i>

This is incorrect.  If I do the same listing, my Blue-1.0.tar.bz2 belongs to the portage group (check yours?), but my mplayer 0.91/1.0_pre1 installed just fine.  The nature of the problem is outlined in bug 27380 (in that case it also said file does not exist) although for some reason my file had a different md5sum than in this bug report.  The "File does not exist" means that the file with that name is not the file the ebuild is expecting (a bug in emerge?).

The cause of this problem is not even related to the group ownership (or group write permission, although perhaps these should be changed).  Apparently at some point the file contents changed but the filename did not.  Since the file digests are separate from the ebuild files it is hard to tell exactly when, but it must have been somewhere between the last revision of 0.90 and 0.91 (give or take a day?).  A proper fix for this would give the file a different version number.  Of course, in agreement with bug 27380, your workaround is correct.
Comment 6 Joseph Nievelt 2003-09-07 00:26:56 UTC
Sorry to put more traffic on a resolved bug, but I checked the CVS and here's what I've found:

Blue-1.0-tar.bz2 digest from 8/21 to 8/23 (digest v1.1):
2cd7baa4ea60c42251c3dceaab9ae9cb (218710 bytes)
This is presumably the digest for the file 0.90 used.

Blue-1.0-tar.bz2 digest since 8/23 (digest v1.2):
64e2d18438bbef16822c141d846884f6 (219130 bytes)
This change is the fix for this bug.

jochen's bug was that he had the new Blue-1.0.tar.bz2 but the digest hadn't been updated.  This is the sort of thing that would be rather suspicious, if it hadn't coincided with the 0.91 release of the mplayer ebuild.

The bug that Guy and I had is closer to the opposite.  We had the old Blue-1.0.tar.bz2 file with the new digest file.  Since the file is larger, and because our fetch command resumes, we ended up with the old file plus the last 420 bytes from the new file.  Of course the resulting md5sum doesn't match the new digest (or anything really), and we had the error.  Notice that Guy's incorrect md5sum is identical to the one in bug 27380.
Comment 7 Peter Penkala gentoo-dev 2003-09-07 15:10:47 UTC
*** Bug 28028 has been marked as a duplicate of this bug. ***
Comment 8 Martin Holzer (RETIRED) gentoo-dev 2003-09-07 15:28:03 UTC
mirror-admin: could you delete the file on distfiles and import the correct on to the mirror server ?
Comment 9 SpanKY gentoo-dev 2003-09-14 13:33:05 UTC
*** Bug 28724 has been marked as a duplicate of this bug. ***
Comment 10 Joseph Nievelt 2003-09-29 13:23:45 UTC
It looks like the corrupted hash made it into the portage tree!  When I try
to update to 1.0_pre1-r1 I get

!!! File is corrupt or incomplete. (Digests do not match)
>>> our recorded digest: ee26d46d5c52c5e3ac15164e78300b44
>>>  your file's digest: 64e2d18438bbef16822c141d846884f6

I redownload the file, and it's still the same hash, so it should be the
right file.  Somehow just the wrong hash got in there.
Comment 11 Martin Holzer (RETIRED) gentoo-dev 2003-09-29 13:26:53 UTC
just is fixed in cvs

see bug #29640