On 6/10/07, Michael Sullivan <[EMAIL PROTECTED]> wrote:
The last several times I've run glsa-check, it's
recommended that I emerge a package that portage
claims is already installed on my system:
camille ~ # glsa-check -t all
This system is affected by the following GLSAs:
200705-03
camille ~ # glsa-check -p 200705-03
Checking GLSA 200705-03
www-servers/tomcat-5.5.23-r1 (5.0.27-r6)
camille ~ # emerge -pv www-servers/tomcat
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] www-servers/tomcat-5.5.23-r1 USE="doc
examples -admin -java5 -source -test" 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0
kB
Its possible ( somehow ) you have dupe/stale tomcats lying around.
You tried
emerge -C "<www-servers/tomcat-5.5.22"
just to ensure this?, cos it looks like glsa-check sees 5.0.27 somewhere ^^;
strace -e trace=file glsa-check -p 200705-03 2>&1 | grep -v
"\(python\|pym\|pkg\|.py\|.pyc\|.so\|portage\|bin\)"
doesn't seem to list any files 'out of the ordinary' which get queried
for existance by that gtsa-check, so I /assume/ its all just portage
DB.
--
Kent
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
print "enNOSPicAMreil [EMAIL PROTECTED]"[(2*x)..(2*x+1)]}'
--
[EMAIL PROTECTED] mailing list
