Gentoo Archives: gentoo-security

From: Aleksey V Lazar <lazar@××××.edu>
To: Robert Buchholz <rbu@g.o>
Cc: "gentoo-security@l.g.o" <gentoo-security@l.g.o>
Subject: Re: [gentoo-security] Security project meeting summary
Date: Wed, 13 May 2009 23:05:59
Message-Id: 4A0B4EA2.7010609@mnsu.edu
In Reply to: Re: [gentoo-security] Security project meeting summary by Robert Buchholz
Robert Buchholz wrote:
> 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 >
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. -- Aleksey V. Lazar Website Development Minnesota State University

Replies

Subject Author
Re: [gentoo-security] Security project meeting summary Peter Volkov <pva@g.o>