# qpkg -I -i glibc sys-libs/glibc-2.3.3.20040420-r1 * (which is not affected by 200408-16) # glsa-check -t all WARNING: This tool is completely new and not very tested, so it should not be used on production systems. It's mainly a test tool for the new GLSA release and distribution system, it's functionality will later be merged into emerge and equery. Please read http://www.gentoo.org/proj/en/portage/glsa-integration.xml before using this tool AND before reporting a bug. This system is affected by the following GLSA: 200410-07 but when executing glsa-check -f all sys-libs/glibc-2.3.4.20040808-r1 will be emerged btw: is vanilla 2.6.8.1 still affected by 200410-07? Reproducible: Always Steps to Reproduce: on any system with sys-libs/glibc-2.3.3.20040420-r1 installed: 1. emerge sync 2. glsa-check -t all 3. glsa-check -f all Actual Results:
Which gentoolkit version is that ? If it's pre8 please try with pre10.
yes, it's pre8... (sorry for omitting this detail) pre10 doesn't solve the problem because it still wants to upgrade glibc the only difference is that pre10 wants to emerge sys-libs/glibc-2.3.4.20041006 (which is masked) instead of sys-libs/glibc-2.3.4.20040808-r1
update: in the meantime glsa 200410-19 came out... i manually upgraded to glibc-2.3.3.20040420-r2 which is unaffected. (glsa-check would have been emerged sys-libs/glibc-2.3.4.20040808-r1 but i'm afraid upgrading glibc version on a production server) after that, "glsa-check -t all" says the system is still affected by 200410-19, consequently, a further "glsa-check -f all" would emerge glibc-2.3.4.20040808-r1 which isn't a desiderable feature :(
*** This bug has been marked as a duplicate of 68050 ***
