1 |
Robert Buchholz wrote: |
2 |
> On Wednesday 13 May 2009, Aleksey V Lazar wrote: |
3 |
> |
4 |
>> Robert Buchholz wrote: |
5 |
>> |
6 |
>>> On Tuesday 29 July 2008, Bill wrote: |
7 |
>>> |
8 |
>>>>> Currently (to the best of my understanding) there is no easy way |
9 |
>>>>> (e.g.: an /emerge/ option) to identify and update only the |
10 |
>>>>> packages that have security fixes. |
11 |
>>>>> |
12 |
>>>> This doesn't work anymore? |
13 |
>>>> |
14 |
>>>> 1. emerge --sync (emerge-webrsync) |
15 |
>>>> 2. glsa-check -p affected |
16 |
>>>> 3. glsa-check -f affected |
17 |
>>>> 4. env-update |
18 |
>>>> 5. revdep-rebuild |
19 |
>>>> |
20 |
>>> GLSA support has also been integrated into Portage 2.2, so you can |
21 |
>>> do something along the lines of |
22 |
>>> # emerge --update @security |
23 |
>>> |
24 |
>> This no longer seems to work for me. Is there a new way to |
25 |
>> accomplish the task? |
26 |
>> |
27 |
> |
28 |
> Which Portage version are you on, specifically? If it is Portage 2.2, |
29 |
> this might be a bug. If it is Portage 2.1, you are not using a recent |
30 |
> enough Portage version. |
31 |
> |
32 |
> |
33 |
> Robert |
34 |
> |
35 |
I'm using Portage version 2.1.6.13 right now. I know for a fact that |
36 |
I've used the emerge --update @security command before (right around 29 |
37 |
July 2008). The command stopped working since then, apparently. Thanks. |
38 |
|
39 |
-- |
40 |
Aleksey V. Lazar |
41 |
Website Development |
42 |
Minnesota State University |