This bug was fixed in the package lxc - 1:4.0.12-0ubuntu1~20.04.1
---
lxc (1:4.0.12-0ubuntu1~20.04.1) focal; urgency=medium
* Cherry-pick upstream bugfixes (stable-4.0):
- 0002-lxc-checkconfig-Fix-bashism.patch
- 0003-doc-Fix-reverse-allowlist-denylist.patch
* New
This bug was fixed in the package lxc - 1:4.0.12-0ubuntu1~21.10.1
---
lxc (1:4.0.12-0ubuntu1~21.10.1) impish; urgency=medium
* Cherry-pick upstream bugfixes (stable-4.0):
- 0002-lxc-checkconfig-Fix-bashism.patch
- 0003-doc-Fix-reverse-allowlist-denylist.patch
* New
Have confirmed the packages to be functional on both focal and impish.
Tried installation, upgrade and basic container creation, deletion and normal
operations.
** Tags removed: verification-needed-focal verification-needed-impish
** Tags added: verification-done-focal verification-done-impish
Hello Stéphane, or anyone else affected,
Accepted lxc into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1:4.0.12-0ubuntu1~21.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Uploaded the exact same thing to impish queue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1959993
Title:
SRU of LXC 4.0.12 to focal (upstream bugfix release)
Status in
At yesterday's SRU team meeting we concluded that we don't want the
archive to end up going down in versions as you upgrade from Focal to
Impish. IOW, we aren't granting an exception in this case. Some reasons:
The time a security update is needed in the future would not be an
appropriate time to
(note that I haven't actually reviewed the upload yet)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1959993
Title:
SRU of LXC 4.0.12 to focal (upstream bugfix release)
Thanks Brian, my memory of this whole thing clearly dates back a long
time then ;)
I still remember some of the discussions of what we'd expect people to
be doing in such cases and whether we'd ever officially support (as in
test/validate) upgrade paths other than release to release+1 and LTS to
As a point of clarification here the release upgrade process skips
interim releases once they become end of life, so if one were to upgrade
from Focal they would upgrade to Impish or Jammy (depending on how their
system is configured). It looks like I made this change 7 years ago
(gasp!).
OK thanks. I'll consult with others on the SRU team on this - I've added
it to our meeting agenda. If it's decided that this is OK then I'll make
sure it's documented to avoid holding you up on it again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
(We technically had the same issue with the previous upload as 4.0.6 was
higher than what hirsute shipped at the time, though in that case the
EOL for hirsute was just a month or so away making the case for skipping
that SRU even stronger :))
--
You received this bug notification because you are
In general, it's indeed a problem for such cases, though there are a few
mitigating factors here:
- This would only be a problem for those who upgrade from focal to
impish. My understanding is that there is no direct upgrade path to
achieve this, you'd need to go throughgroovy and hirsute, both
Thank you for the detailed SRU information! You anticipated most of the
obvious questions and saved us a bunch of round trips.
> Should someone do an upgrade to impish, we've confirmed that the
upgrade is resolvable and that they'll just be left with a more recent
version of LXC than that in the
13 matches
Mail list logo
