USE=static emerge tar but after all emerge failed like this. I copy binary tar to my system, and emerge tar recovery. >>> Emerging (1 of 1) www-plugins/moonlight-1.0.1 >>> Downloading 'ftp://ftp.novell.com/pub/mono/sources/moon/moon-1.0.1.tar.bz2' --2009-08-03 14:40:16-- ftp://ftp.novell.com/pub/mono/sources/moon/moon-1.0.1.tar.bz2 => `/usr/portage/distfiles/moon-1.0.1.tar.bz2' Resolving ftp.novell.com... 130.57.1.88 Connecting to ftp.novell.com|130.57.1.88|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /pub/mono/sources/moon ... done. ==> SIZE moon-1.0.1.tar.bz2 ... 8812587 ==> PASV ... done. ==> RETR moon-1.0.1.tar.bz2 ... done. Length: 8812587 (8.4M) 100%[==========================================================>] 8,812,587 421K/s in 21s 2009-08-03 14:40:39 (401 KB/s) - `/usr/portage/distfiles/moon-1.0.1.tar.bz2' saved [8812587] * moon-1.0.1.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking moon-1.0.1.tar.bz2 to /var/tmp/portage/www-plugins/moonlight-1.0.1/work * * ERROR: www-plugins/moonlight-1.0.1 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 2324: Called _eapi0_src_unpack * ebuild.sh, line 593: Called unpack 'moon-1.0.1.tar.bz2' * ebuild.sh, line 386: Called _unpack_tar 'bzip2' * ebuild.sh, line 361: Called die * The specific snippet of code: * assert "$myfail" * The die message: * failure unpacking moon-1.0.1.tar.bz2 * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/www-plugins/moonlight-1.0.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/www-plugins/moonlight-1.0.1/temp/environment'. * >>> Emerging (1 of 1) app-arch/tar-1.22 * tar-1.22.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking tar-1.22.tar.bz2 to /var/tmp/portage/app-arch/tar-1.22/work * * ERROR: app-arch/tar-1.22 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 2582: Called unpack 'tar-1.22.tar.bz2' * ebuild.sh, line 386: Called _unpack_tar 'bzip2' * ebuild.sh, line 361: Called die * The specific snippet of code: * assert "$myfail" * The die message: * failure unpacking tar-1.22.tar.bz2 * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/app-arch/tar-1.22/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-arch/tar-1.22/temp/environment'. Reproducible: Always
please paste your 'emerge --info' to this bug to assist the maintainers in diagnosing this issue.
Created attachment 200089 [details] emerge --info Here you are.
This seems to be the same as bug 252680, though I'm not sure why it only manifests when tar is static, since the patch _is_ applied.
*** Bug 287470 has been marked as a duplicate of this bug. ***
re-open if this is still a problem
