Hi, Quoting Antoine Beaupré (2024-12-23 02:31:29) > On 2024-12-22 22:57:37, Johannes Schauer Marin Rodrigues wrote: > > Quoting Antoine Beaupré (2024-12-22 22:39:51) > >> > In your mind, what should sbuild add to support this? > >> > > >> > I can only think of one logical implementation and that is to add yet > >> > another > >> > mangling/mapping option which expresses equivalence relationships or > >> > aliases of > >> > distribution names and if one is requested and the other already exists, > >> > just > >> > use that. The problem then is: which extra-args or distro-mangle options > >> > do you > >> > apply? Will those be mapped too? Which one will take precedence? > >> > >> Why not just use the existing logic from? > >> > >> > I: Applied base distribution name mangle rule > >> > s/(?^:^(experimental|rc-buggy|UNRELEASED)$)/unstable/ turning > >> > "UNRELEASED" into "unstable" > > > > that one is for retrieving a base distribution for what is otherwise an > > overlay. For example, experimental is an overlay to unstable and > > bookworm-backports is an overlay for bookworm. You cannot create a chroot of > > bookworm-security -- you have to create a chroot for bookworm and then you > > can > > add the security archive on top. It would be wrong to use a bookworm chroot > > for > > somebody who wants to build for bookworm-backports. So the > > UNSHARE_MMDEBSTRAP_DISTRO_MANGLE option cannot be used for this. > > I don't understand: how does that differ from the need expressed here?
I understand that it makes sense to symlink UNRELEASED->unstable as
"UNRELEASED" is supposed to be an alias to "unstable". Indeed the schroot-based
man page of sbuild-createchroot suggests to run:
sudo sbuild-createchroot unstable ... --alias=sid --alias=UNRELEASED ...
But this would be wrong for bookworm-backports or bookworm-security, for
example which are two mangling rules that are created by default:
https://sources.debian.org/src/sbuild/0.88.1/lib/Sbuild/Conf.pm/#L427
If this variable were to be re-used then somebody who intends to build for
bookworm-backports would have a chroot for just bookworm, without backports
extracted. That is wrong.
Instead I think what you need here is what aliases used to be for schroot and
that would be a new mapping option which would replace the symlink mechanism.
Does that make sense?
Thanks!
cheers, josch
signature.asc
Description: signature
