As discussed in #ubuntu-devel right now, it's probably best to avoid
bumping Noble's package version higher than Oracular, so I'll arrange
some tweaks:

No-change rebuild using 1.0.5-3build1~ubuntu0.24.04.1 for Noble.

No-change rebuild using 1.0.5-3build1 for Oracular.

** Changed in: retry (Ubuntu)
       Status: Fix Released => In Progress

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to retry in Ubuntu.
Matching subscriptions: ubuntu-qa-bugs
https://bugs.launchpad.net/bugs/2080616

Title:
  [SRU] No change rebuild for MIR

Status in retry package in Ubuntu:
  In Progress
Status in retry source package in Jammy:
  In Progress
Status in retry source package in Noble:
  In Progress

Bug description:
  [ Impact ]

   * `retry` has become a dependency of `autopkgtest`, and `autopkgtest` has an 
SRU exception to get updated to older releases: 
https://wiki.ubuntu.com/StableReleaseUpdates#autopkgtest
  Since `autopkgtest` is in `main`, `retry` needs to be too, which led to an 
MIR described in bug 2076381.
  The MIR got approved, and `retry` has already been promoted on Oracular, but 
it seems impossible to promote it on Jammy and Noble because it's not in the 
`-updates` pockets (see comment #9 on the MIR bug).

  I'm thus submitting a no change rebuild SRU to Jammy and Noble, so
  that the MIR can complete.

  [ Test Plan ]

   * `retry` has some dep8 test, even already on the Jammy version, and
  those should be green.

   * Manual verification that the `retry` package installs correctly, and the 
provided binary runs fine:
  ```
  sudo apt install retry
  retry --help  # should display help
  retry --until=success -- false  # should run forever
  retry --until=success --delay "1,2,4,8,16,32,64" -- false  # should repeat 
forever with increasing delay until 64 seconds
  ```

  [ Where problems could occur ]

   * For some reason the newly rebuilt binary could be buggy because of
  some compilation issue. It's a fairly simple single C file, so I
  expect if that one doesn't work, there might be issues for other
  packages too.

   * If `retry` breaks for some reason, that might also break its
  dependencies. `rdepends` shows that only `debci`, and soon to be
  `autopkgtest` depend on `retry`. That makes the list pretty small, and
  only packages used by developers (and actually used by my team for
  `autopkgtest`), so we should spot the issue pretty quickly and we will
  need to work on it, which should mitigate having long standing unfixed
  bugs.

  [ Other Info ]

  * Nothing that I can think of.

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


-- 
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to     : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help   : https://help.launchpad.net/ListHelp

Reply via email to