[Valdis.Kletnieks at vt.edu]

On Sun, 20 Apr 2014 19:59:27 -0700, Amber Thrall said:
> I recently built and installed kernel version 3.15.0-rc1 following the
> KernelBuild article on kernelnewbies.org.  Everything went smooth and my
> system is running fine.  However when performing an update via (sudo yum
> update) the dependencies failed requiring
> "kernel-devel-uname-r=3.13.10".  uname-r returns "3.15.0-rc1" as
> expected.

Note that nothing below talks about 3.15.  You've apparently  installed it
outside of rpm/yum, which is perfectly OK - rpm and yum will silently
ignore kernel versions you've installed yourself. (Right now I have 3 Fedora
kernels and 4 or 5 different linux-next kernels all in /boot, works fine).

> Is there a way to get yum to recognize the latest kernel I built?  Or
> does that require updating the kernel's source RPM?

Actually, making yum notice the 3.15 kernel won't fix your problem.

> I'm running Fedora 20 and am new to kernel building.  Yum's error
> message is included below:
>
> Error: Package:
> 10:buildsys-build-rpmfusion-kerneldevpkgs-current-20-19.x86_64
> (rpmfusion-free-updates)
>            Requires: kernel-devel-uname-r = 3.13.10-200.fc20.x86_64
>            Installed: kernel-devel-3.11.10-301.fc20.x86_64 (@anaconda)
>                kernel-devel-uname-r = 3.11.10-301.fc20.x86_64
>            Installed: kernel-devel-3.13.9-200.fc20.x86_64 (@updates)
>                kernel-devel-uname-r = 3.13.9-200.fc20.x86_64

Your *real* problem is that you have an RPM from rpmfusion that wants
the 3.13.10-200 version of the kernel, but the two kernels known to rpm/yum
are the 3.11.10-301 that you installed originally, and a 3.13.9-200 version.
(And since the rpmfusion package wants *exactly* 3.13.10-200, telling yum
you have a 3.15 kernel won't make it happier).

You have several choices:

1) Find a 3.13.10-200 kernel from Fedora and install it. (This could be
difficult, as yum probably should have already found it for you).
2) remove the package from rpmfusion if you're not actually using it.
3) If you have an 'excludes = kernel*' in your yum.conf file to keep yum
from automatically updating your kernel, try 'yum --disableexcludes=all' to
see if that fixes the problem.
4) Ignore the issue until rpmfusion and Fedora agree again on what the latest
kernel is...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140421/48a2bb17/attachment.bin