On Thu, 23 Feb 2023 at 22:53, Santiago Vila wrote:
>
> El 23/2/23 a las 22:26, Luca Boccassi escribió:
> > On Thu, 23 Feb 2023 at 20:50, Santiago Vila wrote:
> >> The buildds already did the switch several months ago.
> >
> > Wait, what? Specific changes were made to debootstrap in order to
> >
El 23/2/23 a las 22:26, Luca Boccassi escribió:
On Thu, 23 Feb 2023 at 20:50, Santiago Vila wrote:
The buildds already did the switch several months ago.
Wait, what? Specific changes were made to debootstrap in order to
allow the buildd machines to stay un-merged, as the CTTE wanted,
Can y
On Thu, 23 Feb 2023 at 20:50, Santiago Vila wrote:
>
> El 23/2/23 a las 21:38, Luca Boccassi escribió:
> > It's too soon for this. I think the right time will be the first point
> > release of Bookworm - at that point we can get the buildds to switch
> > too. But the release should be built in the
El 23/2/23 a las 21:38, Luca Boccassi escribió:
It's too soon for this. I think the right time will be the first point
release of Bookworm - at that point we can get the buildds to switch
too. But the release should be built in the current default as per
CTTE's instructions.
The buildds already
On Thu, 23 Feb 2023 20:00:42 +0100 Santiago Vila
wrote:
> Package: debootstrap
> Version: 1.0.128+nmu2
> Severity: important
> Tags: patch
>
> Dear maintainer:
>
> Because Debian has decided that bookworm will have
> usr-merge by default even for building packages,
> I would expect usr-merge to
Package: debootstrap
Version: 1.0.128+nmu2
Severity: important
Tags: patch
Dear maintainer:
Because Debian has decided that bookworm will have
usr-merge by default even for building packages,
I would expect usr-merge to be enabled by default
in all cases, including when using the buildd profile.
6 matches
Mail list logo
