Re: other question about kmod
Hi,
On Thu, 2012-03-29 at 14:09 -0600, Ken Dreyer wrote:
On Thu, Mar 29, 2012 at 2:00 PM, Richard Shaw
<hobbes1069(a)gmail.com> wrote:
> # repoquery --archlist=i386,i686 --provides kmod-VirtualBox-OSE-PAE
> VirtualBox-OSE-kmod = 4.1.8-1.fc16.16
> kmod-VirtualBox-OSE-PAE = 4.1.8-1.fc16.16
> kmod-VirtualBox-OSE-PAE(x86-32) = 4.1.8-1.fc16.16
>
> Why would the non-PAE package provide a PAE name?
It has to satisfy this line in the userspace VirtualBox-OSE.spec
93 Requires: %{name}-kmod = %{version}%{?prereltag}
kmod-foo is the actual kmod, versus
foo-kmod is a virtual "provides" to satisfy dependencies. Each kmod
varient provides it.
http://rpmfusion.org/Packaging/KernelModules/Kmods2#kmodtool
Kmods make me cross-eyed sometimes :)
But in Sergio's case, when I install VirtualBox-OSE, it already pulls
in the appropriate kmod- package:
yum install VirtualBox-OSE
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package VirtualBox-OSE.i686 0:4.1.8-1.fc15 will be installed
--> Processing Dependency: VirtualBox-OSE-kmod = 4.1.8 for package:
VirtualBox-OSE-4.1.8-1.fc15.i686
--> Processing Dependency: libgsoap++.so.0 for package:
VirtualBox-OSE-4.1.8-1.fc15.i686
--> Running transaction check
---> Package gsoap.i686 0:2.7.17-4.fc15 will be installed
---> Package kmod-VirtualBox-OSE-2.6.42.12-1.fc15.i686.PAE.i686
0:4.1.8-1.fc15.10 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
VirtualBox-OSE i686 4.1.8-1.fc15 rpmfusion-free-updates 18 M
Installing for dependencies:
gsoap i686 2.7.17-4.fc15 updates 198 k
kmod-VirtualBox-OSE-2.6.42.12-1.fc15.i686.PAE
i686 4.1.8-1.fc15.10 rpmfusion-free-updates 164 k
Transaction Summary
================================================================================
Install 3 Package(s)
Total download size: 19 M
Installed size: 68 M
Is this ok [y/N]:
- Ken
I am investigation this, I will try be clear, so lets forget what was
write after this point of thread and begging again , because I think I
have news ...
First clarify that VirtualBox-OSE have and had scripts like its write in
http://rpmfusion.org/Packaging/KernelModules/Kmods2#userland_package ( I
though not, but after verify they are all there)
but, for me, it still miss something to kmod works correctly. We need
assure that meta package kmod-VirtualBox-OSE-4.1.12-1.fc16.3.x86_64 is
installed.
when I do:
yum install VirtualBox-OSE
installs: VirtualBox-OSE and what you call in wiki
kmod-foo-<kernel-version> and for me misses kmod-foo
Strange is, yum install VirtualBox-OSE VirtualBox-OSE-kmod still not
install kmod-foo
but yum install VirtualBox-OSE kmod-VirtualBox-OSE install kmod-foo and
kmod-foo-<kernel-version>
so my early conclusion is this:
MUST: The package must provide %{name}-kmod-common using 'Provides:
%{name}-kmod-common = %{version}';
should be on kmod-foo not in foo .
Thanks,
--
Sérgio M. B.