Re: [arch-general] Missing Dependency virtualbox-host-dkms
On Mon, Mar 7, 2016 at 6:52 PM, Sebastiaan Lokhorst wrote: > Yes, I think that would be the best solution. Each '*-headers' package > could provide 'kernel-headers' (or something like that). > Provides does not imply conflict, so that wouldn't be a problem. > > Note that a user could still install a certain 'x-headers' which does not > match their 'y' kernel, since the headers do not depend on the kernel or > vice versa. (in the libgl case this is not a problem, since the libgl > packages depend on the matching driver) > > But I think most users who use the regular kernel and are not familiar with > other kernels would install the plain 'linux-headers' package when > prompted, and not the 'linux-lts-headers' package or something else. Now that you mention it, would it be possible to have virtualbox depend on a "virtualbox-host" fake package that both virtualbox-host-modules and virtualbox-host-dkms Provide? That way end users wouldn't need to install any headers or make dependencies, and their updates would be faster, while folks on other kernels would still be able to satisfy the dependency their own way. Or is there another reason virtualbox-host-modules was dropped as a dependency? Unfortunately, "virtualbox-host" wouldn't automatically fix anyone who's gotten into the broken state, since they'll now have virtualbox-host-dkms installed, but it won't be building any vbox* modules for them. Maybe it would be a good idea to create *both* virtual packages? If that's more work than it's worth, an Arch News post might do the trick too. But people using virtualbox-host-dkms really do require at least one kernel package, and it could be helpful to have pacman enforce that.
Re: [arch-general] Missing Dependency virtualbox-host-dkms
2016-03-08 0:10 GMT+01:00 Jack O'Connor : > > Would it be possible to depend on a "Provides" that all the different > kernel header packages share? Similar to how nvidia-libgl, > catalyst-libgl, and mesa-libgl all provide the "libgl" dependency. > That would solve the presumably-very-common case where users initially > installed virtualbox without any host headers at all, and are now > landing in a broken state by default. (Or would that mean that the > different header packages conflict where they didn't before?) Yes, I think that would be the best solution. Each '*-headers' package could provide 'kernel-headers' (or something like that). Provides does not imply conflict, so that wouldn't be a problem. Note that a user could still install a certain 'x-headers' which does not match their 'y' kernel, since the headers do not depend on the kernel or vice versa. (in the libgl case this is not a problem, since the libgl packages depend on the matching driver) But I think most users who use the regular kernel and are not familiar with other kernels would install the plain 'linux-headers' package when prompted, and not the 'linux-lts-headers' package or something else.
Re: [arch-general] Missing Dependency virtualbox-host-dkms
> I didn't force the deps to linux-headers because you could use the kernel > (linux, linux-lts, linux-zen, linux-grsec, etc) you prefer (or all together). > I will add a message with the next release of virtualbox. Would it be possible to depend on a "Provides" that all the different kernel header packages share? Similar to how nvidia-libgl, catalyst-libgl, and mesa-libgl all provide the "libgl" dependency. That would solve the presumably-very-common case where users initially installed virtualbox without any host headers at all, and are now landing in a broken state by default. (Or would that mean that the different header packages conflict where they didn't before?) - Jack
Re: [arch-general] Missing Dependency virtualbox-host-dkms
On dim., 2016-03-06 at 18:16 +0100, Chr1s via arch-general wrote: > On 03/06/2016 05:16 PM, Eli Schwartz wrote: > > > > It would be rather unfair towards users of a different kernel to make a > > hard dependency on the main kernel. > You're right, that could be unfair esp when you install kernels via aur. > > Is it possible to add a hint while installing the package? > I didn't force the deps to linux-headers because you could use the kernel (linux, linux-lts, linux-zen, linux-grsec, etc) you prefer (or all together). I will add a message with the next release of virtualbox. Cheers, -- Sébastien "Seblu" Luttringer https://seblu.net | Twitter: @seblu42 GPG: 0x2072D77A signature.asc Description: This is a digitally signed message part
Re: [arch-general] Missing Dependency virtualbox-host-dkms
On Sun, 6 Mar 2016 18:16:09 +0100, Chr1s via arch-general wrote: >Is it possible to add a hint while installing the package? > >I know theres already an opt dep but for me an opt dep is very optional >but in this case you really need some headers to get the modules >working. Just to make it clear, to avoid any misunderstanding. You need the kernel source code to compile the modules. This is not only a requirement when building kernel modules. The linux packages are just split into the kernel image and header packages, while other packages usually aren't split and contain their header files.
Re: [arch-general] Missing Dependency virtualbox-host-dkms
On 03/06/2016 05:16 PM, Eli Schwartz wrote: > It would be rather unfair towards users of a different kernel to make a > hard dependency on the main kernel. You're right, that could be unfair esp when you install kernels via aur. Is it possible to add a hint while installing the package? I know theres already an opt dep but for me an opt dep is very optional but in this case you really need some headers to get the modules working. Cheers Chris
Re: [arch-general] Missing Dependency virtualbox-host-dkms
On Sun, 6 Mar 2016 17:12:47 +0100, Chr1s via arch-general wrote: >Is it possible to add the `linux-headers' package as a dependency for >the `virtualbox-host-dkms' package or miss I something? Hi, you miss that the official provided linux and linux-lts headers are already optional dependencies [rocketmouse@archlinux ~]$ pacman -Qi virtualbox-host-dkms | grep -A1 Optional\ D Optional Deps : linux-headers [installed] linux-lts-headers and an example from one of my bash histories [root@archlinux rocketmouse]# grep dkms ~/.bash_history | grep 5 dkms remove -m vboxhost -v 5.0.12 --all dkms install vboxhost/5.0.14 -k 4.3.3-3-ARCH/x86_64 && dkms install vboxhost/5.0.14 -k 4.0.4-rt1-1-rt/x86_64 && dkms install vboxhost/5.0.14 -k 3.10.61-rt65-1-rt-lts/x66_64 as you can see, a kernel not necessarily is provided by official repositories so you can not make such headers hard dependencies and I not necessarily have linux or linux-lts from official repositories installed at all, so I also don't want to be forced to install the headers. Regards, Ralf
Re: [arch-general] Missing Dependency virtualbox-host-dkms
FYI: There's a recent thread on arch-dev-public: https://lists.archlinux.org/pipermail/arch-dev-public/2016-March/027802.html --byte pgp3CVjmYXzci.pgp Description: Digitale Signatur von OpenPGP
Re: [arch-general] Missing Dependency virtualbox-host-dkms
On 03/06/2016 11:12 AM, Chr1s via arch-general wrote: > Is it possible to add the `linux-headers' package as a dependency for > the `virtualbox-host-dkms' package or miss I something? I guess what you are missing is that it is already an optdepends. It would be rather unfair towards users of a different kernel to make a hard dependency on the main kernel. -- Eli Schwartz
[arch-general] Missing Dependency virtualbox-host-dkms
Cheers Replacing the `virtualbox-host-modules' with the `virtualbox-host-dkms' package causes a "modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.4.3-1-ARCH". The whole misc (/lib/modules/4.4.3-1-ARCH/kernel/misc/) directory is missing. You need to install the `linux-headers' package for a working dkms. DKMS than can make the modules and creates the misc folder with all virtualbox *ko files. Is it possible to add the `linux-headers' package as a dependency for the `virtualbox-host-dkms' package or miss I something? Thanks Kind regards Chris