canonical-ubuntu-qa team mailing list archive

[Brian Murray <2068775@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

At the beginning of the Lunar development cycle we created images from
Kinetic (because there were no Lunar images yet) but they were from a
Kinetic daily image so had newer versions of dbus and curl (I believe
they were 0 day security updates) than were available in Lunar. This
naturally caused some oddities when testing packages.

One possible solution to this is to build the development release image
from the "release" image (i.e. the one that was 22.10 in the above
example) of the previous release. However, being able to do this is
dependent upon those images being available in glance in the cloud
environment we are using.

Another solution might be to downgrade any package versions which are no
longer installable (or something like that) after upgrading to the
development release of Ubuntu.

** Affects: auto-package-testing
     Importance: Medium
         Status: New

** Changed in: auto-package-testing
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2068775

Title:
  development release images should not include package versions not in
  the development release

Status in Auto Package Testing:
  New

Bug description:
  At the beginning of the Lunar development cycle we created images from
  Kinetic (because there were no Lunar images yet) but they were from a
  Kinetic daily image so had newer versions of dbus and curl (I believe
  they were 0 day security updates) than were available in Lunar. This
  naturally caused some oddities when testing packages.

  One possible solution to this is to build the development release
  image from the "release" image (i.e. the one that was 22.10 in the
  above example) of the previous release. However, being able to do this
  is dependent upon those images being available in glance in the cloud
  environment we are using.

  Another solution might be to downgrade any package versions which are
  no longer installable (or something like that) after upgrading to the
  development release of Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2068775/+subscriptions