Bug 60866 – When I try to emerge limewire, I get an error saying that the file (/usr/portage/distfiles//LimeWireLinux.tgz) does not exist.

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Russell Thoams 2004-08-19 02:05:02 UTC]

I hope this is ok. It's my first bug report. Basicially I noticed it a few days ago, and posted on the forums for more information. I was then told by a developer that this sort of error should be filed as a bug report, but however that it should be fixed now. I tried again today, to emerge limewire and got the same error:

tux ~ # emerge limewire
Calculating dependencies ...done!
>>> emerge (1 of 1) net-p2p/limewire-4.1.3 to /
 
!!! File is corrupt or incomplete. (Digests do not match)
>>> our recorded digest: a705476aacd812914963da83b39b4e1d
>>>  your file's digest: 5903ab5809ed4af56cd6d09e27b98cf9
!!! File does not exist: /usr/portage/distfiles//LimeWireLinux.tgz



Reproducible: Always
Steps to Reproduce:
1. Open a terminal, and login to root
2. Type 'emerge limewire'
3. The error should be plain to see

Actual Results:  
tux ~ # emerge limewire
Calculating dependencies ...done!
>>> emerge (1 of 1) net-p2p/limewire-4.1.3 to /
 
!!! File is corrupt or incomplete. (Digests do not match)
>>> our recorded digest: a705476aacd812914963da83b39b4e1d
>>>  your file's digest: 5903ab5809ed4af56cd6d09e27b98cf9
!!! File does not exist: /usr/portage/distfiles//LimeWireLinux.tgz


Expected Results:  
It should have gone through, and built the package as normal.

tux ~ # emerge info
Portage 2.0.50-r9 (default-x86-2004.0, gcc-3.3.4, glibc-2.3.4.20040808-r0,
2.6.7-gentoo-r9)
=================================================================
System uname: 2.6.7-gentoo-r9 i686 AMD Athlon(tm) XP 3000+
Gentoo Base System version 1.5.2
Autoconf: sys-devel/autoconf-2.59-r4
Automake: sys-devel/automake-1.8.5-r1
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/
ftp://mirrors.sec.informatik.tu-darmstadt.de/gentoo/
http://gentoo.blueyonder.co.uk http://gentoo.mirror.sdv.fr"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X aim alsa apm arts avi berkdb calendar cdr crypt cups dvd encode esd
foomaticdb ftp gdbm gif gnome gphoto2 gpm gtk gtk2 imlib java jpeg libg++ libwww
mad mikmod motif mozilla mpeg msn mysql ncurses nls oggvorbis opengl oss pam
pdflib pdflip perl png ppds python quicktime readline sdl slang sockets spell
spl ssl svga tcltk tcpd truetype usb x86 xml2 xmms xv zlib"

[Comment 1 Paul de Vrieze (RETIRED) 2004-08-19 05:16:12 UTC]

The ebuilds are broken. They use the same name for different versions. It isn't strange this causes md5 errors. Local copies of this package need to be used.

[Comment 2 Jon Hood (RETIRED) 2004-08-19 09:54:45 UTC]

There was no COPYING file in the tarball and I wasn't sure if it was safe to rename and distribute on our servers, and you caught me just as I talked to them. LimeWire is GPL'd, so we can safely rename and distribute the tarballs :). We shouldn't run into this problem anymore ;). Fixed in portage.