[Bug 2020530] Re: The debootstrap SRU to end all debootstrap SRUs

[Steve Langasek]

** Summary changed:

-  Add Ubuntu Mantic as a known release 
+ The debootstrap SRU to end all debootstrap SRUs

** Description changed:

+ [Impact]
+ Today, debootstrap requires a sourceful change to know about every target name.  This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
+ 
+ We have done this 30 times.
+ 
+ It causes development drag, because the upload of debootstrap to the
+ devel series is not instantaneous, usually gets hung up on failing
+ autopkgtests of reverse-dependencies related to other aspects of the
+ archive opening, and is slow to get SRUed back to stable series.
+ 
+ And the only code change required in debootstrap is a symlink to the
+ 'gutsy' script which has not changed in 15 years.
+ 
+ In mantic, I have changed the code to detect when running on Ubuntu, and
+ if it is, to default to the common Ubuntu bootstrap script for release
+ names that it does not recognize.  This removes the need for any further
+ uploads of debootstrap to inform it of new Ubuntu release names.
+ 
+ [Original description]
  (on Jammy)
  # sg sbuild -c mk-sbuild --skip-proposed mantic
  Specified release (mantic) not known to debootstrap
  
  Without this update users cannot generate mantic chroots for
  development.

-- 
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/2020530

Title:
  The debootstrap SRU to end all debootstrap SRUs

Status in debootstrap package in Ubuntu:
  New

Bug description:
  [Impact]
  Today, debootstrap requires a sourceful change to know about every target name.  This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.

  We have done this 30 times.

  It causes development drag, because the upload of debootstrap to the
  devel series is not instantaneous, usually gets hung up on failing
  autopkgtests of reverse-dependencies related to other aspects of the
  archive opening, and is slow to get SRUed back to stable series.

  And the only code change required in debootstrap is a symlink to the
  'gutsy' script which has not changed in 15 years.

  In mantic, I have changed the code to detect when running on Ubuntu,
  and if it is, to default to the common Ubuntu bootstrap script for
  release names that it does not recognize.  This removes the need for
  any further uploads of debootstrap to inform it of new Ubuntu release
  names.

  [Original description]
  (on Jammy)
  # sg sbuild -c mk-sbuild --skip-proposed mantic
  Specified release (mantic) not known to debootstrap

  Without this update users cannot generate mantic chroots for
  development.

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