Hmmm, yum offering up an older kernel than is currently installed.

[Thorsten Leemhuis]

On 29.09.2008 18:15, M A Young wrote:
> On Mon, 29 Sep 2008, Rodd Clarkson wrote:
> ...
>> ---> Package kmod-nvidia.i686 0:173.14.12-4.lvn9 set to be updated
>> --> Processing Dependency: kmod-nvidia-2.6.26.3-29.fc9.i686 = 173.14.12-4.lvn9 for package: kmod-nvidia
> ...
>> ---> Package kmod-nvidia-2.6.26.3-29.fc9.i686.i686 0:173.14.12-4.lvn9 
> set to be updated
>> --> Processing Dependency: kernel-uname-r = 2.6.26.3-29.fc9.i686 for package: kmod-nvidia-2.6.26.3-29.fc9.i686
>> --> Running transaction check
>> ---> Package kernel.i686 0:2.6.26.3-29.fc9 set to be installed
>> --> Finished Dependency Resolution
> ...
>> Transaction Check Error:
>>  package kernel-2.6.26.5-39.fc9.i686 (which is newer than kernel-2.6.26.3-29.fc9.i686) is already installed
>>  package kernel-2.6.26.5-45.fc9.i686 (which is newer than kernel-2.6.26.3-29.fc9.i686) is already installed
> 
> What is going on is that the most recent kernel acceptable to the livna 
> kmod-nvidia module isn't installed, so yum tries to drag it in, only to 
> fail because more recent kernels are already installed. So basically, yum 
> is doing something sensible, but the livna repository doesn't have 
> updates-testing kernel support.

Correct afaics. Normally that doesn't result in problems like these, but 
the two weeks buildsys outage livna had lead to this error.

Further: The plan is to have suppose for updates-testing in RPM Fusion soon.

Workaround for now:

# rpm -e kmod-nvidia --nodeps
# yum install akmod-nvidia

HTH

Cu
knurd