1 |
On Wednesday 13 May 2009, Aleksey V Lazar wrote: |
2 |
> Robert Buchholz wrote: |
3 |
> > On Tuesday 29 July 2008, Bill wrote: |
4 |
> >>> Currently (to the best of my understanding) there is no easy way |
5 |
> >>> (e.g.: an /emerge/ option) to identify and update only the |
6 |
> >>> packages that have security fixes. |
7 |
> >> |
8 |
> >> This doesn't work anymore? |
9 |
> >> |
10 |
> >> 1. emerge --sync (emerge-webrsync) |
11 |
> >> 2. glsa-check -p affected |
12 |
> >> 3. glsa-check -f affected |
13 |
> >> 4. env-update |
14 |
> >> 5. revdep-rebuild |
15 |
> > |
16 |
> > GLSA support has also been integrated into Portage 2.2, so you can |
17 |
> > do something along the lines of |
18 |
> > # emerge --update @security |
19 |
> |
20 |
> This no longer seems to work for me. Is there a new way to |
21 |
> accomplish the task? |
22 |
|
23 |
Which Portage version are you on, specifically? If it is Portage 2.2, |
24 |
this might be a bug. If it is Portage 2.1, you are not using a recent |
25 |
enough Portage version. |
26 |
|
27 |
|
28 |
Robert |