Monday, 16 November 2026

Re: Default suites for mmdebstrap and sbuild with unshare

On Tue, 2026-11-17 at 02:17 +0100, Benjamin Drung via ubuntu-devel wrote: > Hi everyone, > > Currently sbuild has some rough edges when using it with mmdebstrap to > build the unshare tarballs. I currently have some config options to make > it work as I expect it. To make that a more pleasant experience out of > the box, I want to hear your opinion what should be the default. I have > two questions: > > What suites do expect when building a package against a given suite? > > What suites do you expect when building a chroot with mmdebstrap? > > For the sbuild case we should probably enable the same suite as > Launchpad does. The tricky part is the default for sbuild VS mmdebstrap. > I came up with this proposal: > > $suite-release -> $suite > $suite-security -> $suite > $suite-updates -> $suite $suite-updates > $suite-proposed -> $suite $suite-updates $suite-proposed > $suite-backports -> $suite $suite-updates $suite-backports > > mmdebstrap should always add $suite-security provided by > security.ubuntu.com as default setting. So should the main mirror also > add $suites-security? > > IMO the best default for mmdebstrap is to map $suite to $suite-updates > and for sbuild to map $suite to $suite-proposed. And one more question: Which components do you expect as default? IMO main plus universe would be a good default. -- Benjamin Drung Debian & Ubuntu Developer -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel