Platform is Gentoo Prefix on SuSE Enterprise 10 SP2. Emerging gentoolkit-dev fails: emerge gentoolkit-dev ... ... make[1]: Entering directory `/local/scratch/portage/app-portage/gentoolkit-dev-0.2.7/work/gentoolkit-dev-0.2.7/src/imlate' install -m 0755 imlate /local/scratch/portage/app-portage/gentoolkit-dev-0.2.7/image/local/tmp/d//usr/bin/ install -m 0644 imlate.1 /local/scratch/portage/app-portage/gentoolkit-dev-0.2.7/image/local/tmp/d//usr/share/man/man1/ make[1]: Leaving directory `/local/scratch/portage/app-portage/gentoolkit-dev-0.2.7/work/gentoolkit-dev-0.2.7/src/imlate' >>> Completed installing gentoolkit-dev-0.2.7 into /local/scratch/portage/app-portage/gentoolkit-dev-0.2.7/image/local/tmp/d/ ecompressdir: bzip2 -9 /local/tmp/d/usr/share/man * prefixing shebang of local/tmp/d/usr/bin/ebump * prefixing shebang of local/tmp/d/usr/bin/echangelog * prefixing shebang of local/tmp/d/usr/bin/ekeyword * prefixing shebang of local/tmp/d/usr/bin/eshowkw * prefixing shebang of local/tmp/d/usr/bin/eviewcvs * QA Notice: the following files use invalid (possible non-prefixed) shebangs: * local/tmp/d/usr/bin/imlate:/usr/bin/python2.4 (in PATH but target not found) * ERROR: app-portage/gentoolkit-dev-0.2.7 failed: * Aborting due to QA concerns: invalid shebangs found The initial lines of the usr/bin/imlate file look like this: #!/usr/bin/python # Copyright 1999-2010 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Id: imlate 796 2010-07-18 20:28:12Z idl0r $ # Author: Christian Ruppert <idl0r@gentoo.org> # Python 2.6 compatibility from __future__ import print_function VERSION = "1.0.1"
does upgrading portage still work? I think this is actually a bug in portage that was resolved already
I tried to do `emerge --sync' followed by `emerge gentoolkit-dev' and `emerge portage' in a Prefix tree that was bootstrapped on November 5. Emerging gentoolkit-dev succeeded (version number 0.2.7 unchanged). Upgrading portage (from 2.2.01.17133 to 2.2.01.17168) failed with * ERROR: sys-apps/portage-2.2.01.17168 failed: * Aborting due to QA concerns: invalid shebangs found * * Call stack: * misc-functions.sh, line 1692: Called install_qa_check * misc-functions.sh, line 210: Called install_qa_check_prefix * misc-functions.sh, line 855: Called die * The specific snippet of code: * die "Aborting due to QA concerns: invalid shebangs found" * * If you need support, post the output of 'emerge --info =sys-apps/portage-2.2. 01.17168', * the complete build log and the output of 'emerge -pqv =sys-apps/portage-2.2.0 1.17168'. * The complete build log is located at '/local/scratch/portage/sys-apps/portage -2.2.01.17168/temp/build.log'. * The ebuild environment file is located at '/local/scratch/portage/sys-apps/po rtage-2.2.01.17168/temp/environment'. * S: '/local/scratch/portage/sys-apps/portage-2.2.01.17168/work/prefix-portage- 2.2.01.17168' !!! post install failed; exiting.
can't reporduce with same portage version, you'll need to provide more output
No longer a problem; gentoolkit-dev emerges fine today. Versions are: gentoolkit-dev: 0.2.8 portage: 2.2.01.17168