Michael Meskes wrote:
It's debatable which package is at fault, but it's definitely
unacceptable to just reassign the bug without a single line of
explanation.
again, the current way is: a module source package works with l-m-e, or
it doesn't.
Assuming that Panthera didn't even check what's
It's debatable which package is at fault, but it's definitely
unacceptable to just reassign the bug without a single line of
explanation.
Assuming that Panthera didn't even check what's going on, here's the
explanation:
linux-modules-extra calls make inside virtualbox-ose-source
with a
Michael Meskes wrote:
I can live with this if you can point me to some documentation about how
l-m-e works. I wasn't able to find it yet.
there is none, yet. probably it doesn't even make sense to write one,
depending on ETA of dkt. a task for semester break anyway.
--
Address:Daniel
On Mon, Dec 03, 2007 at 02:19:44PM +0100, Daniel Baumann wrote:
again, the current way is: a module source package works with l-m-e, or
it doesn't.
I can live with this if you can point me to some documentation about how
l-m-e works. I wasn't able to find it yet.
he did, and saw that it is
Package: linux-modules-extra-2.6
Version: 2.6.22-9
Severity: important
virtualbox-ose-modules-2.6.22-3-686 contains virtualbox-ose.ko instead
of the expected vboxdrv.ko that's generated by module-assistant.
This renders this binary package useless.
-- System Information:
Debian Release:
5 matches
Mail list logo
