2014-10-17 22:05 GMT+02:00 Sérgio Basto <sergio(a)serjux.com>:
> On Sex, 2014-10-17 at 10:27 -0600, Orion Poplawski wrote:
> > I think the provides for the kernel-debug-devel package is causing
> issues when
> > installing akmods:
> >
> > # repoquery --provides kernel-debug-devel
> > kernel-debug-devel = 3.16.6-200.fc20
> > kernel-debug-devel(x86-64) = 3.16.6-200.fc20
> > kernel-debug-devel-x86_64 = 3.16.6-200.fc20
> > kernel-devel = 3.16.6-200.fc20+debug
> > kernel-devel-uname-r = 3.16.6-200.fc20.x86_64+debug
> > kernel-devel-x86_64 = 3.16.6-200.fc20+debug
> >
> > --> Processing Dependency: kernel-devel-uname-r for package:
> > akmods-0.5.1-3.fc19.noarch
> > ---> Package kernel-debug-devel.x86_64 0:3.16.6-200.fc20 will be
> installed
> >
> > Why does the kernel-debug-devel package have kernel-devel* provides? Or
> > should akmods require something different?
> >
> >
https://bugzilla.redhat.com/show_bug.cgi?id=227533
>
> akmods needs the kernel-devel of running kernel system , but doesn't
> know at requires install time , so for me it is a bug , I usually say ,
> use yum install akmods-foo and kernel-devel of running kernel
> or like in
http://rpmfusion.org/Howto/nVidia#Akmods :
>
> yum install akmod-nvidia-96xx "kernel-devel-uname-r == $(uname -r)"
>
Best would be to have a yum/dnf plugin within akmod that would "emit" a
RPM dependency based on that kernel-devel-uname-r value.
There are probably few corner cases to work through such when there is a
new kernel/kernel-devel and the corresponding kernel-devel isn't there. In
this case it will need to pick the kernel-devel-uname-r from the
transaction.
Also this probably means that such plugin is installed "before" the
akmod-foo installation is requested.
Nicolas (kwizart)