So I've been testing newer kernels from koji directly, and now my regular yum update is broken with this error. Am I mistaken, or shouldn't yum/rpm ignore older packages in the repo vs. the newer ones I have installed?
============================== Entering rpm code =============================== Running rpm_check_debug Running Transaction Test Finished Transaction Test
Transaction Check Error: package kernel-2.6.27.9-163.fc10.x86_64 (which is newer than kernel-2.6.27.9-159.fc10.x86_64) is already installed package kernel-2.6.28-0.131.rc8.git4.fc11.x86_64 (which is newer than kernel-2.6.27.9-159.fc10.x86_64) is already installed
Error Summary -------------
On Tue, 2008-12-23 at 22:06 -0500, Chuck Anderson wrote:
So I've been testing newer kernels from koji directly, and now my regular yum update is broken with this error. Am I mistaken, or shouldn't yum/rpm ignore older packages in the repo vs. the newer ones I have installed?
Sure, unless something else pulls it in anyways, such as a kmod.
On Tue, Dec 23, 2008 at 10:06:36PM -0500, Chuck Anderson wrote:
So I've been testing newer kernels from koji directly, and now my regular yum update is broken with this error. Am I mistaken, or shouldn't yum/rpm ignore older packages in the repo vs. the newer ones I have installed?
Transaction Check Error: package kernel-2.6.27.9-163.fc10.x86_64 (which is newer than kernel-2.6.27.9-159.fc10.x86_64) is already installed package kernel-2.6.28-0.131.rc8.git4.fc11.x86_64 (which is newer than kernel-2.6.27.9-159.fc10.x86_64) is already installed
I tracked this down to kmod-kqemu wanting a specific version of the kernel to be installed. I never had kernel -159 installed, but the latest kmod-kqemu from rpmfusion needs it.
I know that traditionally rpm doesn't like to install older packages than you already have unless you specify --oldpackage, but this seems to be causing a bug with yum. Yum or rpm should be allowing an older "installonly" package to be pulled in even when a newer package is already installed. Otherwise, you'll end up in this situation any time you don't follow the exact order of oldest...newest kernel version installs.
Is there any reason why yum shouldn't allow an older "installonly" package to be installed when you already have a newer one?
On Tue, 2008-12-23 at 22:20 -0500, Chuck Anderson wrote:
Is there any reason why yum shouldn't allow an older "installonly" package to be installed when you already have a newer one?
It's undefined territory. What should the %post do? Add the older kernel stanza as the latest one so by default you get the older kernel?
When you go off the reservation with packages, you keep all the pieces. This includes moving your kernel beyond what your kernel module provider has provided modules for.
On Tue, Dec 23, 2008 at 07:51:56PM -0800, Jesse Keating wrote:
On Tue, 2008-12-23 at 22:20 -0500, Chuck Anderson wrote:
Is there any reason why yum shouldn't allow an older "installonly" package to be installed when you already have a newer one?
It's undefined territory. What should the %post do? Add the older kernel stanza as the latest one so by default you get the older kernel?
Yes.
When you go off the reservation with packages, you keep all the pieces. This includes moving your kernel beyond what your kernel module provider has provided modules for.
Ok, I understand having to deal with stuff, but I'd rather deal with the grub.conf fixups than the "lets break all yum updates" stuff. Perhaps I should file an RFE at upstream yum.
On Tue, 2008-12-23 at 22:06 -0500, Chuck Anderson wrote:
So I've been testing newer kernels from koji directly, and now my regular yum update is broken with this error. Am I mistaken, or shouldn't yum/rpm ignore older packages in the repo vs. the newer ones I have installed?
Actually, it's been corrected in a different way in upstream.
For installonlypkgs it is okay to install the pkg specifically. It'll be oldpackaged in place.
-sv
-
Chuck Anderson -
Ignacio Vazquez-Abrams -
Jesse Keating -
Seth Vidal