This bug was fixed in the package virtualbox - 5.1.34-dfsg-
0ubuntu1.17.10.2
---
virtualbox (5.1.34-dfsg-0ubuntu1.17.10.2) artful; urgency=medium
* New upstream version 5.1.34-dfsg
LP: #1746316 -> security patches for spectre and meltdown
LP: #1736116 -> freeze with kernel
This bug was fixed in the package virtualbox-guest-additions-iso -
5.1.34-0ubuntu1.16.04.2
---
virtualbox-guest-additions-iso (5.1.34-0ubuntu1.16.04.2) xenial; urgency=medium
* New upstream version 5.1.34
LP: #1746316 -> security patches for spectre and meltdown
LP:
This bug was fixed in the package virtualbox - 5.1.34-dfsg-
0ubuntu1.16.04.2
---
virtualbox (5.1.34-dfsg-0ubuntu1.16.04.2) xenial; urgency=medium
* New upstream version 5.1.34-dfsg
LP: #1746316 -> security patches for spectre and meltdown
LP: #1736116 -> freeze with kernel
This bug was fixed in the package virtualbox-guest-additions-iso -
5.1.34-0ubuntu1.17.10.1
---
virtualbox-guest-additions-iso (5.1.34-0ubuntu1.17.10.1) artful; urgency=medium
* New upstream version 5.1.34
LP: #1746316 -> security patches for spectre and meltdown
LP:
This bug was fixed in the package virtualbox-ext-pack -
5.1.34-0ubuntu1.17.10.2
---
virtualbox-ext-pack (5.1.34-0ubuntu1.17.10.2) artful; urgency=medium
* Really point to 5.1.34 source to download
virtualbox-ext-pack (5.1.34-0ubuntu1.17.10.1) artful; urgency=medium
* New
This bug was fixed in the package virtualbox-ext-pack -
5.1.34-0ubuntu1.16.04.2
---
virtualbox-ext-pack (5.1.34-0ubuntu1.16.04.2) xenial; urgency=medium
* Really point to 5.1.34 source to download
virtualbox-ext-pack (5.1.34-0ubuntu1.16.04.1) xenial; urgency=medium
* New
This bug was fixed in the package kbuild -
1:0.1.9998svn2814+dfsg-2~ubuntu16.04.1
---
kbuild (1:0.1.9998svn2814+dfsg-2~ubuntu16.04.1) xenial; urgency=medium
* SRU to xenial, to make virtualbox 5.1 build correctly
* New upstream version 5.1.32-dfsg
LP: #1746316 -> security
** Changed in: virtualbox-ext-pack (Ubuntu)
Status: New => Fix Released
** Changed in: kbuild (Ubuntu)
Status: New => Fix Released
** Changed in: virtualbox (Ubuntu)
Status: In Progress => Fix Released
** Changed in: virtualbox-guest-additions-iso (Ubuntu)
Status:
I've installed virtualbox (and virtualbox-qt) 5.1.34-dfsg-
0ubuntu1.17.10.2 from artful-proposed. I can confirm that it fixes bug
1754991. I haven't done a thorough regression test, but everything else
seems to work as expected.
Thanks for updating, LocutusOfBorg :)
--
You received this bug
** Tags removed: verification-needed verification-needed-artful
verification-needed-xenial
** Tags added: verification-done verification-done-artful
verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Lonnie, or anyone else affected,
Accepted virtualbox-ext-pack into artful-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/virtualbox-ext-pack/5.1.34-0ubuntu1.17.10.2 in a few hours, and then in
the -proposed repository.
Please help us by
oops, fixed and reuploaded
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746316
Title:
[SRU] VirtualBox needs Security Patches
To manage notifications about this bug go to:
Hello,
The package virtualbox-ext-pack (5.1.34-0ubuntu1.16.04.1) from xenial-proposed
install the version 5.1.32 of the VirtualBox Extension Pack, instead of the
5.1.34.
term.log:
Paramétrage de virtualbox-ext-pack (5.1.34-0ubuntu1.16.04.1) ...
virtualbox-ext-pack: downloading:
Test results will be reported on #1736116
** Tags removed: verification-needed verification-needed-artful
verification-needed-xenial
** Tags added: verification-done verification-done-artful
verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Hello Lonnie, or anyone else affected,
Accepted kbuild into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/kbuild/1:0.1.9998svn2814+dfsg-2~ubuntu16.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
@sil2100 thanks!
>I am for now not accepting the virtualbox-ext-pack for artful as I
first would like to get confirmation about something: looking at the
debian/control and debian/rules version variables, those seem to be
using the 5.1.32 version string while the package itself is versioned as
Hello Lonnie, or anyone else affected,
Accepted virtualbox into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/virtualbox/5.1.34
-dfsg-0ubuntu1.16.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
I am for now not accepting the virtualbox-ext-pack for artful as I first
would like to get confirmation about something: looking at the
debian/control and debian/rules version variables, those seem to be
using the 5.1.32 version string while the package itself is versioned as
5.1.34. Is that a
Ok, this is now more clear to me from the SRU-team's POV, thanks. During
verification please briefly describe some of the test-cases you have
performed and I'll be on cloud nine.
** Also affects: virtualbox-ext-pack (Ubuntu)
Importance: Undecided
Status: New
** Also affects:
BTW, bugs like LP: #1754991 can be probably also considered duplicated
of this one, so confirming their fix will be sufficient to confirm also
this one (the Spectre/Meltdown kernel fixes needs to be followed by
virtualbox changes too)
--
You received this bug notification because you are a
Hello, the MRE has been discussed many times, e.g. I did the same work a
lot of times, including describing the MRE exception paperwork.
e.g. LP: #1594493
LP: #1629870 (here you can see why the upstream testsuite is better than
autopkgtests)
LP: #1674819
LP: #1683965
LP: #1729568
If we compare
The bare minimum, I suppose, would be to provide us with some general
set of test steps testers should perform to check if anything that's not
already broken regressed or not. The related bug with 4.13 kernels seems
to impact xenial with the HWE stack - but since the regular 4.4 kernels
still
Sadly this is not something I am willing to accept in this state as an
SRU with my SRU reviewer hat on. The bug is missing the standard SRU
template information, with a detailed test case to be performed and the
regression potential analysis. Sure, we all know that the recent
security patches
** Changed in: virtualbox (Ubuntu Xenial)
Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)
** Changed in: virtualbox (Ubuntu Artful)
Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)
--
You received this bug notification because you are a member of Ubuntu
Please look at bug: 1736116 for an SRU template
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746316
Title:
[SRU] VirtualBox needs Security Patches
To manage notifications about this bug go to:
25 matches
Mail list logo
