The debootstrap SRU to end all debootstrap SRUs

[Renan Rodrigo]

[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 the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).

[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
    if [ "$s" = mantic ]; then continue; fi
    sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
    sudo debootstrap $s ${s}-new
done
for s in $series; do
    if [ "$s" = mantic ]; then continue; fi
    sudo diff -uNr ${s}-old ${s}-new
done 2>&1 \
| grep -vE 'No such file or directory|is a (character|block) special file|Binary files .*(\.pyc|/var/cache/.*) differ' \
|filterdiff -x '*/etc/machine-id' -x '*/var/lib/dbus/machine-id' -x '*/var/log/**' -x '*/var/lib/dpkg/status*' -x '*/var/cache/**'
(exclude from the diff: dangling (wide) symlinks; device files; compiled pyc files that will differ on each generation; and other text files that are randomly generated or contain timestamp or ordering differences)

sudo apt install ubuntu-dev-tools
sg sbuild -c 'mk-sbuild --skip-proposed mantic'

[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.

[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.

[Bryce Harrington (bryce)]

piuparts seems to be hitting this in autopkgtest runs on jammy, e.g.:

https://autopkgtest.ubuntu.com/packages/p/piuparts/jammy/amd64
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/p/piuparts/20230525_155217_00e90@/log.gz

0m0.0s DEBUG: Starting command: ['dpkg', '--info', 't.deb']
0m0.0s DUMP:
   new Debian package, version 2.0.
   size 576 bytes: control archive=272 bytes.
       231 bytes, 8 lines control
   Package: t
   Version: 4
   Maintainer: Piu Parts <email address hidden>
   Priority: optional
   Architecture: all
   Installed-Size: 0
   Description: Auto Package Test Dummy
    Extremely simple binary package for piuparts testing
0m0.0s DEBUG: Command ok: ['dpkg', '--info', 't.deb']
0m0.0s DEBUG: Created temporary directory /tmp/tmp2s1lk6a4
0m0.0s DEBUG: Setting up minimal chroot for mantic at /tmp/tmp2s1lk6a4.
0m0.0s DEBUG: Starting command: ['eatmydata', 'debootstrap', '--variant=minbase', '--keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg', '--include=eatmydata', '--no-merged-usr', '--components=main,restricted,universe,multiverse', 'mantic', '/tmp/tmp2s1lk6a4', 'http://ftpmaster.internal/ubuntu/']
0m0.0s DUMP:
  E: No such script: /usr/share/debootstrap/scripts/mantic
0m0.0s ERROR: Command failed (status=1): ['eatmydata', 'debootstrap', '--variant=minbase', '--keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg', '--include=eatmydata', '--no-merged-usr', '--components=main,restricted,universe,multiverse', 'mantic', '/tmp/tmp2s1lk6a4', 'http://ftpmaster.internal/ubuntu/']
  E: No such script: /usr/share/debootstrap/scripts/mantic

Guessing debootstrap needs an SRU fix such as was done in https://launchpad.net/bugs/1995612 ?

[Brian Murray (brian-murray)]

Hello Renan, or anyone else affected,

Accepted debootstrap into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.127ubuntu1.2 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-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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.

[Brian Murray (brian-murray)]

Hello Renan, or anyone else affected,

Accepted debootstrap into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.128+nmu2ubuntu1.1 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-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. 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.

[Brian Murray (brian-murray)]

Hello Renan, or anyone else affected,

Accepted debootstrap into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.126+nmu1ubuntu0.3 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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Brian Murray (brian-murray)]

Hello Renan, or anyone else affected,

Accepted debootstrap into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.118ubuntu1.9 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-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted debootstrap (1.0.128+nmu2ubuntu1.1) for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

xen-tools/4.9.2-1 (ppc64el)

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/lunar/update_excuses.html#debootstrap

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted debootstrap (1.0.127ubuntu1.2) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

sbuild/0.83.1ubuntu1 (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/kinetic/update_excuses.html#debootstrap

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted debootstrap (1.0.126+nmu1ubuntu0.3) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

sbuild/0.81.2ubuntu6 (amd64)
xen-tools/4.9.1-1 (arm64, ppc64el)

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/jammy/update_excuses.html#debootstrap

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

Thank you!

[Steve Langasek (vorlon)]

lunar passes. After amending the test case to clean up the output of the diff, here is the remaining manageable delta which I think is not worth further test case refinement on as it can be hand-reviewed for sanity.

diff -ur bionic-old/etc/console-setup/cached_setup_keyboard.sh bionic-new/etc/console-setup/cached_setup_keyboard.sh
--- bionic-old/etc/console-setup/cached_setup_keyboard.sh 2023-05-27 02:40:01.972144149 +0000
+++ bionic-new/etc/console-setup/cached_setup_keyboard.sh 2023-05-27 03:46:59.789488446 +0000
@@ -5,4 +5,4 @@
     exit 0
 fi
 kbd_mode '-u'
-loadkeys '/tmp/tmpkbd.0HDubT' > '/dev/null'
+loadkeys '/tmp/tmpkbd.Ds1StA' > '/dev/null'
Binary files bionic-old/var/lib/systemd/catalog/database and bionic-new/var/lib/systemd/catalog/database differ
Binary files trusty-old/etc/console-setup/cached.kmap.gz and trusty-new/etc/console-setup/cached.kmap.gz differ
Binary files xenial-old/etc/console-setup/cached.kmap.gz and xenial-new/etc/console-setup/cached.kmap.gz differ
diff -ur xenial-old/etc/init.d/.depend.boot xenial-new/etc/init.d/.depend.boot
--- xenial-old/etc/init.d/.depend.boot 2023-05-27 02:58:16.630479975 +0000
+++ xenial-new/etc/init.d/.depend.boot 2023-05-27 04:09:02.805597475 +0000
@@ -1,4 +1,4 @@
-TARGETS = console-setup mountkernfs.sh hostname.sh resolvconf udev networking hwclock.sh mountdevsubfs.sh checkroot.sh urandom checkfs.sh checkroot-bootclean.sh bootmisc.sh mountnfs-bootclean.sh mountnfs.sh mountall-bootclean.sh mountall.sh kmod procps
+TARGETS = console-setup mountkernfs.sh hostname.sh resolvconf udev networking hwclock.sh mountdevsubfs.sh checkroot.sh urandom mountnfs.sh mountall.sh checkfs.sh checkroot-bootclean.sh bootmisc.sh procps kmod mountnfs-bootclean.sh mountall-bootclean.sh
 INTERACTIVE = console-setup udev checkroot.sh checkfs.sh
 udev: mountkernfs.sh
 networking: mountkernfs.sh urandom procps resolvconf
@@ -6,12 +6,12 @@
 mountdevsubfs.sh: mountkernfs.sh udev
 checkroot.sh: hwclock.sh mountdevsubfs.sh hostname.sh
 urandom: hwclock.sh
+mountnfs.sh: networking
+mountall.sh: checkfs.sh checkroot-bootclean.sh
 checkfs.sh: checkroot.sh
 checkroot-bootclean.sh: checkroot.sh
-bootmisc.sh: checkroot-bootclean.sh mountnfs-bootclean.sh mountall-bootclean.sh udev
+bootmisc.sh: udev checkroot-bootclean.sh mountnfs-bootclean.sh mountall-bootclean.sh
+procps: mountkernfs.sh udev
+kmod: checkroot.sh
 mountnfs-bootclean.sh: mountnfs.sh
-mountnfs.sh: networking
 mountall-bootclean.sh: mountall.sh
-mountall.sh: checkfs.sh checkroot-bootclean.sh
-kmod: checkroot.sh
-procps: mountkernfs.sh udev
diff -ur xenial-old/etc/init.d/.depend.stop xenial-new/etc/init.d/.depend.stop
--- xenial-old/etc/init.d/.depend.stop 2023-05-27 02:58:16.630479975 +0000
+++ xenial-new/etc/init.d/.depend.stop 2023-05-27 04:09:02.805597475 +0000
@@ -1,9 +1,9 @@
 TARGETS = sendsigs resolvconf urandom rsyslog umountnfs.sh hwclock.sh networking umountfs umountroot halt reboot
 rsyslog: sendsigs
-umountnfs.sh: sendsigs rsyslog
+umountnfs.sh: rsyslog sendsigs
 hwclock.sh: rsyslog
 networking: umountnfs.sh
-umountfs: umountnfs.sh hwclock.sh urandom networking resolvconf
+umountfs: umountnfs.sh hwclock.sh networking urandom resolvconf
 umountroo...

[Steve Langasek (vorlon)]

kinetic verified:

diff -ur bionic-old/etc/console-setup/cached_setup_keyboard.sh bionic-new/etc/console-setup/cached_setup_keyboard.sh
--- bionic-old/etc/console-setup/cached_setup_keyboard.sh 2023-05-27 04:52:32.038110370 +0000
+++ bionic-new/etc/console-setup/cached_setup_keyboard.sh 2023-05-27 05:14:01.061523804 +0000
@@ -5,4 +5,4 @@
     exit 0
 fi
 kbd_mode '-u'
-loadkeys '/tmp/tmpkbd.RWkHvU' > '/dev/null'
+loadkeys '/tmp/tmpkbd.xwQjgK' > '/dev/null'
Binary files bionic-old/var/lib/systemd/catalog/database and bionic-new/var/lib/systemd/catalog/database differ
Binary files trusty-old/etc/console-setup/cached.kmap.gz and trusty-new/etc/console-setup/cached.kmap.gz differ
Binary files xenial-old/etc/console-setup/cached.kmap.gz and xenial-new/etc/console-setup/cached.kmap.gz differ
diff -ur xenial-old/etc/init.d/.depend.boot xenial-new/etc/init.d/.depend.boot
--- xenial-old/etc/init.d/.depend.boot 2023-05-27 05:10:32.880450036 +0000
+++ xenial-new/etc/init.d/.depend.boot 2023-05-27 05:35:12.680651277 +0000
@@ -1,17 +1,17 @@
-TARGETS = console-setup mountkernfs.sh hostname.sh resolvconf udev hwclock.sh mountdevsubfs.sh checkroot.sh networking urandom procps mountall-bootclean.sh mountall.sh bootmisc.sh checkfs.sh checkroot-bootclean.sh mountnfs.sh mountnfs-bootclean.sh kmod
+TARGETS = console-setup mountkernfs.sh hostname.sh resolvconf udev networking urandom hwclock.sh mountdevsubfs.sh checkroot.sh kmod checkroot-bootclean.sh bootmisc.sh mountall-bootclean.sh mountall.sh mountnfs-bootclean.sh mountnfs.sh checkfs.sh procps
 INTERACTIVE = console-setup udev checkroot.sh checkfs.sh
 udev: mountkernfs.sh
+networking: mountkernfs.sh urandom procps resolvconf
+urandom: hwclock.sh
 hwclock.sh: mountdevsubfs.sh
 mountdevsubfs.sh: mountkernfs.sh udev
 checkroot.sh: hwclock.sh mountdevsubfs.sh hostname.sh
-networking: mountkernfs.sh urandom procps resolvconf
-urandom: hwclock.sh
-procps: mountkernfs.sh udev
+kmod: checkroot.sh
+checkroot-bootclean.sh: checkroot.sh
+bootmisc.sh: checkroot-bootclean.sh mountall-bootclean.sh mountnfs-bootclean.sh udev
 mountall-bootclean.sh: mountall.sh
 mountall.sh: checkfs.sh checkroot-bootclean.sh
-bootmisc.sh: mountall-bootclean.sh udev mountnfs-bootclean.sh checkroot-bootclean.sh
-checkfs.sh: checkroot.sh
-checkroot-bootclean.sh: checkroot.sh
-mountnfs.sh: networking
 mountnfs-bootclean.sh: mountnfs.sh
-kmod: checkroot.sh
+mountnfs.sh: networking
+checkfs.sh: checkroot.sh
+procps: mountkernfs.sh udev
diff -ur xenial-old/etc/init.d/.depend.start xenial-new/etc/init.d/.depend.start
--- xenial-old/etc/init.d/.depend.start 2023-05-27 05:10:32.880450036 +0000
+++ xenial-new/etc/init.d/.depend.start 2023-05-27 05:35:12.680651277 +0000
@@ -1,6 +1,6 @@
-TARGETS = rsyslog killprocs single cron ondemand rc.local
+TARGETS = rsyslog killprocs single cron rc.local ondemand
 INTERACTIVE =
 single: killprocs
 cron: rsyslog
-ondemand: rsyslog cron
 rc.local: rsyslog cron
+ondemand: rsyslog cron
diff -ur xenial-old/etc/init.d/.depend.stop xenial-new/etc/init.d/.depend.stop
--- xenial-old/etc/init.d/.depend.stop 2023-05-27 05:10:32.880450036 +0000
+++ xenial-new/etc/init.d/.depend.stop 2023-05-27 05:35:12.680651277 +0000
@@ -1,...

[Steve Langasek (vorlon)]

jammy:

diff -ur bionic-old/etc/console-setup/cached_setup_keyboard.sh bionic-new/etc/console-setup/cached_setup_keyboard.sh
--- bionic-old/etc/console-setup/cached_setup_keyboard.sh 2023-05-27 05:44:38.076305887 +0000
+++ bionic-new/etc/console-setup/cached_setup_keyboard.sh 2023-05-27 06:07:35.042640002 +0000
@@ -5,4 +5,4 @@
     exit 0
 fi
 kbd_mode '-u'
-loadkeys '/tmp/tmpkbd.HUcuOs' > '/dev/null'
+loadkeys '/tmp/tmpkbd.Nh2cmW' > '/dev/null'
Binary files bionic-old/var/lib/systemd/catalog/database and bionic-new/var/lib/systemd/catalog/database differ
Binary files trusty-old/etc/console-setup/cached.kmap.gz and trusty-new/etc/console-setup/cached.kmap.gz differ
Binary files xenial-old/etc/console-setup/cached.kmap.gz and xenial-new/etc/console-setup/cached.kmap.gz differ
diff -ur xenial-old/etc/init.d/.depend.boot xenial-new/etc/init.d/.depend.boot
--- xenial-old/etc/init.d/.depend.boot 2023-05-27 06:02:41.694973318 +0000
+++ xenial-new/etc/init.d/.depend.boot 2023-05-27 06:29:10.283880347 +0000
@@ -1,17 +1,17 @@
-TARGETS = console-setup mountkernfs.sh hostname.sh resolvconf udev hwclock.sh mountdevsubfs.sh checkroot.sh networking urandom mountall-bootclean.sh mountall.sh bootmisc.sh kmod mountnfs-bootclean.sh mountnfs.sh checkroot-bootclean.sh checkfs.sh procps
+TARGETS = console-setup mountkernfs.sh hostname.sh resolvconf udev networking hwclock.sh mountdevsubfs.sh checkroot.sh urandom mountall.sh checkfs.sh checkroot-bootclean.sh mountnfs-bootclean.sh mountnfs.sh bootmisc.sh mountall-bootclean.sh kmod procps
 INTERACTIVE = console-setup udev checkroot.sh checkfs.sh
 udev: mountkernfs.sh
+networking: mountkernfs.sh urandom procps resolvconf
 hwclock.sh: mountdevsubfs.sh
 mountdevsubfs.sh: mountkernfs.sh udev
 checkroot.sh: hwclock.sh mountdevsubfs.sh hostname.sh
-networking: mountkernfs.sh urandom procps resolvconf
 urandom: hwclock.sh
-mountall-bootclean.sh: mountall.sh
 mountall.sh: checkfs.sh checkroot-bootclean.sh
-bootmisc.sh: mountall-bootclean.sh mountnfs-bootclean.sh udev checkroot-bootclean.sh
-kmod: checkroot.sh
+checkfs.sh: checkroot.sh
+checkroot-bootclean.sh: checkroot.sh
 mountnfs-bootclean.sh: mountnfs.sh
 mountnfs.sh: networking
-checkroot-bootclean.sh: checkroot.sh
-checkfs.sh: checkroot.sh
+bootmisc.sh: mountnfs-bootclean.sh udev mountall-bootclean.sh checkroot-bootclean.sh
+mountall-bootclean.sh: mountall.sh
+kmod: checkroot.sh
 procps: mountkernfs.sh udev
diff -ur xenial-old/etc/init.d/.depend.start xenial-new/etc/init.d/.depend.start
--- xenial-old/etc/init.d/.depend.start 2023-05-27 06:02:41.694973318 +0000
+++ xenial-new/etc/init.d/.depend.start 2023-05-27 06:29:10.283880347 +0000
@@ -1,6 +1,6 @@
-TARGETS = rsyslog killprocs single cron rc.local ondemand
+TARGETS = rsyslog killprocs single cron ondemand rc.local
 INTERACTIVE =
 single: killprocs
 cron: rsyslog
-rc.local: rsyslog cron
 ondemand: rsyslog cron
+rc.local: rsyslog cron
diff -ur xenial-old/etc/init.d/.depend.stop xenial-new/etc/init.d/.depend.stop
--- xenial-old/etc/init.d/.depend.stop 2023-05-27 06:02:41.694973318 +0000
+++ xenial-new/etc/init.d/.depend.stop 2023-05-27 06:29:10.283880347 +0000
@@ -1,9 +1,9 @@
 TARGETS = sendsigs resolvconf urandom r...

[Steve Langasek (vorlon)]

focal:

diff -ur bionic-old/etc/console-setup/cached_setup_keyboard.sh bionic-new/etc/console-setup/cached_setup_keyboard.sh
--- bionic-old/etc/console-setup/cached_setup_keyboard.sh 2023-05-27 16:52:56.620889824 +0000
+++ bionic-new/etc/console-setup/cached_setup_keyboard.sh 2023-05-27 17:53:57.947478847 +0000
@@ -5,4 +5,4 @@
     exit 0
 fi
 kbd_mode '-u'
-loadkeys '/tmp/tmpkbd.ES0zxz' > '/dev/null'
+loadkeys '/tmp/tmpkbd.3svNez' > '/dev/null'
Binary files bionic-old/var/lib/systemd/catalog/database and bionic-new/var/lib/systemd/catalog/database differ
Binary files trusty-old/etc/console-setup/cached.kmap.gz and trusty-new/etc/console-setup/cached.kmap.gz differ
Binary files xenial-old/etc/console-setup/cached.kmap.gz and xenial-new/etc/console-setup/cached.kmap.gz differ
diff -ur xenial-old/etc/init.d/.depend.boot xenial-new/etc/init.d/.depend.boot
--- xenial-old/etc/init.d/.depend.boot 2023-05-27 17:11:47.996820723 +0000
+++ xenial-new/etc/init.d/.depend.boot 2023-05-27 18:12:10.964639161 +0000
@@ -1,17 +1,17 @@
-TARGETS = console-setup mountkernfs.sh hostname.sh resolvconf udev hwclock.sh mountdevsubfs.sh checkroot.sh networking urandom checkfs.sh mountall.sh checkroot-bootclean.sh mountnfs.sh bootmisc.sh mountall-bootclean.sh mountnfs-bootclean.sh procps kmod
+TARGETS = console-setup mountkernfs.sh hostname.sh resolvconf udev urandom hwclock.sh networking mountdevsubfs.sh checkroot.sh kmod checkfs.sh bootmisc.sh mountall.sh checkroot-bootclean.sh mountnfs.sh mountall-bootclean.sh mountnfs-bootclean.sh procps
 INTERACTIVE = console-setup udev checkroot.sh checkfs.sh
 udev: mountkernfs.sh
+urandom: hwclock.sh
 hwclock.sh: mountdevsubfs.sh
+networking: mountkernfs.sh urandom procps resolvconf
 mountdevsubfs.sh: mountkernfs.sh udev
 checkroot.sh: hwclock.sh mountdevsubfs.sh hostname.sh
-networking: mountkernfs.sh urandom procps resolvconf
-urandom: hwclock.sh
+kmod: checkroot.sh
 checkfs.sh: checkroot.sh
+bootmisc.sh: udev checkroot-bootclean.sh mountall-bootclean.sh mountnfs-bootclean.sh
 mountall.sh: checkfs.sh checkroot-bootclean.sh
 checkroot-bootclean.sh: checkroot.sh
 mountnfs.sh: networking
-bootmisc.sh: udev mountall-bootclean.sh checkroot-bootclean.sh mountnfs-bootclean.sh
 mountall-bootclean.sh: mountall.sh
 mountnfs-bootclean.sh: mountnfs.sh
 procps: mountkernfs.sh udev
-kmod: checkroot.sh
diff -ur xenial-old/etc/init.d/.depend.start xenial-new/etc/init.d/.depend.start
--- xenial-old/etc/init.d/.depend.start 2023-05-27 17:11:47.996820723 +0000
+++ xenial-new/etc/init.d/.depend.start 2023-05-27 18:12:10.964639161 +0000
@@ -1,6 +1,6 @@
-TARGETS = rsyslog killprocs single cron rc.local ondemand
+TARGETS = rsyslog killprocs single cron ondemand rc.local
 INTERACTIVE =
 single: killprocs
 cron: rsyslog
-rc.local: rsyslog cron
 ondemand: rsyslog cron
+rc.local: rsyslog cron
diff -ur xenial-old/etc/init.d/.depend.stop xenial-new/etc/init.d/.depend.stop
--- xenial-old/etc/init.d/.depend.stop 2023-05-27 17:11:47.996820723 +0000
+++ xenial-new/etc/init.d/.depend.stop 2023-05-27 18:12:10.964639161 +0000
@@ -1,9 +1,9 @@
 TARGETS = sendsigs resolvconf urandom rsyslog umountnfs.sh hwclock.sh networking umountfs umountroot halt reboot
 rsys...

[Brian Murray (brian-murray)]

Hello Renan, or anyone else affected,

Accepted debootstrap into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.95ubuntu0.13 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted debootstrap (1.0.95ubuntu0.13) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

unattended-upgrades/1.1ubuntu1.18.04.14 (amd64, armhf, i386, ppc64el, s390x)
xen-tools/4.7-1 (ppc64el)

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/bionic/update_excuses.html#debootstrap

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

Thank you!

[Steve Langasek (vorlon)]

bionic:

diff -ur bionic-old/etc/console-setup/cached_setup_keyboard.sh bionic-new/etc/console-setup/cached_setup_keyboard.sh
--- bionic-old/etc/console-setup/cached_setup_keyboard.sh 2023-05-27 20:22:20.596658003 +0000
+++ bionic-new/etc/console-setup/cached_setup_keyboard.sh 2023-05-27 21:22:31.046385284 +0000
@@ -5,4 +5,4 @@
     exit 0
 fi
 kbd_mode '-u'
-loadkeys '/tmp/tmpkbd.SEcyjn' > '/dev/null'
+loadkeys '/tmp/tmpkbd.pjeF6r' > '/dev/null'
Binary files bionic-old/var/lib/systemd/catalog/database and bionic-new/var/lib/systemd/catalog/database differ
Binary files trusty-old/etc/console-setup/cached.kmap.gz and trusty-new/etc/console-setup/cached.kmap.gz differ
Binary files xenial-old/etc/console-setup/cached.kmap.gz and xenial-new/etc/console-setup/cached.kmap.gz differ
diff -ur xenial-old/etc/init.d/.depend.boot xenial-new/etc/init.d/.depend.boot
--- xenial-old/etc/init.d/.depend.boot 2023-05-27 20:40:52.876090140 +0000
+++ xenial-new/etc/init.d/.depend.boot 2023-05-27 21:45:12.192465733 +0000
@@ -1,17 +1,17 @@
-TARGETS = console-setup mountkernfs.sh hostname.sh resolvconf udev urandom hwclock.sh mountdevsubfs.sh checkroot.sh networking checkroot-bootclean.sh bootmisc.sh mountnfs-bootclean.sh mountnfs.sh mountall-bootclean.sh mountall.sh checkfs.sh procps kmod
+TARGETS = console-setup mountkernfs.sh hostname.sh resolvconf udev urandom hwclock.sh networking mountdevsubfs.sh checkroot.sh procps bootmisc.sh mountnfs.sh mountall.sh checkfs.sh checkroot-bootclean.sh mountall-bootclean.sh mountnfs-bootclean.sh kmod
 INTERACTIVE = console-setup udev checkroot.sh checkfs.sh
 udev: mountkernfs.sh
 urandom: hwclock.sh
 hwclock.sh: mountdevsubfs.sh
+networking: mountkernfs.sh urandom procps resolvconf
 mountdevsubfs.sh: mountkernfs.sh udev
 checkroot.sh: hwclock.sh mountdevsubfs.sh hostname.sh
-networking: mountkernfs.sh urandom procps resolvconf
-checkroot-bootclean.sh: checkroot.sh
-bootmisc.sh: checkroot-bootclean.sh mountnfs-bootclean.sh mountall-bootclean.sh udev
-mountnfs-bootclean.sh: mountnfs.sh
+procps: mountkernfs.sh udev
+bootmisc.sh: udev mountall-bootclean.sh mountnfs-bootclean.sh checkroot-bootclean.sh
 mountnfs.sh: networking
-mountall-bootclean.sh: mountall.sh
 mountall.sh: checkfs.sh checkroot-bootclean.sh
 checkfs.sh: checkroot.sh
-procps: mountkernfs.sh udev
+checkroot-bootclean.sh: checkroot.sh
+mountall-bootclean.sh: mountall.sh
+mountnfs-bootclean.sh: mountnfs.sh
 kmod: checkroot.sh
diff -ur xenial-old/etc/init.d/.depend.start xenial-new/etc/init.d/.depend.start
--- xenial-old/etc/init.d/.depend.start 2023-05-27 20:40:52.876090140 +0000
+++ xenial-new/etc/init.d/.depend.start 2023-05-27 21:45:12.192465733 +0000
@@ -1,6 +1,6 @@
-TARGETS = rsyslog killprocs single cron rc.local ondemand
+TARGETS = rsyslog killprocs single cron ondemand rc.local
 INTERACTIVE =
 single: killprocs
 cron: rsyslog
-rc.local: rsyslog cron
 ondemand: rsyslog cron
+rc.local: rsyslog cron
diff -ur xenial-old/etc/init.d/.depend.stop xenial-new/etc/init.d/.depend.stop
--- xenial-old/etc/init.d/.depend.stop 2023-05-27 20:40:52.876090140 +0000
+++ xenial-new/etc/init.d/.depend.stop 2023-05-27 21:45:12.192465733 +0000
@@ -3,7 +3,7 @@
 umountnfs.sh: rsysl...

[Dimitri John Ledkov (xnox)]

$ mk-sbuild jammy
Specified release (jammy) not known to debootstrap

$ dpkg-query -W debootstrap ubuntu-dev-tools
debootstrap 1.0.126+nmu1ubuntu0.3
ubuntu-dev-tools 0.189

Verification failed on Jammy.

this update to debootstrap breaks ubuntu-dev-tools mk-sbuild tool, when trying to create any old/supported/new releases.

Note in kinetic ubuntu-dev-tools was fixed to hard-coded use gutsy symlink, but this change is not in Jammy and earlier releases.

See https://git.launchpad.net/ubuntu-dev-tools/commit/?id=1f3e4a5ad75cc639a320ead8ef2771ed2a4172ed

Updating debootstrap in jammy and lower, will break all users of mk-sbuild.

[Łukasz Zemczak (sil2100)]

The version of debootstrap in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the target series has reached its End of Life.

[Launchpad Janitor (janitor)]

This bug was fixed in the package debootstrap - 1.0.127ubuntu1.2

---------------
debootstrap (1.0.127ubuntu1.2) kinetic; urgency=medium

  * Update debootstrap to automatically use the gutsy script by default
    if the target is an Ubuntu release known to distro-info, eliminating
    the need to upload debootstrap for each new Ubuntu release.
  * Add dependency on distro-info, which is part of ubuntu-minimal, for the
    above
  * Remove all the old symlinks that are no longer needed.
  * LP: #2020530.

 -- Steve Langasek <email address hidden> Fri, 26 May 2023 22:17:22 +0000

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for debootstrap has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package debootstrap - 1.0.128+nmu2ubuntu1.1

---------------
debootstrap (1.0.128+nmu2ubuntu1.1) lunar; urgency=medium

  * Update debootstrap to automatically use the gutsy script by default
    if the target is an Ubuntu release known to distro-info, eliminating
    the need to upload debootstrap for each new Ubuntu release.
  * Add dependency on distro-info, which is part of ubuntu-minimal, for the
    above
  * Remove all the old symlinks that are no longer needed.
  * LP: #2020530.

 -- Steve Langasek <email address hidden> Fri, 26 May 2023 22:14:38 +0000

[Chris Halse Rogers (raof)]

Hello Renan, or anyone else affected,

Accepted ubuntu-dev-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-dev-tools/0.193ubuntu4~20.04.1 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-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. 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.

[Chris Halse Rogers (raof)]

Hello Renan, or anyone else affected,

Accepted ubuntu-dev-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-dev-tools/0.193ubuntu4~22.04.1 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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Chris Halse Rogers (raof)]

Hello Renan, or anyone else affected,

Accepted ubuntu-dev-tools into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-dev-tools/0.193ubuntu4~22.10.1 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-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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.

[Chris Halse Rogers (raof)]

Hello Renan, or anyone else affected,

Accepted ubuntu-dev-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-dev-tools/0.193ubuntu4~20.04.2 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-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. 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.

[Chris Halse Rogers (raof)]

Hello Renan, or anyone else affected,

Accepted ubuntu-dev-tools into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-dev-tools/0.193ubuntu4~23.04.1 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-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. 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.

[Chris Halse Rogers (raof)]

An upload of debootstrap to lunar-proposed has been rejected from the upload queue for the following reason: "No SRU bug, adds a Breaks that doesn't apply to the version in lunar *or* kinetic, so will never be triggered?".

[Steve Langasek (vorlon)]

sg sbuild -c 'mk-sbuild --skip-proposed mantic' succeeds in lunar, so marking this verification-done for lunar.

[Steve Langasek (vorlon)]

sg sbuild -c 'mk-sbuild --skip-proposed mantic' succeeds in kinetic.

[Steve Langasek (vorlon)]

Waiting for acceptance of new debootstrap into jammy and focal for end-to-end verification of the mk-sbuild test case.

[Chris Halse Rogers (raof)]

Hello Renan, or anyone else affected,

Accepted debootstrap into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.118ubuntu1.10 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-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. 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.

[Chris Halse Rogers (raof)]

Hello Renan, or anyone else affected,

Accepted debootstrap into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.126+nmu1ubuntu0.4 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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Chris Halse Rogers (raof)]

An upload of debootstrap to kinetic-proposed has been rejected from the upload queue for the following reason: "Kinetic already has a sufficient version of ubuntu-dev-tools, and any upgrade of Jammy will pull in updates first or not have updates enabled and won't see this either".

[Steve Langasek (vorlon)]

Only change to debootstrap from previous upload is the addition of Breaks: so I'm not re-testing debootstrap of all series.

jammy:

$ sudo apt install ubuntu-dev-tools
$ sg sbuild -c 'mk-sbuild --skip-proposed mantic'
Specified release (mantic) not known to debootstrap
$
# enable proposed
$ sudo apt install debootstrap
-> correctly pulls in new ubuntu-dev-tools as well due to breaks
$ sg sbuild -c 'mk-sbuild --skip-proposed mantic'
-> succeeds
$

[Steve Langasek (vorlon)]

And for focal; again, not re-testing debootstrap of all series.

$ sudo apt install ubuntu-dev-tools
$ sg sbuild -c 'mk-sbuild --skip-proposed mantic'
Specified release (mantic) not known to debootstrap
$
# enable proposed
$ sudo apt install debootstrap
-> correctly pulls in new ubuntu-dev-tools as well due to breaks
$ sg sbuild -c 'mk-sbuild --skip-proposed mantic'
-> succeeds
$