[32;01m*[0m CPV: app-shells/bash-completion-1.2 [32;01m*[0m REPO: gentoo_prefix [32;01m*[0m USE: elibc_Interix kernel_Interix prefix userland_GNU x86-interix >>> Unpacking source... >>> Unpacking bash-completion-1.2.tar.bz2 to /opt/gentoo/var/tmp/portage/app-shells/bash-completion-1.2/work tar: bash-completion-1.2/test/fixtures/_filedir/a"b: Cannot mkdir: No such file or directory tar: bash-completion-1.2/test/fixtures/_filedir/a"b/d: Cannot open: No such file or directory tar: Exiting with failure status due to previous errors [31;01m*[0m ERROR: app-shells/bash-completion-1.2 failed: [31;01m*[0m failure unpacking bash-completion-1.2.tar.bz2 [31;01m*[0m [31;01m*[0m Call stack: [31;01m*[0m ebuild.sh, line 54: Called call-ebuildshell 'src_unpack' [31;01m*[0m environment, line 113: Called src_unpack [31;01m*[0m environment, line 372: Called _eapi0_src_unpack [31;01m*[0m ebuild.sh, line 652: Called unpack 'bash-completion-1.2.tar.bz2' [31;01m*[0m ebuild.sh, line 438: Called _unpack_tar 'bzip2' [31;01m*[0m ebuild.sh, line 413: Called assert 'failure unpacking bash-completion-1.2.tar.bz2' [31;01m*[0m isolated-functions.sh, line 14: Called die [31;01m*[0m The specific snippet of code: [31;01m*[0m [[ $x -eq 0 ]] || die "$@" [31;01m*[0m [31;01m*[0m If you need support, post the output of 'emerge --info =app-shells/bash-completion-1.2', [31;01m*[0m the complete build log and the output of 'emerge -pqv =app-shells/bash-completion-1.2'. [31;01m*[0m The complete build log is located at '/opt/gentoo/var/tmp/portage/app-shells/bash-completion-1.2/temp/build.log'. [31;01m*[0m The ebuild environment file is located at '/opt/gentoo/var/tmp/portage/app-shells/bash-completion-1.2/temp/environment'. [31;01m*[0m S: '/opt/gentoo/var/tmp/portage/app-shells/bash-completion-1.2/work/bash-completion-1.2'
My suspicion is that it actually doesn't like the directory names, it tries to create this structure: % la /Library/Gentoo/var/tmp/portage/app-shells/bash-completion-1.2/work/bash-completion-1.2/test/fixtures/_filedir/ total 0 drwxr-xr-x 10 340 Jun 13 12:21 . drwxr-xr-x 20 680 Jun 13 12:21 .. drwxr-xr-x 3 102 Jun 13 12:21 a b drwxr-xr-x 3 102 Jun 13 12:21 a"b drwxr-xr-x 3 102 Jun 13 12:21 a$b drwxr-xr-x 3 102 Jun 13 12:21 a&b drwxr-xr-x 3 102 Jun 13 12:21 a'b drwxr-xr-x 3 102 Jun 13 12:21 ab drwxr-xr-x 3 102 Jun 13 12:21 aé drwxr-xr-x 7 238 Jun 13 12:21 ext
Thanks for filing the report. Basically, we'd have to provide a custom tarball that doesn't include the test/ subdir. I'm not happy with doing that maintenance overhead for one platform.
(In reply to comment #1) > My suspicion is that it actually doesn't like the directory names, > drwxr-xr-x 3 102 Jun 13 12:21 a b > drwxr-xr-x 3 102 Jun 13 12:21 a"b > drwxr-xr-x 3 102 Jun 13 12:21 a$b > drwxr-xr-x 3 102 Jun 13 12:21 a&b > drwxr-xr-x 3 102 Jun 13 12:21 a'b (In reply to comment #2) > Basically, we'd have to provide a custom tarball that doesn't include the test/ > subdir. I'm not happy with doing that maintenance overhead for one platform. IMO this is an upstream bug: Creating directories with specific names to test whether creating directories with specific names works actually should be done within a testcase, not within the tarball at all. Or what else are these directory names for within the tarball?
Is this a problem with 2.1-r1?
just tried to unpack 2.1 on interix: wamas test $ tar xfj ~/bash-completion-2.1.tar.bz2 tar: bash-completion-2.1/test/fixtures/_filedir/a"b: Cannot mkdir: No such file or directory tar: bash-completion-2.1/test/fixtures/_filedir/a"b: Cannot mkdir: No such file or directory tar: bash-completion-2.1/test/fixtures/_filedir/a"b/d: Cannot open: No such file or directory tar: Exiting with failure status due to previous errors
state of interix is unknown
