[Bug 2077344] Re: upgrades should change snap-store and firmware-updater tracking

[Łukasz Zemczak]

Hello Nick, or anyone else affected,

Accepted ubuntu-release-upgrader into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:24.04.22
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, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-noble

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/2077344

Title:
  upgrades should change snap-store and firmware-updater tracking

Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  We would like 24.04 LTS systems and newer to have snap-store track
  2/stable, and firmware-updater track 1/stable.

  ubuntu-release-upgrader has a "deb2snap" mechanism capable of doing
  this.

  [Test Plan]

  1. On Jammy, see that snap-store and firmware-updater are not tracking
  2/stable and 1/stable, respectively:

  $ snap info snap-store | grep "^tracking:"
  $ snap info firmware-updater | grep "^tracking:"

  Perform an upgrade from Jammy to Noble:

  $ do-release-upgrade -d

  After the upgrade, confirm that snap-store and firmware-updater are
  tracking the new channels:

  $ snap info snap-store | grep "^tracking:"
  $ snap info firmware-updater | grep "^tracking:"

  In this case, since the snap tracking was not previously modified, no
  informational message should be displayed to the user.

  2. Do the same test as before, but before the upgrade, switch snap-
  store to something like beta/stable so that a notification is
  displayed about switching the snap tracking.

  [Where problems could occur]

  The patch is editing deb2snap.json entries. Typos would lead to a
  failure in changing the trackings. We should also be certain that
  these are the correct trackings for these snaps.

  There is also some new logic added to allow "force switching" a snap's
  tracking channel. This logic should only be in effect when a deb2snap
  entry explicitly asks for it. Nonetheless, issues in the
  implementation would effect the deb2snap logic during the upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2077344/+subscriptions