| 1 |
use "glsa-check -f package" on each offender first. It will safely |
| 2 |
remove the bad packages. |
| 3 |
|
| 4 |
Due to its history of breaking systems, depclean should be left until |
| 5 |
absolutely necessary. |
| 6 |
|
| 7 |
BillK |
| 8 |
|
| 9 |
On Sat, 2005-09-10 at 15:35 -0700, Ben Munat wrote: |
| 10 |
> Owen Ford wrote: |
| 11 |
> > On Sat, 2005-09-10 at 11:49 -0700, Ben Munat wrote: |
| 12 |
> > |
| 13 |
> >>First, glsa-check claims that I'm vulnerable to 200412-02 and 200505-01. The first is |
| 14 |
> >>pdflib and the second is various horde packages. However, I have the current versions of |
| 15 |
> >>these installed -- the versions that the glsa says I need to solve the vulnerability. So, |
| 16 |
> >>why would glsa-check say I'm vulnerable when I'm not? |
| 17 |
> > |
| 18 |
> > |
| 19 |
> > There are probably versions of those packages slotted. I use emerge -Cp |
| 20 |
> > package to see which are installed. |
| 21 |
> > |
| 22 |
> |
| 23 |
> Very good... exactly the problem. Thanks. |
| 24 |
> |
| 25 |
> As for dealing with all my orphaned packages, I'm figuring on going through the output of |
| 26 |
> "emerge --depclean" and unmerging everything that comes up with no dependencies under |
| 27 |
> "equery depends" and is something that I don't think I'll use. Does that sound reasonable? |
| 28 |
> |
| 29 |
> Oh, and I'm assuming that "equery depends" just checks for installed packages that depend |
| 30 |
> on the given package... anyone know any way to check a package's dependency against the |
| 31 |
> entire portage tree? |
| 32 |
> |
| 33 |
> b |
| 34 |
-- |
| 35 |
gentoo-server@g.o mailing list |
Archives