#1109454 cdebootstrap: autopkgtest regression: Couldn't download Release!

#1109454#5
Date:
2025-07-18 09:31:06 UTC
From:
To:
Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails since July
2025 in unstable and testing, but also in stable and oldstable. Can you
please investigate the situation and fix it? I copied some of the output
at the bottom of this report.

The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing.

More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

As this is a test only issue, with my Release Team member hat on I have
tagged it such that it won't be auto-removed before the release as it's
so late in the freeze and it's not worth removing the package from
trixie because of this at this moment.

Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cdebootstrap/62220238/log.gz

126s autopkgtest [07:11:23]: test buster-standard: [-----------------------
127s D: Read suites config from /usr/share/cdebootstrap
127s D: Searching initial config, using origin Debian and codename buster
127s D: Found initial config, specifies keyring
debian-archive-keyring.gpg, mirror http://deb.debian.org/debian
127s D: Using mirror http://deb.debian.org/debian
127s D: Using keyring /usr/share/keyrings/debian-archive-keyring.gpg
127s P: Retrieving Release
127s D: Downloading http://deb.debian.org/debian/dists/buster/Release
127s E: Couldn't download Release!
127s autopkgtest [07:11:24]: test buster-standard: -----------------------]

#1109454#10
Date:
2025-07-21 14:48:58 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
cdebootstrap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1109454@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Blank <waldi@debian.org> (supplier of updated cdebootstrap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Mon, 21 Jul 2025 16:33:58 +0200
Source: cdebootstrap
Architecture: source
Version: 0.7.9
Distribution: unstable
Urgency: medium
Maintainer: Bastian Blank <waldi@debian.org>
Changed-By: Bastian Blank <waldi@debian.org>
Closes: 1109454
Changes:
 cdebootstrap (0.7.9) unstable; urgency=medium
 .
   * Test current Debian releases.  (closes: #1109454)
Checksums-Sha1:
 3e83070ce04bee6bbfd35533472fdf36734f8f93 1075 cdebootstrap_0.7.9.dsc
 14b11b60967388146a596a7171a0a1df9fa8f4bf 32372 cdebootstrap_0.7.9.tar.xz
 f2aca3a42f48c8bec7177f2c79ec2c256efc0e29 6137 cdebootstrap_0.7.9_source.buildinfo
Checksums-Sha256:
 50852d525b3a9cddda97e9d660bc1fd36e5ee08d9aebb215123800590967315a 1075 cdebootstrap_0.7.9.dsc
 40a58b4684ba89ea41347d0c81f424bf06734870d0ac4ff683fa77246ad14346 32372 cdebootstrap_0.7.9.tar.xz
 c35864e7330ed8eb494742b540ee57f29c1f5db265215f1bb273d26a14760825 6137 cdebootstrap_0.7.9_source.buildinfo
Files:
 02e325c78409f11f8416a0487eeacd74 1075 admin optional cdebootstrap_0.7.9.dsc
 6e5d57051b81ec9da074805f5b738b59 32372 admin optional cdebootstrap_0.7.9.tar.xz
 3b590397ccc365e1817bea539f840a8e 6137 admin optional cdebootstrap_0.7.9_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQQ8pEKDNIgQDAQDOBFji0aBW7swjwUCaH5QIgAKCRBji0aBW7sw
j113AP9Uwf5NyfUW07tX26VleffB3ypxHSxeYOUMQuCdmjS0HAEAyYqAbZnedTp8
CuUE44T7y4gbOAAEUInLjGo1CYMP4AI=
=rTrU
-----END PGP SIGNATURE-----

#1109454#15
Date:
2025-07-27 08:02:41 UTC
From:
To:
Hi,
suite name? That way the test in (old|)stable will also tell if you can
still bootstrap testing with the version in (old|)stable.

Or alternatively, make the tests "Restriction: skippable" and exit with
77 when the suite no longer exists in the archive?

But let's not do this for trixie, I'll hint what we have now.

Paul