| 1 |
Peter Volkov wrote: |
| 2 |
> В Срд, 13/05/2009 в 17:50 -0500, Aleksey V Lazar пишет: |
| 3 |
> |
| 4 |
> |
| 5 |
>> I'm using Portage version 2.1.6.13 right now. I know for a fact that |
| 6 |
>> I've used the emerge --update @security command before (right around |
| 7 |
>> 29 July 2008). The command stopped working since then, apparently. |
| 8 |
>> Thanks. |
| 9 |
>> |
| 10 |
> |
| 11 |
> Check your emerge.log. You had portage-2.2* installed at that time. |
| 12 |
> portage-2.2 was hard masked later to force all users downgrade to |
| 13 |
> portage-2.1.6 - portage branch with backported stable features from |
| 14 |
> portage-2.2. If you still wish to use emerge --update @security you'll |
| 15 |
> have manually unmask portage-2.2 using /etc/portage/package.unmask (see |
| 16 |
> handbook and/or man portage for more info). But note, portage-2.2 was |
| 17 |
> masked for a reason ;) |
| 18 |
> |
| 19 |
> |
| 20 |
This explains it. Thanks, Peter. |
| 21 |
|
| 22 |
-- |
| 23 |
Aleksey V. Lazar |
Archives