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
The
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 ~ #
--- Kent Fredric [EMAIL PROTECTED] wrote:
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
Kent Fredric writes:
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:
[...]
Its possible ( somehow ) you have dupe/stale tomcats lying around.
On Saturday 09 June 2007 21:50:14 Alex Schuster wrote:
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 ^^;
Any idea how this can happen? Aborted emerges or what? But shouldn't
emerge clean, or auto-clean which
On 6/10/07, Alex Schuster [EMAIL PROTECTED] wrote:
Kent Fredric writes:
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:
[...]
Its possible (
6 matches
Mail list logo
