eix-0.10.0 prints the version numbers of unstable packages in green (default) color although /etc/eixrc contains COLOR_UNSTABLE='yellow' and eix --dump also shows COLOR_UNSTABLE='yellow'. This error does not occur in eix-0.9.11 and eix-0.9.12. I did not change anything in standard /etc/eixrc and do not use an .eixrc. Reproducible: Always
emerge --info Portage 2.1.3.9 (default-linux/amd64/2007.0, gcc-4.1.2, glibc-2.6.1-r0, 2.6.22-g entoo-r7-galenos x86_64) ================================================================= System uname: 2.6.22-gentoo-r7-galenos x86_64 AMD Athlon(tm) 64 X2 Dual Core Pro cessor 4200+ Timestamp of tree: Tue, 25 Sep 2007 08:20:01 +0000 ccache version 2.4 [enabled] app-shells/bash: 3.2_p17-r1 dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4, 2.5.1-r2 dev-python/pycrypto: 2.0.1-r6 dev-util/ccache: 2.4-r7 sys-apps/baselayout: 1.12.10-r4 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.18 sys-devel/gcc-config: 1.4.0-r2 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.22-r2
I cannot reproduce this here - I see stable and unstable packages marked as usual. Some questions which might help to locate the problem: 1. Are you using ACCEPT_KEYWORDS=amd64 or x86 (in contrast to ~amd64 or ~x86)? 2. Does this really only concern the colors, i.e. do you see the "~" in front of unstable packages? 3. Does this concern all packages or only those (or not those) for which you have locally a different setting?
(In reply to comment #2) 1.) No.: ACCEPT_KEYWORDS="amd64 ~amd64" (from emerge --info) ACCEPT_KEYWORDS="~amd64" (in /etc/make.conf) 2.) I do NOT see the tilde ~ sign in front of unstable packages. Sorry that haven't noticed this before. 3.) The printout for ALL unstable packages is affected. I would like to add that I do not use extensive settings in /etc/portage/profile
I can confirm this bug. 1. I have ACCEPT_KEYWORDS="x86 ~x86". 2. I don't see tilde. 3. All packages.
It's not a bug, it's a feature :) The logic to determine the packages stability was completely rewritten in eix-0.10.0, and actually the previous behavior was false in your case: With ACCEPT_KEYWORDS=~ARCH all ~ARCH packages *are* stable; and they were even stable without your local settings in /etc/portage/*, so they are not even "ex-unstable". However, I can understand that you also want to consider ACCEPT_KEYWORDS as part of your "local settings" in your case, i.e. that the ~ARCH packages are considered as "ex-unstable". In current eix svn trunk (eix-0.10.1), I introduced a new variable ALWAYS_ACCEPT_KEYWORDS which when set to false will use only ARCH to determine the "original" stability. This is now the default to imitate the behavior of earlier eix versions to some extent.
(In reply to comment #5) > It's not a bug, it's a feature :) > > The logic to determine the packages stability was completely rewritten in > eix-0.10.0, and actually the previous behavior was false in your case: With > ACCEPT_KEYWORDS=~ARCH all ~ARCH packages *are* stable; and they were even No they are installable without any extra actions but they are _not_ stable. Anyway I now see that the bug I just filed at sf.net is a dupe of this so I closed that one.
(In reply to comment #6) > No they are installable without any extra actions but [...] This is exactly what eix considers as stable. This is reasonable, because eix should usually reflect the local setting and > they are _not_ stable. could not be influenced by the local setting. As a richer substitute, eix knows states like "ex-unstable", "ex-masked", "ex-system-masked".
