How does one deal with obsoleted updates from updates-testing

2010-03-08 Thread Quentin Armitage
My F-13 system produces the following output from yum list extras: Extra Packages glibc.i686 2.11.90-14 installed glibc-common.i686 2.11.90-14 installed glibc-devel.i686 2.11.90-14 @updates-testing glibc-headers.i686

Re: How does one deal with obsoleted updates from updates-testing

2010-03-08 Thread Seth Vidal
On Mon, 8 Mar 2010, Quentin Armitage wrote: The glibc packages (including nscd) were in updates-testing, but have been obsoleted, and so 2.11.90-12 is now the current version again. What is the mechanism for becoming aware that a package that has been installed through updates-testing has

Re: How does one deal with obsoleted updates from updates-testing

2010-03-08 Thread Quentin Armitage
On Mon, 2010-03-08 at 10:26 -0500, Seth Vidal wrote: On Mon, 8 Mar 2010, Quentin Armitage wrote: The glibc packages (including nscd) were in updates-testing, but have been obsoleted, and so 2.11.90-12 is now the current version again. What is the mechanism for becoming aware that a

Re: How does one deal with obsoleted updates from updates-testing

2010-03-08 Thread James Antill
On Mon, 2010-03-08 at 18:54 +, Quentin Armitage wrote: On Mon, 2010-03-08 at 10:26 -0500, Seth Vidal wrote: On Mon, 8 Mar 2010, Quentin Armitage wrote: The glibc packages (including nscd) were in updates-testing, but have been obsoleted, and so 2.11.90-12 is now the current