Summary: | cannot disable FEATURES from command line | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sascha Silbe <sascha-gentoo-bugzilla> |
Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | henrik |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sascha Silbe
2005-01-26 05:55:00 UTC
Try FEATURES="-collision-protect" emerge foobar. WORKSFORME Same problem, after doing `cd /var/tmp/portage ; rm -rf *`? FYI: The second run shows exactly the same results, so it is reproducable. Regarding Comment #1: This is exactly what I did (see "Steps to Reproduce:"), but it didn't work. Regarding Comment #2: I'm trying that now. Still the same problem, even after "rm -rf /var/tmp/portage/*". I can also reproduce it with media-fonts/corefonts-1-r2, so it's not specific to xorg-x11. Just tried a few combinations: make.conf cmdline result 1. "" "" -CP 2. "" CP CP 3. "" -CP -CP 4. CP "" CP 5. CP CP CP 6. CP -CP CP 7. -CP "" -CP 8. -CP CP CP 9. -CP -CP -CP Only the 6. case works other than expected. I can't reproduce this. What portage version are you running? # emerge info | grep FEATURES FEATURES="buildpkg collision-protect confcache distlocks livecvsportage noinfo parallel-fetch sandbox" # FEATURES="-collision-protect" emerge info | grep FEATURES FEATURES="buildpkg confcache distlocks livecvsportage noinfo parallel-fetch sandbox" # FEATURES=-collision-protect emerge info | grep FEATURES FEATURES="buildpkg confcache distlocks livecvsportage noinfo parallel-fetch sandbox" Also try some other flags (strict, userpriv, ...), the relevant code is generic so if it doesn't work for collision-protect it shouldn't work for anything. I highly suspect something local (alias? bash-function?). I'm using the current stable for x86 (2.0.51-r15). For gcc etc. see "emerge info" output above. root@caravan:~# emerge info | grep FEATURES FEATURES="autoaddcvs autoconfig ccache collision-protect distlocks fixpackages maketest sandbox severe sfperms strict test userpriv usersandbox" root@caravan:~# FEATURES="-collision-protect" emerge info | grep FEATURES FEATURES="autoaddcvs autoconfig ccache collision-protect distlocks fixpackages maketest sandbox severe sfperms strict test userpriv usersandbox" root@caravan:~# FEATURES=-collision-protect emerge info | grep FEATURES FEATURES="autoaddcvs autoconfig ccache collision-protect distlocks fixpackages maketest sandbox severe sfperms strict test userpriv usersandbox" It also happens with other FEATURES on that host, so it's not collision-protect-specific: root@caravan:~# FEATURES=-ccache emerge info | grep FEATURES FEATURES="autoaddcvs autoconfig ccache collision-protect distlocks fixpackages maketest sandbox severe sfperms strict test userpriv usersandbox" A clean environment doesn't change anything, so it's not an environment variable, alias or shell function: root@caravan:~# env -i FEATURES=-collision-protect emerge info | grep FEATURES FEATURES="autoaddcvs autoconfig ccache collision-protect distlocks fixpackages maketest sandbox severe sfperms strict test userpriv usersandbox" There are no fancy files (like bashrc) in /etc/portage: root@caravan:~# ls -lR /etc/portage/ /etc/portage/: total 16 -rw-r--r-- 1 root root 34 Jan 17 21:26 mirrors -rw-r--r-- 1 root root 1235 Jan 17 21:36 package.keywords -rw-r--r-- 1 root root 261 Dec 31 16:00 package.use drwxrwsr-x 2 root portage 4096 Oct 21 22:31 sets /etc/portage/sets: total 0 root@caravan:~# Ok, so lets see if we can at least check wether this is portage specific: $ env|grep USER $ USER=foo env|grep USER If that does give the expected result the next level would be python: $ python -c 'import os; print os.environ["USER"]' $ USER=foo python -c 'import os; print os.environ["USER"]' That works fine so far: root@caravan:~# env|grep USER USER=root root@caravan:~# USER=foo env|grep USER USER=foo root@caravan:~# python -c 'import os; print os.environ["USER"]' root root@caravan:~# USER=foo python -c 'import os; print os.environ["USER"]' foo root@caravan:~# I can reproduce the problem here with sys-apps/portage-2.0.51-r15. sponge ~ # env|grep USER USER=root sponge ~ # USER=foo env|grep USER USER=foo sponge ~ # emerge info | grep FEATURES FEATURES="autoaddcvs autoconfig collision-protect cvs digest distlocks maketest sandbox sfperms strict test" sponge ~ # FEATURES="-collision-protect" emerge info | grep FEATURES FEATURES="autoaddcvs autoconfig collision-protect cvs digest distlocks maketest sandbox sfperms strict test" This problem only exists for disabling features currently enabled in /etc/make.conf it seems: sponge ~ # FEATURES="foo" emerge info | grep FEATURES FEATURES="autoaddcvs autoconfig collision-protect cvs digest distlocks foo maketest sandbox sfperms strict test" i can reproduce it with maketest in FEATURES. Replace it with 'test' and FEATURES=-collision-protect emerge info should work again. FEATURES="-collision-protect maketest" emerge info --->>> broken FEATURES="-collision-protect -maketest" emerge info --->>> working sed -i "s:maketest:test:" /etc/make.conf solved it here. I can confirm that replacing "maketest" with "test" in FEATURES "solves" this problem. /etc/make.conf.example lists maketest, but not test. So which one is correct? And why does it affect all other FEATURES in such a way? maketest is the old name, test is the new name Will be out in 2.0.51.18. This is broken in HEAD. Not sure if you want a new bug or not. kyoto root # FEATURES="-userpriv" emerge info Portage 1.574-cvs (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20040808-r1, 2.6.10-hardened-r3 i686) ================================================================= System uname: 2.6.10-hardened-r3 i686 AMD Athlon(tm) XP 1800+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 16 2005, 23:00:21)] distcc: No such file or directory [disabled] ccache: No such file or directory [enabled] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.8.5-r3, 1.5, 1.7.9-r1, 1.6.3, 1.4_p6, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="no" CFLAGS="-mcpu=athlon-xp -march=athlon-xp -O3 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-mcpu=athlon-xp -march=athlon-xp -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig buildpkg ccache confcache digest distlocks parallel-fetch sandbox sfperms" GENTOO_MIRRORS="http://gentoo.chem.wisc.edu/gentoo ftp://gentoo.chem.wisc.org/gentoo" MAKEOPTS="-j2" PKGDIR="/home/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="x86 3dnow X acpi alsa apm arts avi bash-completion berkdb bitmap-fonts bmp canna caps cdr cjk crypt cups curl dvd dvdr dvdread emboss encode esd ethereal f77 fam font-server foomaticdb fortran gdbm gif gpm gtk gtk2 imagemagick imap imlib ipv6 jpeg kde libg++ libwww lm_sensors mad maildir matroska mikmod mmx mono motif mp3 mpeg mysql ncurses nis nls nptl offensive oggvorbis openal opengl oss pam pdflib perl png posix python qt quicktime readline sdl spell sse ssl svg svga tcpd threads tiff truetype truetype-fonts type1-fonts wxwindows xml2 xmms xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS FEATURES output from emerge info shouldn't have Userpriv. Fixed 13 hours ago. :P ... and counting. Fixed on or before 2.0.51.22-r1 Looking through the batch of bugs, I'm not sure that some of these are actually fixed in stable. Others, the requirements have possibly changed after the initial fix was committed. If you think this bug has been closed incorrectly, please reopen or ask that it be reopened. I've reimplemented the fix for this in svn r3320 because the -* hack seems quite non-intuitive to me. |