After executing env FEATURES="-collision-protect" emerge --oneshot portage (code listing 1.11 in Gentoo prefix guide for OS X),portage-2.2.00.13878 fails in make install due to '\' problem as in earlier bug. >>> Install portage-2.2.00.13878 into /Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/image/Users/msears/Gentoo/ category sys-apps make DESTDIR=/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/image/ install Making install in src make[1]: Entering directory `/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/work/prefix-portage-2.2.00.13878/src' make[2]: Entering directory `/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/work/prefix-portage-2.2.00.13878/src' make[3]: Entering directory `/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/work/prefix-portage-2.2.00.13878/src' test -z "/Users/msears/Gentoo/usr/lib/portage/bin" || /Users/msears/Gentoo/bin/mkdir -p "/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/image//Users/msears/Gentoo/usr/lib/portage/bin" /Users/msears/Gentoo/usr/bin/install -c chpathtool '/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/image//Users/msears/Gentoo/usr/lib/portage/bin' make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/work/prefix-portage-2.2.00.13878/src' make[2]: Leaving directory `/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/work/prefix-portage-2.2.00.13878/src' make[1]: Leaving directory `/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/work/prefix-portage-2.2.00.13878/src' Making install in man make[1]: Entering directory `/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/work/prefix-portage-2.2.00.13878/man' make[2]: Entering directory `/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/work/prefix-portage-2.2.00.13878/man' make[2]: Nothing to be done for `install-exec-am'. test -z "/Users/msears/Gentoo/usr/share/man/man1" || /Users/msears/Gentoo/bin/mkdir -p "/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/image//Users/msears/Gentoo/usr/share/man/man1" /Users/msears/Gentoo/usr/bin/install -c -m 644 dispatch-conf.1 ebuild.1 egencache.1 emaint.1 emerge.1 env-update.1 etc-update.1 quickpkg.1 repoman.1 '/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/image//Users/msears/Gentoo/usr/share/man/man1' test -z "/Users/msears/Gentoo/usr/share/man/man5" || /Users/msears/Gentoo/bin/mkdir -p "/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/image//Users/msears/Gentoo/usr/share/man/man5" /Users/msears/Gentoo/usr/bin/install -c -m 644 chpathtool.5 color.map.5 ebuild.5 make.conf.5 portage.5 '/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/image//Users/msears/Gentoo/usr/share/man/man5' make[2]: Leaving directory `/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/work/prefix-portage-2.2.00.13878/man' make[1]: Leaving directory `/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/work/prefix-portage-2.2.00.13878/man' Making install in bin make[1]: Entering directory `/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/work/prefix-portage-2.2.00.13878/bin' /Users/msears/Gentoo/usr/bin/install -c -d -m 755 -o "msears" -g "BRYNMAWRdomain users" /Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/image//Users/msears/Gentoo/usr/lib/portage/bin /Users/msears/Gentoo/usr/bin/install: invalid group `BRYNMAWRdomain users' make[1]: *** [install] Error 1 make[1]: Leaving directory `/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/work/prefix-portage-2.2.00.13878/bin' make: *** [install-recursive] Error 1 * ERROR: sys-apps/portage-2.2.00.13878 failed: * make install failed. * * Call stack: * ebuild.sh: 64: <call src_install> * environment:2632: emake DESTDIR="${D}" install || die "make install failed."; * * If you need support, post the topmost build error, and the call stack if relevant. >>> Failed to emerge sys-apps/portage-2.2.00.13878, Log file: >>> '/Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/temp/build.log' * Messages for package sys-apps/portage-2.2.00.13878: * ERROR: sys-apps/portage-2.2.00.13878 failed: * make install failed. * * Call stack: * ebuild.sh: 64: <call src_install> * environment:2632: emake DESTDIR="${D}" install || die "make install failed."; * * If you need support, post the topmost build error, and the call stack if relevant. Reproducible: Always Steps to Reproduce: 1. env FEATURES="-collision-protect" emerge --oneshot portage Actual Results: see above Expected Results: portage installed
what's your current portage version? emerge --version
Portage 2.2.00.13878-prefix (prefix/darwin/macos/10.5/x86, gcc-4.2.1, unavailable, 9.7.1 i386)
is the information in pym/portage/const_autotool.py correct?
Yes: EPREFIX = "/Users/msears/Gentoo" SYSCONFDIR = "/Users/msears/Gentoo/etc" DATADIR = "/Users/msears/Gentoo/usr/share" PORTAGE_BASE = "/Users/msears/Gentoo/usr/lib/portage" portagegroup = "BRYNMAWR\domain users" portageuser = "msears" rootuser = "msears" rootuid = 273009453 rootgid = 1612776775 PORTAGE_BASH = "/Users/msears/Gentoo/bin/bash" PORTAGE_MV = "/Users/msears/Gentoo/bin/mv"
can you attach the config.log file from var/tmp/portage/sys-apps/portage-2.2.00.13878/work please?
Created attachment 200160 [details] config.log
hmmmm, that's strange, but indeed wrong.
is grep PORTAGE_GROUP $EPREFIX/etc/make.globals returning what you would expect?
yes: PORTAGE_GROUP="BRYNMAWR\domain users"
I'm starting to get lost
yikes...not good
can you also attach the logfile from /Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/temp/
Created attachment 200161 [details] build log
can you bzgrep through the environment.bz2 file in that same dir for PORTAGE_GROUP please?
grep PORTAGE_GROUP environment econf --with-portage-user="${PORTAGE_USER:-portage}" --with-portage-group="${PORTAGE_GROUP:-portage}" --with-root-user="${rootuser}" --with-offset-prefix="${EPREFIX}" --with-default-path="${defaultpath}" || die "econf failed";
does portage emerge when etc/make.globals is changed to PORTAGE_GROUP='BRYNMAWR\domain users'
No, PORTAGE_GROUPS is (was) set to "BRYNMAWR\domain user"
users that is
so if you change from double quotes to single quotes it still fails? what if you change the single backslash into a double backslash?
double backslash worked (single quotes made no difference)
scratch that needed single quotes AND double backslash
looks like I have a working portage/gentoo prefix now...Thanks!!!
what is the final situation? you always need double backslashes?
if you edit pym/portage/const_autotool.py and insert a double backslash there too, does portage still work?
1. Always need single quote, double backslashes in make.globals 2. Editing pym/portage/const_autotool.py has no effect (doesn't compile).
I'm affraid this is still a problem?
it apparently is *** This bug has been marked as a duplicate of bug 285720 ***
