Hi, Quoting Santiago Vila (2025-03-04 23:57:52) > Yes, it seems related to the handling of aliases. > > In case this happens to somebody else, there is a simple > workaround: I added "aliases=unstable" to the schroot snippet and then it > worked again.
maybe the fix is easier than I thought. Your problem happened because you name
your chroots "sid" and there exists a mapping sid->unstable by default so your
chroots do not get found. The goal of this change was to automatically map
UNRELEASED to unstable to avoid an extra tarball for the unshare backend
(#1089035). We could fix this by just removing the sid->unstable mapping. This
would leave a problem for people who name their schroot 'UNRELEASED' instead of
using an alias in their sid schroot config. But it's probably rare enough for
people having an extra UNRELEASED schroot in addition to their sid/unstable
schroot, right?
--- a/lib/Sbuild/Conf.pm
+++ b/lib/Sbuild/Conf.pm
@@ -951,7 +951,6 @@ $unshare_mmdebstrap_extra_args = [
GROUP => 'Chroot options',
DEFAULT => {
"UNRELEASED" => "unstable",
- "sid" => "unstable",
"rc-buggy" => "experimental"
},
HELP =>
Thanks!
cheers, josch
signature.asc
Description: signature
