Hi Debian Virtualbox Team,
I'm one of the developers of a Debian Live system called Tails [0].
We support booting Tails as a guest inside Virtualbox and therefore
ship modules built by virtualbox-ose-guest-dkms in the released Tails
ISO images.
[0]
http://tails.boum.org/
For better (recent) hardware support, we would like to ship
squeeze-backports' Linux 2.6.38+ kernel as part of our next release.
One of the blockers to this is: last time I checked (~1 week ago),
Squeeze's virtualbox-ose-guest-dkms failed to build against the Linux
2.6.38 headers from squeeze-backports.
So I'm wondering what is the right way to go from here. Hence two
questions.
1. Do you consider this build failure against a kernel that is not
part of Squeeze (although part of squeeze-backports) to be a bug
that is worth reporting to the Debian BTS... and worth pushing to
s-p-u? (Cherry-picking some patches from a newer 3.2.x upstream
release would be needed, it seems.)
2. Current testing packages are trivial to backport for Squeeze, and
the backported -dkms package builds nicely against 2.6.38 headers.
On the other hand, I'm aware committing to maintain such backports
on the long run involves quite more work. Do you intend, as a team,
to maintain Virtualbox 4.x in squeeze-backports during the Squeeze
life-cycle?
Thanks for maintaining Virtualbox in Debian,
bye,
--
intrigeri <intrigeri@???>
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
| Did you exchange a walk on part in the war
| for a lead role in the cage?
