View previous topic :: View next topic |
Author |
Message |
exeral n00b
Joined: 23 Jan 2013 Posts: 8
|
Posted: Wed Jan 23, 2013 8:41 am Post subject: [solved] glsa-check still complaining |
|
|
Hi everybody
I upgraded firefox to 10.0.11 due to glsa alert
but glsa-check is still complaining:
Quote: | root@server:~# glsa-check -l affected
[A] means this GLSA was marked as applied (injected),
[U] means the system is not affected and
[N] indicates that the system might be affected.
201301-01 [N] Mozilla Products: Multiple vulnerabilities ( mail-client/mozilla-thunderbird-bin mail-client/thunderbird net-libs/xulrunner-bin ... )
|
Quote: | root@server:~# glsa-check -p affected
Checking GLSA 201301-01
>>> No upgrade path exists for these packages:
net-libs/xulrunner-1.9.2.20 |
Quote: | root@server:~# glsa-check -f affected
Fixing GLSA 201301-01
>>> cannot fix GLSA, no unaffected packages available |
Quote: | root@server~# eix -I xul
No matches found. |
What can I do
thanks
Last edited by exeral on Wed Jan 23, 2013 1:08 pm; edited 1 time in total |
|
Back to top |
|
|
Veldrin Veteran
Joined: 27 Jul 2004 Posts: 1945 Location: Zurich, Switzerland
|
Posted: Wed Jan 23, 2013 11:05 am Post subject: |
|
|
From the output, it seems, that you still have xulrunner installed.
IIRC it is no longer required for Firefox & Co and therefore safe to remove: emerge -C xulrunner or emerge -ac
be careful with the latter command, as it checks for any obsolete package.
It is not showing up in eix, as eix uses only ebuilds from the portage trees/overlays.
V. _________________ read the portage output!
If my answer is too concise, ask for an explanation. |
|
Back to top |
|
|
exeral n00b
Joined: 23 Jan 2013 Posts: 8
|
Posted: Wed Jan 23, 2013 1:07 pm Post subject: |
|
|
thank you ! problem solved
but i don't undertsand
Quote: | eix uses only ebuilds from the portage trees/overlays |
|
|
Back to top |
|
|
Veldrin Veteran
Joined: 27 Jul 2004 Posts: 1945 Location: Zurich, Switzerland
|
Posted: Wed Jan 23, 2013 10:46 pm Post subject: |
|
|
the eix database is built from the ebuilds available in the portage tree (and overlays). if an ebuild gets entirely removed from the portage tree, eix will no longer list it, and therefore not able to help you find it.
In you case, xulrunner was used by firefox, but more recent versions do not need it anymore (as is provided directly by firefox), but at the same time it was not mandatory to remove it. so over time, when old version which required xulrunner got removed from the portage tree, xulrunner was also removed, and thus gets no longer listed in eix.
I hope that clarifies it.
V. _________________ read the portage output!
If my answer is too concise, ask for an explanation. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|