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>
Robert Buchholz wrote:
<blockquote cite="mid:200905130024.38274.rbu@g.o" type="cite">
<pre wrap="">On Wednesday 13 May 2009, Aleksey V Lazar wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Robert Buchholz wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Tuesday 29 July 2008, Bill wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Currently (to the best of my understanding) there is no easy way
(e.g.: an /emerge/ option) to identify and update only the
packages that have security fixes.
</pre>
</blockquote>
<pre wrap=""> This doesn't work anymore?
1. emerge --sync (emerge-webrsync)
2. glsa-check -p affected
3. glsa-check -f affected
4. env-update
5. revdep-rebuild
</pre>
</blockquote>
<pre wrap="">GLSA support has also been integrated into Portage 2.2, so you can
do something along the lines of
# emerge --update @security
</pre>
</blockquote>
<pre wrap="">This no longer seems to work for me. Is there a new way to
accomplish the task?
</pre>
</blockquote>
<pre wrap=""><!---->
Which Portage version are you on, specifically? If it is Portage 2.2,
this might be a bug. If it is Portage 2.1, you are not using a recent
enough Portage version.
Robert
</pre>
</blockquote>
I'm using Portage version 2.1.6.13 right now. I know for a fact that
I've used the <tt>emerge --update @security </tt>command before
(right around 29 July 2008). The command stopped working since then,
apparently. Thanks.<br>
<br>
<pre class="moz-signature" cols="72">--
Aleksey V. Lazar
Website Development
Minnesota State University
</pre>
</body>
</html>
|
|
