glsa-check -f all fixing 200410-30 >>> merging kde-base/kdegraphics-3.3.1-r1 Calculating dependencies !!! All ebuilds that could satisfy "=kde-base/kdegraphics-3.3.1-r1" have been masked. !!! One of the following masked packages is required to complete your request: - kde-base/kdegraphics-3.3.1-r1 (masked by: ~x86 keyword) emerge kdegraphics -vp These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] kde-base/kdegraphics-3.3.0-r1 +arts -debug +gphoto2 +imlib -jpeg2k +opengl -povray +scanner -tetex -xinerama 0 kB Total size of downloads: 0 kB This is strange because glsa-check want to install kde-base/kdegraphics-3.3.1-r1 although kdegraphics-3.3.0-r1 is installed (3.3.0-r1 is not vurnerable). It should just skip this glsa. Knowing that I'm not vurnerable I want to inject this glsa glsa-check -i 200410-30 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. injecting 200410-30 glsa-check -f all fixing 200410-30 >>> merging kde-base/kdegraphics-3.3.1-r1 Calculating dependencies !!! All ebuilds that could satisfy "=kde-base/kdegraphics-3.3.1-r1" have been masked. !!! One of the following masked packages is required to complete your request: - kde-base/kdegraphics-3.3.1-r1 (masked by: ~x86 keyword) Conclusion: it's not possible to inject glsa's anymore. Before portage 2.0.51 this worked without problem. I hope this can be fixed soon, because I think Gentoo is leading when it comes to release sa's. However if the tools are lacking to administer glsa's Gentoo loses one of the most important feature.
Try 'new' instead of 'all'.
Hi Marius, Thanks for the reply and for glsa-check. Using `new` I'm indeed able to skip the incorrect merges. This leaves only one problem; glsa-check wants to install keyword masked ebuilds, do you have any idea how to fix this problem? Thanks! BTW, I thought that glsa-check should be replaced by `emerge security` do you have any update on that?
So the original bug is invalid, there is already a different bugreport for the 'merging masked packages' symptom. As for `emerge security`: I wanted to wait for the API that was originally planned for 2.0.51 but got postponed later, but the code has still bugs like this so maybe that was a good decision after all.