[Bug 1947362] Autopkgtest regression report (debootstrap/1.0.123ubuntu6.1)

Ubuntu SRU Bot 1947362 at bugs.launchpad.net
Fri Oct 15 19:07:45 UTC 2021


All autopkgtests for the newly accepted debootstrap (1.0.123ubuntu6.1) for hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

pbuilder/0.231build1 (arm64, ppc64el, s390x, amd64)
sbuild/0.81.2ubuntu5 (arm64, ppc64el, s390x, amd64)
lava/2020.12-1ubuntu2 (arm64)
piuparts/1.1.2 (arm64, ppc64el, s390x, amd64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#debootstrap

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Add Ubuntu Jammy as a known release

Status in debootstrap package in Ubuntu:
  In Progress
Status in debootstrap source package in Trusty:
  New
Status in debootstrap source package in Xenial:
  New
Status in debootstrap source package in Bionic:
  Fix Committed
Status in debootstrap source package in Focal:
  Fix Committed
Status in debootstrap source package in Hirsute:
  Fix Committed
Status in debootstrap source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  Without this update users cannot generate jammy chroots for
  development.

  [Test Case]

  Attempt to debootstrap jammy.

  [Where problems could occur]

  Nowhere really, this simply introduces a suite specific script which
  is not used unless you attempt to create and Ubuntu Jammy chroot.

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




More information about the foundations-bugs mailing list