On Fri, 2012-03-30 at 08:09 +0200, Thorsten Leemhuis wrote: > Sorry, hit the Shortcut for sending mail :-/ > > Sérgio Basto wrote on 30.03.2012 00:59: > > On Thu, 2012-03-29 at 14:09 -0600, Ken Dreyer wrote: > >> On Thu, Mar 29, 2012 at 2:00 PM, Richard Shaw <[email protected]> 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]: > > > > > > Hi, thanks for your help , > > In yours install demo here, you still miss the meta package > > kmod-VirtualBox-OSE, in this case > > kmod-VirtualBox-OSE-4.1.8-1.fc15.10.i686 > > the PAE one is kmod-VirtualBox-OSE-PAE-4.1.8-1.fc15.10.i686 > > > > I made some confusion because we built VirtualBox-OSE-kmod.spec, but at > > the end the arch rpms are all kmod-VirtualBox-OSE(...) > > > > so: > > Requires: kmod-%{name} = %{version}%{?prereltag} > > > > I am testing it now with VirtualBox-OSE-guest and also it should > > requires meta package, for better sync with kernels with kmods. > > > > so add also to VirtualBox-OSE-guest ? > > > > Again, if nobody complains, tomorrow I will update packages with > > Requires: kmod-%{name} = %{version}%{?prereltag} > > Sorry, I can't follow your logic. What Ken pointed out should be enough. The > > Requires: %{name}-kmod = %{version}%{?prereltag}
yum install VirtualBox-OSE Installing: VirtualBox-OSE x86_64 4.1.12-1.fc16 VirtualBox Installing for dependencies: kmod-VirtualBox-OSE-3.3.0-8.fc16.x86_64 x86_64 4.1.12-1.fc16.1 VirtualBox doesn't install VirtualBox-OSE x86_64 4.1.12-1.fc16 VirtualBox but yum install VirtualBox-OSE-kmod Installing: kmod-VirtualBox-OSE x86_64 4.1.12-1.fc16.1 VirtualBox Installing for dependencies: VirtualBox-OSE x86_64 4.1.12-1.fc16 VirtualBox kmod-VirtualBox-OSE-3.3.0-8.fc16.x86_64 x86_64 4.1.12-1.fc16.1 VirtualBox install all and yum remove VirtualBox-OSE-kmod Removing: kmod-VirtualBox-OSE x86_64 4.1.12-1.fc16.1 @VirtualBox kmod-VirtualBox-OSE-3.3.0-8.fc16.x86_64 x86_64 4.1.12-1.fc16.1 @VirtualBox Removing for dependencies: VirtualBox-OSE x86_64 4.1.12-1.fc16 @VirtualBox match with the 2, kmod-VirtualBox-OSE and kmod-VirtualBox-OSE-3.3.0-8.fc16.x86_64 > should track in the meta package, as its name is shorter then the akmods > package, which provides this to. Then the meta package tracks in the > latest kmod. Or, if users prefer to use akmods, then this won't happen, > as the akmod package provides the dep. > > Does that clarify the problem? As VirtualBox-OSE.spec already had this rules, we back to start, which is : yum install VirtualBox-OSE should also push kmod-meta-package . Thanks, -- Sérgio M. B.
