Bug#600939: I am not clear on why this is marked won't fix.
On Fri, Oct 22, 2010 at 11:21:26AM -0400, Jon Daley wrote:
> I am not clear on why this is marked won't fix - is the upgrade path that
> I found that proper way to do it?
No-one has explained exactly what change affects VirtualBox, so there is
no way we can revert it. And we are not going to make an ABI bump.
> e.g. Whenever the dkms build doesn't work due to kernel changes,
> uninstall virtualbox-ose-dkms, and then reinstall it, so it picks up the
> new changes?
Or use 'dkms build' to force a rebuild. (I'm not sure exactly how to do
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus