Here is what I got -------------------- $ emerge xv >>> emerge ( 1 of 1) media-gfx/xv-3.10a-r11 to / -- snip -- >>>Unpacking source ... Unpacking /usr/porgage/distfiles/xv-3.10a-jumbo-patches-20050110.tar.bz2 to /var/tmp/portage/xv-3.10a-r11/work tar: this does not look like a tar archive. ------------------------------------- I made the following change which allowed the package to succesfuly install. I (temporarly changed) the following line in /usr/lib/portage/bin/ebuild.sh -------------------------------------------------- > 383 old line > bzip2 -dc "${DESTDIR}/${x}" | tar -xf - ${tarvars} || die "$myfail" > 383 new line > tar -jxvf "${DESTDIR}/${x}" || die "$myfail" -------------------------------------------------- this change allowed me to succesfuly install the package. Reproducible: Always Steps to Reproduce: 1. emerge sync 2. emerge xv 3. Actual Results: Here is what I got -------------------- $ emerge xv >>> emerge ( 1 of 1) media-gfx/xv-3.10a-r11 to / -- snip -- >>>Unpacking source ... Unpacking /usr/porgage/distfiles/xv-3.10a-jumbo-patches-20050110.tar.bz2 to /var/tmp/portage/xv-3.10a-r11/work tar: this does not look like a tar archive. Expected Results: installed the package. ------------------------------------- I made the following change which allowed the package to succesfuly install. I (temporarly changed) the following line in /usr/lib/portage/bin/ebuild.sh -------------------------------------------------- > 383 old line > bzip2 -dc "${DESTDIR}/${x}" | tar -xf - ${tarvars} || die "$myfail" > 383 new line > tar -jxvf "${DESTDIR}/${x}" || die "$myfail" -------------------------------------------------- this change allowed me to succesfuly install the package.
does the md5 verify correctly? could this be a filesystem/disk error?
Jeff, please reopen this bug if it's still an issue and you can provide more details.