Re: rpm 4.2

I think I have one final question, is it possible to install the rpm
provided by the specific advisory and not necessarily the most recent
version of the package associated with the advisory?

For example:

RHBA-2004:265-23 bugfix   bash-2.05b-29.0.3.i386
RHBA-2005:437-11 bugfix   bash-2.05b-41.4.i386
RHBA-2006:0064-02 bugfix   bash-2.05b-41.5.i386
RHBA-2006:0311-04 bugfix   bash-2.05b-41.7.i386

Say I had change control in place and only bash version 2.05b-41.5 was
approved, can I install that version using yum and yum-security based on the
advisory?

'yum update --advisory=RHBA-2006:0064-02' will install bash-2.05b-41.7,
which I don't want. Is there a plug-in or a configuration option that will
allow me to deploy the packages provided by the advisory?

On Wed, Mar 11, 2009 at 12:58 PM, James Antill <[email protected]> wrote:

> Joshua Bahnsen <[email protected]> writes:
>
> > Actually my needs have changed. I was wondering if there was a way to
> > display all unpatched advisories using yum-security from yum-utils
> 1.1.14?
> > Newer versions will display all packages that are not patched
> unfortunately
> > this does not work with yum 3.2.8.
>
>  You could try backporting get_applicable_notices() from update_md.py,
> I _think_ that's all the newer yum-security plugin needs from the
> newer yum core (there might be a couple of other deps. though, for
> formatting ... just backport the older code from the older
> yum-security plugin).
>
>  I'm prepared to be wrong though :)
>
> --
> James Antill -- [email protected]
> _______________________________________________
> Yum mailing list
> [email protected]
> http://lists.baseurl.org/mailman/listinfo/yum
>

_______________________________________________
Yum mailing list
[email protected]
http://lists.baseurl.org/mailman/listinfo/yum