I am attempting to do a stage 1 install on a new laptop. It bootstapped successfully however emerge system fails when unpacking the sys-libs/db tarball. tar falls over when extracting directories. Experiment shows that if --absolute-names is specified in the tarvars then the tarball will unpack successfully, however I am not sure how to modify the tarvars used by the ebuild. Note that this problem has occured with other versions of db >4.1.25 when I have attempted to extract their tarballs. Reproducible: Always Steps to Reproduce: 1. Use livecd 2004.3-r1 2. Follow Gentoo handbook instructions to install a stage 1 system. 3. emerge system fails. Actual Results: The following is observed when attempting to emerge the db package manually using "emerge -d db" (after the initial emerge system has failed) Calculating dependencies Parent: None Depstring: sys-libs/db Candidates: ['sys-libs/db'] ebuild: sys-libs/db-4.1.25_p1-r4 binpkg: None + dyn_setup + '[' GNU == Linux ']' + pkg_setup + return + set +x + dyn_unpack + trap abort_unpack SIGINT SIGQUIT + local newstuff=no + '[' -e /var/tmp/portage/db-4.1.25_p1-r4/work ']' + '[' -e /var/tmp/portage/db-4.1.25_p1-r4/work ']' + install -m0700 -d /var/tmp/portage/db-4.1.25_p1-r4/work + '[' -d /var/tmp/portage/db-4.1.25_p1-r4/work ']' + cd /var/tmp/portage/db-4.1.25_p1-r4/work + echo '>>> Unpacking source...' >>> Unpacking source... + src_unpack + unpack db-4.1.25.tar.gz + local x + local y + local myfail + local tarvars + '[' GNU == BSD ']' + tarvars=--no-same-owner + myfail=failure unpacking db-4.1.25.tar.gz ++ pwd + echo '>>> Unpacking db-4.1.25.tar.gz to /var/tmp/portage/db-4.1.25_p1-r4/work' >>> Unpacking db-4.1.25.tar.gz to /var/tmp/portage/db-4.1.25_p1-r4/work + y=db-4.1.25.tar + y=tar + '[' tar == tar ']' + tar xzf /usr/portage/distfiles/db-4.1.25.tar.gz --no-same-owner tar: db-4.1.25/xa: Directory renamed before its status could be extracted tar: db-4.1.25/txn: Directory renamed before its status could be extracted tar: db-4.1.25/tcl: Directory renamed before its status could be extracted tar: db-4.1.25/rpc_server: Directory renamed before its status could be extracted tar: db-4.1.25/rpc_client: Directory renamed before its status could be extracted tar: db-4.1.25/rep: Directory renamed before its status could be extracted tar: db-4.1.25/qam: Directory renamed before its status could be extracted tar: db-4.1.25/os_win32: Directory renamed before its status could be extracted tar: db-4.1.25/os_vxworks: Directory renamed before its status could be extracted tar: db-4.1.25/os: Directory renamed before its status could be extracted tar: db-4.1.25/mutex: Directory renamed before its status could be extracted tar: db-4.1.25/mp: Directory renamed before its status could be extracted tar: db-4.1.25/log: Directory renamed before its status could be extracted tar: db-4.1.25/lock: Directory renamed before its status could be extracted tar: db-4.1.25/libdb_java: Directory renamed before its status could be extracted tar: db-4.1.25/hsearch: Directory renamed before its status could be extracted tar: db-4.1.25/hmac: Directory renamed before its status could be extracted tar: db-4.1.25/hash: Directory renamed before its status could be extracted tar: db-4.1.25/fileops: Directory renamed before its status could be extracted tar: db-4.1.25/examples_cxx: Directory renamed before its status could be extracted tar: db-4.1.25/examples_c: Directory renamed before its status could be extracted tar: db-4.1.25/env: Directory renamed before its status could be extracted tar: db-4.1.25/dbreg: Directory renamed before its status could be extracted tar: db-4.1.25/dbm: Directory renamed before its status could be extracted tar: db-4.1.25/dbinc_auto: Directory renamed before its status could be extracted tar: db-4.1.25/dbinc: Directory renamed before its status could be extracted tar: db-4.1.25/db_verify: Directory renamed before its status could be extracted tar: db-4.1.25/db_upgrade: Directory renamed before its status could be extracted tar: db-4.1.25/db_stat: Directory renamed before its status could be extracted tar: db-4.1.25/db_recover: Directory renamed before its status could be extracted tar: db-4.1.25/db_printlog: Directory renamed before its status could be extracted tar: db-4.1.25/db_load: Directory renamed before its status could be extracted tar: db-4.1.25/db_dump185: Directory renamed before its status could be extracted tar: db-4.1.25/db_dump: Directory renamed before its status could be extracted tar: db-4.1.25/db_deadlock: Directory renamed before its status could be extracted tar: db-4.1.25/db_checkpoint: Directory renamed before its status could be extracted tar: db-4.1.25/db_archive: Directory renamed before its status could be extracted tar: db-4.1.25/db185: Directory renamed before its status could be extracted tar: db-4.1.25/db: Directory renamed before its status could be extracted tar: db-4.1.25/cxx: Directory renamed before its status could be extracted tar: db-4.1.25/crypto: Directory renamed before its status could be extracted tar: db-4.1.25/common: Directory renamed before its status could be extracted tar: db-4.1.25/clib: Directory renamed before its status could be extracted tar: db-4.1.25/build_unix: Directory renamed before its status could be extracted tar: db-4.1.25/btree: Directory renamed before its status could be extracted tar: db-4.1.25: Directory renamed before its status could be extracted tar: Error exit delayed from previous errors + diefunc unpack 373 2 'failure unpacking db-4.1.25.tar.gz' + local funcname=unpack lineno=373 exitcode=2 + shift 3 + echo + echo '!!! ERROR: sys-libs/db-4.1.25_p1-r4 failed.' !!! ERROR: sys-libs/db-4.1.25_p1-r4 failed. + echo '!!! Function unpack, Line 373, Exitcode 2' !!! Function unpack, Line 373, Exitcode 2 + echo '!!! failure unpacking db-4.1.25.tar.gz' !!! failure unpacking db-4.1.25.tar.gz Expected Results: emerge system should complete without errors Gentoo Base System version 1.4.16 Portage 2.0.51-r3 (default-linux/x86/2004.3, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r1 i686) ================================================================= System uname: 2.6.9-gentoo-r1 i686 Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz Autoconf: Automake: Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux-headers-2.4.21-r1 Libtools: ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -mcpu=pentium4 -mmmx -msse -msse2 -mfpmath=sse,387 -malign-double -maccumulate-outgoing-args -O3 -fprefetch-loop-arrays -ffast-math -fforce-addr -falign-functions=4 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/kde/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="-march=pentium4 -mcpu=pentium4 -mmmx -msse -msse2 -mfpmath=sse,387 -malign-double -maccumulate-outgoing-args -O3 -fprefetch-loop-arrays -ffast-math -fforce-addr -falign-functions=4 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://gentoo.blueyonder.co.uk ftp://mirrors.blueyonder.co.uk/mirrors/gentoo http://gentoo.osuosl.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X acl apm arts avi berkdb bitmap-fonts cdr crypt cups dvd encode extensions foomaticdb fortran gdbm gif gnome gtk gtk2 ipv6 jpeg kde libwww mad mikmod mmx motif mpeg ncurses nls oggvorbis opengl oss pam pdflib perl perlsuid png python qt quicktime readline sdl spell sse ssl svga tcpd tiff truetype xml2 xmms xv zlib"
I've never seen problems with it before, but looking at your monstrous compiler flags, there is probably one (or more) of them causing havoc with tar. Please check info gcc on each an every of the flags. For example -ffast-math is not suitable as a global flag, and should only be enabled by the author on one package. Also keep in mind that the gcc compiler is not bug-free. Especially sse2 support is still broken. So, recompile tar (and possibly other programs) and try again
I'm also having problems with db-4.1.25 during install of 2004.3 stage-1. scripts/bootstrap.sh seems unable to download it from anywhere. I've run emerge sync a couple of times to see if it's fixed in CVS, but at this point, even attempting to download it from sleepycat fails.
I just "hack" fixed my ebuild to get this one to work. Summary: "sleepycat" change the location of the file download. Ebuild has not been updated. See: http://forums.gentoo.org/viewtopic.php?p=2033440#2033440 Who's the ebuild maintainer for this?
I maintain it, but your problems are not caused by moved tarballs. I'll change the location in the ebuilds. This kind of behaviour from upstream is why gentoo mirrors packages. That makes sure that people can download things. If things can not be downloaded the error is different though. This seems to be an issue with tar (Sam, do you by any chance run a different tar from app-arch/tar)?
I have now bootstapped again from scratch using a more mild set of optimisations - actually not that much milder, went back to my old trusted set (removed malign-double and ffast-math which were recommended on one particular forum thread about Pentium 4M flags). Sorry to inconvenience you Paul - and well spotted, I would have expected compile time errors rather than odd behaviour from tar. Still we learn something new every day. Changing status to Resolved, Invalid
