this used to work, but it's been broken for a while $ emerge --version Portage 3.0.12 (python 3.7.7-final-0, default/linux/amd64/17.1/developer, gcc-10.2.0, glibc-2.31-r2, 5.7.1 x86_64) $ ebuild=$(equery which app-cdr/cdemu) $ FEATURES='-noauto' ebuild ${ebuild} clean setup unpack prepare * Using python3.8 to build >>> Not marked as unpacked; recreating WORKDIR... * Using python3.8 to build >>> Unpacking source... >>> Unpacking cdemu-client-3.2.4.tar.bz2 to /var/tmp/portage/app-cdr/cdemu-3.2.4/work >>> Source unpacked in /var/tmp/portage/app-cdr/cdemu-3.2.4/work >>> Checking cdemu-client-3.2.4.tar.bz2's mtime... >>> WORKDIR is up-to-date, keeping... >>> It appears that 'pretend' has already executed for 'cdemu-3.2.4'; skipping. >>> Remove '/var/tmp/portage/app-cdr/cdemu-3.2.4/.pretended' to force pretend. >>> It appears that 'setup' has already executed for 'cdemu-3.2.4'; skipping. >>> Remove '/var/tmp/portage/app-cdr/cdemu-3.2.4/.setuped' to force setup. >>> It appears that 'unpack' has already executed for 'cdemu-3.2.4'; skipping. >>> Remove '/var/tmp/portage/app-cdr/cdemu-3.2.4/.unpacked' to force unpack. >>> Preparing source in /var/tmp/portage/app-cdr/cdemu-3.2.4/work/cdemu-client-3.2.4 ... * Working in BUILD_DIR: "/var/tmp/portage/app-cdr/cdemu-3.2.4/work/cdemu-3.2.4_build" * Fixing shebang in src/cdemu. >>> Source prepared. $ FEATURES='-noauto' ebuild ${ebuild} clean setup unpack prepare * Using python3.8 to build >>> Not marked as unpacked; recreating WORKDIR... >>> Unpacking source... >>> Unpacking cdemu-client-3.2.4.tar.bz2 to /var/tmp/portage/app-cdr/cdemu-3.2.4/work >>> Source unpacked in /var/tmp/portage/app-cdr/cdemu-3.2.4/work >>> Preparing source in /var/tmp/portage/app-cdr/cdemu-3.2.4/work/cdemu-client-3.2.4 ... * Working in BUILD_DIR: "/var/tmp/portage/app-cdr/cdemu-3.2.4/work/cdemu-3.2.4_build" * ERROR: app-cdr/cdemu-3.2.4::gentoo failed (prepare phase): * python_fix_shebang: EPYTHON unset (pkg_setup not called?)
> $ FEATURES='-noauto' ebuild ${ebuild} clean setup unpack prepare It looks like you passed FEATURES='-noauto', but the bug summary says FEATURES=noauto. Which value are you actually using?
(In reply to Mike Gilbert from comment #1) please read the whole report. both forms are provided to show that one works while the other (as reported) fails.
I did read the whole report. FEATURES='-noauto' appears in both examples.
I can reproduce the failure in the second example by replacing FEATURES='-noauto' with FEATURES='noauto'. I guess that was a copy/paste fail.
(In reply to Mike Gilbert from comment #4) thanks, the 2nd half is supposed to be FEATURES='noauto'. i had that originally, but the paste was corrupted, so i had to manually fix it. doesn't look like bugzilla allows fixing after the fact.
