Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Peter Volkov wrote:
<blockquote cite="mid:1243581585.22483.2039.camel@localhost
" type="cite">
<pre wrap="">В Срд, 13/05/2009 в 17:50 -0500, Aleksey V Lazar пишет:
</pre>
<blockquote type="cite">
<pre wrap="">I'm using Portage version 2.1.6.13 right now. I know for a fact that
I've used the emerge --update @security command before (right around
29 July 2008). The command stopped working since then, apparently.
Thanks.
</pre>
</blockquote>
<pre wrap=""><!---->
Check your emerge.log. You had portage-2.2* installed at that time.
portage-2.2 was hard masked later to force all users downgrade to
portage-2.1.6 - portage branch with backported stable features from
portage-2.2. If you still wish to use emerge --update @security you'll
have manually unmask portage-2.2 using /etc/portage/package.unmask (see
handbook and/or man portage for more info). But note, portage-2.2 was
masked for a reason ;)
</pre>
</blockquote>
This explains it. Thanks, Peter.<br>
<pre class="moz-signature" cols="72">--
Aleksey V. Lazar
</pre>
</body>
</html>
|
|
