This is a complicated one to explain. I am doing an emerge -auDNtv and now I have the following output: ———————————————————————————————————————————————————————————— These are the packages that would be merged, in reverse order: Calculating dependencies ... done! [nomerge ] sys-apps/lm_sensors-2.10.7 USE="sensord" [0] [nomerge ] net-analyzer/rrdtool-1.3.8 USE="doc nls perl python -rrdcgi -ruby -tcl" [0] [ebuild R ] x11-libs/pango-1.24.5-r1 USE="doc* test* -X -debug" 0 kB [0] [nomerge ] dev-haskell/hashed-storage-0.3.9 USE="doc hscolour test -profile" [1] [nomerge ] dev-haskell/test-framework-quickcheck2-0.2.4 USE="doc hscolour -profile" [1] [ebuild N ] dev-haskell/quickcheck-2.1.0.3 USE="doc hscolour -profile" 0 kB [1] [ebuild R ] app-portage/layman-1.2.3 USE="subversion test* -git" 0 kB [0] [ebuild U ] app-portage/eix-0.20.1 [0.19.2] USE="bzip2 doc hardened nls -debug -optimization -sqlite -strong-optimization -tools" 399 kB [0] [nomerge ] x11-libs/pango-1.24.5-r1 USE="doc* test* -X -debug" [0] [ebuild N ] x11-libs/libXft-2.1.14 USE="-debug" 283 kB [0] [ebuild N ] x11-libs/libXrender-0.9.5 USE="-debug" 256 kB [0] [ebuild N ] x11-libs/libXext-1.0.5 USE="-debug" 265 kB [0] [ebuild N ] x11-libs/libX11-1.2.2 USE="xcb -debug -ipv6" 1,833 kB [0] [ebuild N ] x11-libs/libxcb-1.4-r1 USE="doc -debug (-selinux)" 299 kB [0] [ebuild R ] dev-util/subversion-1.6.6 USE="bash-completion doc dso nls perl python sasl test* vim-syntax webdav-neon -apache2 -berkdb -ctypes-python -debug -emacs -extras -gnome-keyring -java -ruby -webdav-serf" 0 kB [0] [nomerge ] x11-libs/libxcb-1.4-r1 USE="doc -debug (-selinux)" [0] [nomerge ] app-doc/doxygen-1.5.8-r1 USE="doc -debug -latex -nodot -qt4" [0] [ebuild U ] media-gfx/graphviz-2.26.0 [2.24.0-r2] USE="doc examples java nls perl python -cairo -gtk -lasi -ruby -tcl" 16,550 kB [0] [ebuild N ] dev-libs/libpthread-stubs-0.1 USE="-debug" 190 kB [0] [ebuild N ] x11-libs/libXdmcp-1.0.3 USE="-debug" 251 kB [0] [ebuild N ] x11-libs/libXau-1.0.5 USE="-debug" 245 kB [0] [ebuild N ] x11-proto/xcb-proto-1.5 88 kB [0] [nomerge ] x11-libs/libXrender-0.9.5 USE="-debug" [0] [nomerge ] x11-libs/libX11-1.2.2 USE="xcb -debug -ipv6" [0] [ebuild N ] x11-libs/xtrans-1.2.5 USE="-debug" 139 kB [0] [ebuild N ] x11-proto/xf86bigfontproto-1.2.0 49 kB [0] [ebuild N ] x11-proto/xcmiscproto-1.2.0 48 kB [0] [ebuild N ] x11-proto/bigreqsproto-1.1.0 48 kB [0] [ebuild N ] x11-proto/kbproto-1.0.4 103 kB [0] [ebuild N ] x11-proto/renderproto-0.11 65 kB [0] [nomerge ] x11-libs/libXext-1.0.5 USE="-debug" [0] [ebuild N ] x11-proto/xextproto-7.0.5 79 kB [0] [ebuild N ] x11-proto/inputproto-1.5.1 61 kB [0] [ebuild N ] x11-proto/xproto-7.0.16 157 kB [0] [ebuild R ] sys-devel/binutils-2.18-r3 USE="nls test* -multislot -multitarget -vanilla" 0 kB [0] [ebuild U ] x11-misc/util-macros-1.5.0 [1.3.0] 58 kB [0] Total: 26 packages (3 upgrades, 19 new, 4 reinstalls), Size of downloads: 21,457 kB Portage tree and overlays: [0] /usr/portage [1] /usr/local/portage/layman/haskell ———————————————————————————————————————————————————————————— But my package.use includes: ———————————————————————————————————————————————————————————— # grep -i 'doc\|test' /etc/portage/package.use x11-libs/pango -doc -test dev-util/subversion -java -test app-portage/layman -test =sys-devel/binutils-2.18-r3 -test ———————————————————————————————————————————————————————————— Weirdly, when I execute # USE="-test" emerge -auDNtv world it honors it. But of course this means it will only honor it this time and for *all* packages. So what’s going on? Where is that USE flag enforced? (And why in the world would testing need X anyway?) :/ Reproducible: Always Steps to Reproduce: What else do you need? emerge --info is coming.
Created attachment 220721 [details] emerge --info
By the way: make.conf includes USE="${USE} doc -test" AND NOT FEATURES="test". BUT emerge --info says USE="test" is enabled!
Could you attach both your package.use and make.conf ? 'test' on pango needs libXft, so from that point on, everything is correct. The question is why those flags get set on pango.
Created attachment 220737 [details] make.conf Ok, here they come. :)
Created attachment 220739 [details] package.use Done.
Try not using USE as a storage var, so it's assigned only once.
(In reply to comment #6) > Try not using USE as a storage var, so it's assigned only once. I did not mention, that usually, USE="test" is enabled in make.conf, and only some packages have it disabled. I only disabled it in make.conf to test it. This worked for I think 2 years now. Only in the last week did it stop working. So I plan on leaving it enabled in make.conf, and still only disabling it for some packages in package.use. Which means, that even if your tip would work for make.conf, this would not help with package.use. :/
Just so we're on the same page: I was talking about USE="${USE} ..." construct. While it looks like it should work, I was trying to eliminate anything looking suspicious. Then again, you may be hitting some obscure bug related to your CFLAGS ("falign-functions=4 -fweb").
(In reply to comment #8) > I was talking about USE="${USE} ..." construct. > While it looks like it should work, I was trying > to eliminate anything looking suspicious. I know. :) And it’s a good point. :) But this is tried and tested for multiple systems over the last couple of years. And it worked nicely. I was planning to look into trying it without that construct anyway. So until then, you’re of course free to blame it on something new in portage wrecking that once working functionality. :) > Then again, you may be hitting some obscure bug > related to your CFLAGS ("falign-functions=4 -fweb"). Hmm, I thought these were pretty standard. But doing an emerge -p without them can’t hurt. I will try them out.
You should NOT use USE="test". That is controlled by FEATURES="test" ...
(In reply to comment #10) > You should NOT use USE="test". That is controlled by FEATURES="test" ... Yeah well, this was NOT the case when I started using it! Quoting “/usr/portage/profile/use.desc”: > test - Workaround to pull in packages needed to run with FEATURES=test. Portage-2.1.2 handles this internally, so don't set it in make.conf/package.use anymore Perhaps you should tell people before changing arbitrary things under their ass. I have problems like these all the time. I read the Gentoo newsletter, let portage e-mail me all emerge messages, read eselect news, and STILL miss half the important changes. By the way: Why are there a bazillion places to read news? Instead of one central point to read ALL the changes you as a user have to make, when updating certain packages or profiles. The amount of stuff I have to read, just to keep up halfways, is insane, compared to the actual amount of information needed to keep things working. And still there are packages not working, and lots of buggy stuff nearly every weekly sync... ON. A. HARDENED. SYSTEM! In this aspect, Gentoo is the WORST. DISTRO. EVER! It being free, is the only reason that I’m not going on a rampage over this. ;)
