Re: Security project meeting summary

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iQIcBAABAgAGBQJKCfcmAAoJECaaHo/OfoM5XkQQALpfjgDR5qHSUMBItJKd1JeS
AjGGU/Eb0gzg+eLEKxHjKPad8hQngpo5hYi7cigP4DeazoaSkVr14sMZpzsqPH8b
OU04jd8DlDYxmkl1313WE0VfIYMrSh4CZwZZi/1HSlzZjqfx2xp/eJqjNEU2fcIE
pbmeIvlEzOjRX/ZWuCtgnvpb6JtI2f+Kx2e8Rm7JaRA6J80SEBiAn53CMtAS7ONC
ToCf+jJzZs/hhk4cpxUblb/REj6itYSrwW9jMKJ1jc1lUV2A2G/T2Ia0Nm3T+Dt2
VEkcdOdPtJ0/ZRU9hqR6cxrzNdrDfjLEJjAmOGtBt6SgLSNDlq0pI99oXrjimWP2
p1j8SfbTD8e03eZid6M4TvCMUDsIowZLOwS+9dQbB+RMXqFNBJMQei2xvmYG3aNX
7CZ4kMh4bPIozI8Cng61mzmYT+H+eVlFr9UfTM2/zvn77/7lx6dmNRh2yaO6Ny8B
8S4La8OlV0C+8rVfSPiuYD7eImCIUidspA1UWBQ1/myTIChatNvoLJI0yiHBOwIQ
Y/S1RdE+cT5PwrOTpuxcn5ty+VFCqyK0nwGVuRwaeeRwOyYQYDgOTuI3kuTx3Mo0
CjkpMj0UednScQpOEskxjk6iYH4tNPKBcUO920giw5zjY+ucOfa6ScTA5ceph+uV
9QB5l43EwEO7eiXaQCxK
=A7qR
-----END PGP SIGNATURE-----