ubuntustudio-bugs team mailing list archive

[Launchpad Bug Tracker <1980180@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package calamares - 3.2.60-0ubuntu0.1

---------------
calamares (3.2.60-0ubuntu0.1) jammy; urgency=medium

  * Updated Calamares to version 3.2.60 for SRU (LP: #1980180).
  * Updated copyright file.
  * Removed obsolete manpage for Calamares.
    - Reasoning: Calamares provides a man page upstream.
  * Imported upstream's signing key into debian/upstream/signing-key.asc.
  * Updated debian/watch to version 4, adding automatic GPG verification
    in the process.
  * Fixed a typo and a variable assignment bug in debian/rules.
    - Details: Originally, the rules file exported the
      DEB_BUILD_MAINT_OPTIONS variable twice, once to enable hardening, and
      once to help make build paths reproducible. I believe this would
      result in hardening being disabled due to clobbering. Additionally,
      there was a typo in the second variable export (a missing "=") that
      caused sbuild to show me a dh warning. Both problems are now resolved -
      the variable is only exported once, with both options set, and the
      typo is fixed.

 -- Aaron Rainbolt <arraybolt3@xxxxxxxxx>  Thu, 21 Jul 2022 13:09:04
-0500

** Changed in: calamares (Ubuntu Jammy)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to calamares in Ubuntu.
https://bugs.launchpad.net/bugs/1980180

Title:
  [SRU] Calamares 3.2 Series for 22.04 LTS

Status in calamares package in Ubuntu:
  Fix Released
Status in calamares source package in Jammy:
  Fix Released
Status in calamares source package in Kinetic:
  Fix Released

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://github.com/calamares/calamares/blob/calamares/CHANGES-3.2 (the
     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://github.com/calamares/calamares/issues/1817

   * (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-settings-ubuntu, it could
     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://phab.lubuntu.me/w/release-team/testing-checklist/ The way the
     checklist works is explained here:
     https://discourse.lubuntu.me/t/testing-checklist-understanding-the-testcases/2743

  ---

  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://github.com/calamares/calamares/compare/v3.2.41.1...v3.2.60

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1980180/+subscriptions