New upstream bugfix release 1.1.4 (LXC MRE)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Vivid |
Fix Released
|
Medium
|
Unassigned |
Bug Description
We have released LXC 1.1.4 upstream: https:/
This will be the first and last upstream bugfix release to hit vivid. The upstream changes are detailed at the URL above.
The MRE was reviewed by Martin Pitt here: https:/
As for testing, this version went through both automated testing (all the tests present in lxc-tests + the python3 API tests) as well as manual testing done by myself, LXC contributors and LXC users who've been building the git stable branch for a while now.
Until now, vivid was on a patched version of 1.1.2, basically 1.1.2 + security updates. LXC 1.1.4 contains all those same security updates, a bunch more bugfixes (160 or so when combining 1.1.3 and 1.1.4 together). This also makes the LXC in both vivid and wily to be identical, simplifying maintenance until vivid goes EOL.
Changed in lxc (Ubuntu): | |
status: | Invalid → Fix Released |
importance: | Undecided → Medium |
Changed in lxc (Ubuntu Vivid): | |
importance: | Undecided → Medium |
tags: |
added: verification-needed removed: verification-failed |
tags: |
added: verification-done removed: verification-needed |
Hello Stéphane, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ lxc/1.1. 4-0ubuntu0. 1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!