SRU of LXCFS 2.0.7 (upstream bugfix release)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxcfs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Triaged
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
Undecided
|
Unassigned | ||
Zesty |
Fix Released
|
Undecided
|
Unassigned | ||
Artful |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
LXCFS upstream released LXCFS 2.0.7 as a bugfix release with following changelog:
- Remove unused variable
- Also check next variable for NULL on cg_rmdir
- virtualize the 'btime' field of /proc/stat
- cleanup: return false instead of NULL as bool
- Limit memswlimit by TotalSwap
- pam_cgfs: remove dead assignment
- pam_cgfs: return created directly
- pam_cgfs: make sure that **p is not NULL
- bindings: Want space for ints? Call sizeof(int)!
- pam_cgfs: make trim() safer
- pam_cgfs: error out on failure in cgv2_init()
- pam_cgfs: remove dead assignment
- bindings: implement guest nice
- bindings: increase reserved buffer size a little
Just like Ubuntu itself, upstream releases long term support releases, as is 2.0 and then periodic point releases including all the accumulated bugfixes.
Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support.
This bugfix release has already been uploaded to Zesty and automatically backported in the upstream PPAs for all Ubuntu releases. So far without any reported regression.
This should qualify under the minor upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release.
Once the SRU hits -updates, we will be backporting this to trusty-backports as well, making sure we have the same version everywhere.
Changed in lxcfs (Ubuntu Artful): | |
status: | New → Fix Released |
Changed in lxcfs (Ubuntu Zesty): | |
status: | New → Triaged |
Changed in lxcfs (Ubuntu Yakkety): | |
status: | New → Triaged |
Changed in lxcfs (Ubuntu Xenial): | |
status: | New → Triaged |
Changed in lxcfs (Ubuntu Trusty): | |
status: | New → Triaged |
Changed in lxcfs (Ubuntu Zesty): | |
status: | Triaged → In Progress |
Changed in lxcfs (Ubuntu Yakkety): | |
status: | Triaged → In Progress |
Changed in lxcfs (Ubuntu Xenial): | |
status: | Triaged → In Progress |
Hello Stéphane, or anyone else affected,
Accepted lxcfs into zesty-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ lxcfs/2. 0.7-0ubuntu1~ 17.04.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 on 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!