vcswatch reports that
this package seems to have a new changelog entry (version
1.0.142, distribution
UNRELEASED) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit 156ec8fc93c6820b7653ef4996e84b760879fa83
Merge: 23af3e7 db37c22
Author: Luca Boccassi <bluca@debian.org>
Date: Sun Jun 29 09:35:01 2025 +0000
Merge branch 'dawn' into 'master'
PureOS: Add symlinks for dawn and landing
See merge request installer-team/debootstrap!140
commit db37c2218886b16585b972704ff4ab0a0c2b83b4
Author: Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>
Date: Sun Jun 29 06:27:20 2025 +0200
PureOS: Add symlinks for dawn and landing
commit 23af3e768c7781c19e025f9f62f0e2f0dcb88761
Author: Steve McIntyre <steve@einval.com>
Date: Sun Jun 22 21:47:36 2025 +0100
fstab: add more helpful boilerplate.
Thanks to Marc Haber for the suggestion. Closes: #1107594
commit f743a98b0733572619d1c3c8cad971e8e3f3550a
Merge: 8457f34 bea8aec
Author: Luca Boccassi <bluca@debian.org>
Date: Wed Jun 4 13:58:28 2025 +0000
Merge branch 'arch-all-foreign-bootstrap' into 'master'
functions: Fix support for modern-style arch:all with foreign bootstrap
See merge request installer-team/debootstrap!139
commit bea8aec547715588e8137557b8fe95e717592c7b
Author: Jonathon Hall <jonathon.hall@puri.sm>
Date: Wed May 28 11:04:49 2025 -0400
functions: Fix support for modern-style arch:all with foreign bootstrap
Commit 5fa79061 ("Implement support for repos with modern-style
arch:all support") added support for modern-style arch:all - where the
architecture-specific release files do not list packages for arch all;
they're in a separate list.
However, it did not work for foreign bootstrap when the second stage is
performed separately. The second stage relied on a global
"ARCH_ALL_SUPPORTED" being set by the first stage, which doesn't happen
when they are executed separately. This caused PureOS Crimson to fail
a foreign bootstrap, because dpkg could not record the selection of
cron-daemon-common (an arch:all pre-dependency of cron).
Additionally, it appears this would not have been precisely correct for
multiple suites. Most logic would use the ARCH_ALL_SUPPORTED value of
the last suite for all suites. download_release_indices would have
carried over the 'all' from prior suites to later suites, possibly
duplicating it if more than one suite supports all.
Don't use global state for this. Check support for each suite when
needed.
Signed-off-by: Jonathon Hall <jonathon.hall@puri.sm>
![[bug history graph]](https://qa.debian.org/data/bts/graphs/d/debootstrap.png){kind=link}