Bug 75453 – blackdown-jre-1.4.2.01 ebuild fails with: "Failed to get offset of tarball!"

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Magnus Ahlberg 2004-12-23 09:28:03 UTC]

When I try to emerge blackdown. It doesn't even try to download any files. Emerge just gives me an error message and shuts down.

Reproducible: Always
Steps to Reproduce:
1. emerge dev-java/blackdown-jre-1.4.2.01
2.
3.

Actual Results:  
# emerge blackdown-jre
Calculating dependencies ...done!
>>> emerge (1 of 1) dev-java/blackdown-jre-1.4.2.01 to /
>>> Unpacking source...
* Failed to get offset of tarball! 

Expected Results:  
Downloaded the file and emerged blackdown-jre 1.4.2.01 without errors.

# emerge info
Portage 2.0.51-r8 (default-linux/x86/2004.2, gcc-3.4.3, glibc-2.3.4.20041102-r0,
2.6.9-gentoo-r9 i686)
=================================================================
System uname: 2.6.9-gentoo-r9 i686 Intel(R) Pentium(R) 4 CPU 2.00GHz
Gentoo Base System version 1.6.8
Python:              dev-lang/python-2.3.4 [2.3.4 (#1, Dec 21 2004, 22:29:45)]
dev-lang/python:     2.3.4
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.8.5-r2, 1.5, 1.6.3, 1.7.9, 1.4_p6, 1.9.3
sys-devel/binutils:  2.15.92.0.2-r2
sys-devel/libtool:   1.5.10-r2
virtual/os-headers:  2.6.8.1-r1
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -ftracer -fprefetch-loop-arrays
-pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/bind /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -ftracer
-fprefetch-loop-arrays -pipe -fvisibility-inlines-hidden"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks moo sandbox sfperms"
GENTOO_MIRRORS="ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/
ftp://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://ftp.du.se/pub/os/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/fluidportage/trunk"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="x86 X aalib acl alsa apache2 apm avi berkdb bitmap-fonts cdr crypt cups
directfb dri dts dvd encode esd fam flac foomaticdb fortran gdbm gif gimpprint
glx gnome gphoto2 gpm gtk gtk2 imagemagick imlib ipv6 java jpeg libwww mad
matroska mikmod mmx motif mpeg ncurses nls oggvorbis opengl oss pam pcmcia
pdflib perl png ppds python quicktime readline samba sdl slang spell sse ssl svg
svga tcltk tcpd tiff truetype xml xml2 xmms xv zlib video_cards_radeon"

[Comment 1 Thomas Matthijs (RETIRED) 2004-12-23 09:33:07 UTC]

please rsync and try again

[Comment 2 Magnus Ahlberg 2004-12-23 11:15:53 UTC]

Yes it seems to be working now. Thanks alot.

[Comment 3 Thomas Matthijs (RETIRED) 2004-12-23 11:19:04 UTC]

fixed

[Comment 4 Todd Walton 2005-04-05 21:11:57 UTC]

I'm having this very problem with blackdown-jar-1.4.2.01-r1.  This bug was opened last December, but it's now April, and I'm having the problem again.  I've re-synced and tried again (before I got here, actually).  It didn't work.  What causes this?

[Comment 5 Patrick Kursawe (RETIRED) 2005-06-04 12:21:14 UTC]

Having the same problem with -r1 and can't find any CVS log entry for 1.4.2.01
of 2004-12-23 - what's happening here?

[Comment 6 Thomas Matthijs (RETIRED) 2005-09-10 11:24:03 UTC]

lets see some 'emerge info' from ppl still having this problem
and the env vars you have, and the exact ebuild you tried with
and version of tar/bzip