Comment 2 for bug 1986775

Revision history for this message
Chad Smith (chad.smith) wrote : Re: schroot 1.6.12-2 incompatible with sbuild-launchpad-chroot

Confirmed a second failure mode here on this bug, newly created schroots in Jammy++ will also prompt and fail when trying to sbuild a package locally.

sbuild --resolve-alternatives --dist=kinetic --arch=amd64 --arch-all ../out/cloud-init_22.3-13-g70ce6442-0ubuntu1~22.10.2.dsc
sbuild (Debian sbuild) 0.81.2ubuntu6 (16 February 2022) on downtown

+=======================================================================================+
| cloud-init 22.3-13-g70ce6442-0ubuntu1~22.10.2 (amd64) Fri, 07 Oct 2022 17:51:21 +0000 |
+=======================================================================================+

Package: cloud-init
Version: 22.3-13-g70ce6442-0ubuntu1~22.10.2
Source Version: 22.3-13-g70ce6442-0ubuntu1~22.10.2
Distribution: kinetic
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

E: /etc/schroot/chroot.d/kinetic-amd64: line 13 [kinetic-amd64] aliases: kinetic-security+main-amd64: Invalid name
I: Naming restrictions are documented in schroot.conf(5)