[SRU] Calamares 3.2 Series for 22.04 LTS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
calamares (Ubuntu) |
Fix Released
|
Medium
|
Simon Quigley | ||
Jammy |
Fix Released
|
Medium
|
Simon Quigley | ||
Kinetic |
Fix Released
|
Medium
|
Simon Quigley |
Bug Description
[Impact]
* The version of Calamares currently present in Ubuntu has quite a few
bugs, which could potentially impact the user in a negative way during
the initial installation process of Ubuntu flavours that make use of
the Calamares installer.
* One such bug is Calamares upstream bug #1817. Attempting to install an
OS using Calamares and LVM results in an almost immediate installation
failure. Testing has revealed that this bug affects both Lubuntu and
Ubuntu Studio 22.04.
* This SRU updates the version of Calamares to the latest stable release,
fixing this bug and a number of other bugs which can be seen at
https:/
current version of Calamares is 3.2.41, so everything up from there are
the changes that will be applied). Additionally, a flaw in the
debian/rules file of the packaging was repaired, and an obsolete
manpage was removed to avoid potential user confusion. All the details
of these changes are documented in the package changelog.
[Test Plan]
* Using a Lubuntu or Ubuntu Studio 22.04 ISO, follow the exact steps
mentioned in the upstream bug report here:
https:/
* (Note: There's a typo in the line that reads `sudo vgcreate myvg
/dev/sda1k` - the "k" at the end doesn't belong. The line should read
`sudo vgcreate myvg /dev/sda1` - I verified this in my testing.)
* The installation will fail. Repeated attempts to install will result in
repeated failures (I tested by attempting to install in this
configuration twice).
* Install Calamares 3.2.60 into the live ISO using the updated package.
* Repeat the steps to reproduce the bug.
* The installation will succeed, and you will be able to boot into the OS
after installation.
[Where problems could occur]
* If a bug was introduced in this version of Calamares, or if a
configuration change is needed in calamares-
result in installations failing, being unable to boot after a
"successful" installation, or being bootable but too damaged to use.
Due to the highly obvious nature of such issues, it will be easy to
catch it if something like this happens.
[Other Info]
* The Lubuntu team has an intensive test suite prepared for detecting
such problems, and the new Calamares package will be put through the
full test suite, possibly multiple times, to ensure that it is stable
and ready for production use.
* As this change will affect both Lubuntu and Ubuntu Studio, we intend to
run both flavors through the full test suite to minimize the potential
for unforseen breakage.
* The full Calamares test suite used by Lubuntu can be located here:
https:/
checklist works is explained here:
https:/
---
Original bug report:
(This is starting as a request for comment from the Ubuntu Stable Release Update Team and will eventually be edited to be an SRU bug.)
In Lubuntu and Ubuntu Studio 22.04 LTS, we dropped the ball by including the same version of Calamares as we did in 21.10. Upstream considers 3.2 to be an "LTS" series, so we would like to follow the upstream release cycle to deliver the latest 3.2 point release to our users.
Here is a specific link to the code changes included between the two versions: https:/
It's quite a lengthy update. As far as I can tell, we have three options:
A) Update to the latest upstream milestone in 22.04. Go through a thorough test suite, which will be outlined in the SRU bug report, and continue to follow upstream point releases. The benefit of this route is that 3.2.60 has many more eyes on it than 3.2.41.1. Bugs are more easily fixed, and problems are likely to be experienced between multiple distributions, not just us.
B) We patch 3.2.41.1 with just translations and all bugfixes, only. This will take quite a bit of work to sort through what qualifies as a bugfix, what can be backported, and the rationale for each bugfix. Would not recommend but perhaps this is the most "standard" option.
C) Only backport specific high-profile bugfixes to 3.2.41.1.
I'd like to just go with A, and speaking on behalf of Lubuntu I think that would be the most sustainable option. I'm *very* rusty on this entire process, so please let me know what other information you may need to help in processing this request.
Thank you.
Changed in calamares (Ubuntu Kinetic): | |
status: | New → Fix Released |
importance: | Undecided → Medium |
Changed in calamares (Ubuntu Jammy): | |
importance: | Undecided → Medium |
assignee: | nobody → Simon Quigley (tsimonq2) |
Changed in calamares (Ubuntu Kinetic): | |
assignee: | nobody → Simon Quigley (tsimonq2) |
Changed in calamares (Ubuntu Jammy): | |
milestone: | none → ubuntu-22.04.1 |
Changed in calamares (Ubuntu Kinetic): | |
milestone: | none → ubuntu-22.05 |
description: | updated |
description: | updated |
description: | updated |
Changed in calamares (Ubuntu Jammy): | |
status: | Triaged → In Progress |
*with Ubuntu Studio hat on*
Honestly, option A seems very sane. I'm against going with dozens or hundreds of patches to accomplish the same goal, and getting Calamares into better shape is definitely a better option.
I did bring up with the Lubuntu team that Calamares did seem to be needing an update, but this was a bit beyond feature freeze, and nobody (including myself) felt comfortable at the time with uploading a new version that close to beta freeze.
However, we have seen what can happen if the installer does not have LTS maintainability and stability, and this does have a detrimental effect on the product. With that, I agree with everything Simon has written and the justification seems sound.
Unfortunately, we have just a month as 22.04.1 is approaching quickly. I have had several recent experiences with SRUs, so I can assist Simon with the SRU if need-be.