Re: Request for review of debootstrap change [was: Re: Second take at DEP17 - consensus call on /usr-merge matters]

2023-08-13 Thread Holger Levsen
On Fri, Aug 11, 2023 at 10:56:03PM +0200, Helmut Grohne wrote: > > what about cdebootstrap? > cdebootstrap (and mmdebstrap) never implemented a merging step[1] and to > this date rely on the usrmerge package doing it at postinst time. Once > base-files ships the aliasing symlinks, both will

Re: Request for review of debootstrap change [was: Re: Second take at DEP17 - consensus call on /usr-merge matters]

2023-08-11 Thread Helmut Grohne
Hi Holger, On Fri, Aug 11, 2023 at 09:28:51AM +, Holger Levsen wrote: > On Fri, Aug 11, 2023 at 09:38:02AM +0100, Luca Boccassi wrote: > > > This is implemented in > > > https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/96 > > what about cdebootstrap? cdebootstrap (and

Re: Request for review of debootstrap change [was: Re: Second take at DEP17 - consensus call on /usr-merge matters]

2023-08-11 Thread Holger Levsen
On Fri, Aug 11, 2023 at 09:38:02AM +0100, Luca Boccassi wrote: > > This is implemented in > > https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/96 what about cdebootstrap? -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org

Re: Request for review of debootstrap change [was: Re: Second take at DEP17 - consensus call on /usr-merge matters]

2023-08-11 Thread Luca Boccassi
On Fri, 11 Aug 2023 at 05:52, Helmut Grohne wrote: > > Hi, > > This is picking up on the debootstrap matter and is kinda crucial. > > On Thu, Jul 13, 2023 at 01:31:04AM +0100, Luca Boccassi wrote: > > > After having sorted this out, what part of your safety concerns with 3C > > > do remain? > > >

Request for review of debootstrap change [was: Re: Second take at DEP17 - consensus call on /usr-merge matters]

2023-08-10 Thread Helmut Grohne
Hi, This is picking up on the debootstrap matter and is kinda crucial. On Thu, Jul 13, 2023 at 01:31:04AM +0100, Luca Boccassi wrote: > > After having sorted this out, what part of your safety concerns with 3C > > do remain? > > Nothing, as that stemmed from a misunderstanding of what the >