> > > > Thus a third thing the README could advise on is how Debian Developers
> > > > and
> > > > Debian sysadmins are advised to build CI systems and test upgrade paths
> > > > for
> > > > the next 10 years as what worked in the past 10 years does not apply
> > > > as-is
> > > > anymore.
> >
> > Just create the chroot for the CI with --merged-usr and all will be
> > fine. Debootstrap in Buster is not going to be updated to do it
> > automatically, only in Bookworm/Bullseye.
>
> Thanks Luca for clarification. So seems we need to get bookworm
> removed from
>
> > One more clarifying question:
> >
> > > > Thus a third thing the README could advise on is how Debian Developers
> > > > and
> > > > Debian sysadmins are advised to build CI systems and test upgrade paths
> > > > for
> > > > the next 10 years as what worked in the past 10 years does not
On Thu, 23 Nov 2023 at 05:45, Otto Kekäläinen wrote:
>
> Hi!
>
> One more clarifying question:
>
> > > Thus a third thing the README could advise on is how Debian Developers and
> > > Debian sysadmins are advised to build CI systems and test upgrade paths
> > > for
> > > the next 10 years as
Hi!
One more clarifying question:
> > Thus a third thing the README could advise on is how Debian Developers and
> > Debian sysadmins are advised to build CI systems and test upgrade paths for
> > the next 10 years as what worked in the past 10 years does not apply as-is
> > anymore.
> People
Hi!
Thanks for the reponse - I am impressed by your ability to respond
almost immediately! However, should the bug report be left open for a
while and not immediately closed? Are you willing to review/merge if
somebody else submits an improvement to the README at
Source: usrmerge
Source-Version: 38
Severity: wishlist
Summary:
Please extend the Debian.README in usrmerge to explain:
- In what releases of the most popular Debian derivatives will the usrmerge
apply?
- Did any of the popular ones fork usrmerge? Does that have any
implications of Debian
7 matches
Mail list logo
