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