On Wed, Nov 18, 2015 at 11:50:04AM -0000, Launchpad Bug Tracker wrote: > 2) vivid: is this needed? let me know, I can update it without issues > (same update as the trusty one)
Vivid's lifetime is through January, 2016; if this update is easy for you to add, please do. > 3) trusty: > update from 4.3.10 to 4.3.34 > > I started from the Debian version that landed in -security some time > ago, and I rebased with the ubuntu changelogs. > > no notable differences a part of the changelog. > > testing has been fine, except for the part that I couldn't install the > current virtualbox-dkms because of the build failures (now trusty images > comes with shipped 3.19 that makes the dkms build fail). > > so, directly installed the 4.3.34 and everything was fine. Trusty sounds difficult. There are multiple supported kernels for 14.04 LTS; 3.13 kernel in 14.04.1 3.16 kernel from 14.04.2 (linux-generic-lts-utopic) 3.19 kernel from 14.04.3 (linux-generic-lts-vivid) 4.2 kernel (linux-generic-lts-wily). All of these are currently supported; when 16.04 LTS is released, I think then only the original 3.13 kernel and the (probably) 4.4 kernel from 16.04 LTS will be supported. I think VB hasn't worked for anyone on the HWE kernels; will this update mean VB will only work on the newest HWE kernels and break for users still on the original 3.13 kernels? > I'm not happy with this request, but well, I monitor for bugs, and I > guess I'll continue doing my best in keeping virtualbox working > correctly (I couldn't before because I was forced by the MRE updates > impossibility) Is there anything that could be done to help? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1517161 Title: virtualbox SRU for CVE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1517161/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
