Gentoo Archives: gentoo-security

From: Robert Buchholz <rbu@g.o>
To: gentoo-security@l.g.o
Cc: Aleksey V Lazar <lazar@××××.edu>, Bill <wviands@×××××××××××××××.edu>
Subject: Re: [gentoo-security] Security project meeting summary
Date: Tue, 12 May 2009 22:24:44
Message-Id: 200905130024.38274.rbu@gentoo.org
In Reply to: Re: [gentoo-security] Security project meeting summary by Aleksey V Lazar
On Wednesday 13 May 2009, Aleksey V Lazar wrote:
> Robert Buchholz wrote: > > On Tuesday 29 July 2008, Bill wrote: > >>> 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. > >> > >> 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 > > > > GLSA support has also been integrated into Portage 2.2, so you can > > do something along the lines of > > # emerge --update @security > > This no longer seems to work for me. Is there a new way to > accomplish the task?
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

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-security] Security project meeting summary Aleksey V Lazar <lazar@××××.edu>