Bug#998867: debootstrap: --no-merged-usr became a no-op

2021-11-28 Thread Johannes Schauer Marin Rodrigues
Hi, the last maintainer action to this bug was 13 days ago, Adam Borowski points out how this breaks buildds, Julien Cristau explains how this change has undesired consequences elsewhere and it breaks my own package mmdebstrap. I saw no changes related to this bug in the development git

Bug#998867: debootstrap: --no-merged-usr became a no-op

2021-11-22 Thread Julien Cristau
On Mon, Nov 15, 2021 at 01:54:36PM +, Dimitri John Ledkov wrote: > > Also, build chroots must still be created without merged-usr for > > sid/bookworm, until something's been done to migrate user systems. > > But Julien, you said that buildds run stable, meaning they are > unaffected by this

Bug#998867: debootstrap: --no-merged-usr became a no-op

2021-11-18 Thread Johannes Schauer Marin Rodrigues
Control: affects -1 mmdebstrap Hi, Quoting Dimitri John Ledkov (2021-11-15 14:54:36) > > Please point out what you plan to do about this change in debootstrap so > > that I can adapt the mmdebstrap autopkgtest accordingly. > > I did notice the mmdebstrap autopkgtest regression. [...] this bug

Bug#998867: debootstrap: --no-merged-usr became a no-op

2021-11-15 Thread Dimitri John Ledkov
There are multiple issues reported in a single bug. > This means that I cannot create a Debian chroot from Debian unstable from 10 > years ago from snapshot.debian.org without merged-/usr and thus my chroot > will behave differently as it did back then. > Please re-enable --no-merged-usr so

Bug#998867: debootstrap: --no-merged-usr became a no-op

2021-11-09 Thread Johannes Schauer Marin Rodrigues
Quoting Julien Cristau (2021-11-09 09:33:14) > On Tue, Nov 09, 2021 at 07:49:03AM +0100, Johannes Schauer Marin Rodrigues > wrote: > > since 1.0.126 the --no-merged-usr option became a no-op if for any code > > name but > > etch*|lenny|squeeze|wheezy|jessie*|stretch|ascii|buster|beowulf|bullseye

Processed: Re: Bug#998867: debootstrap: --no-merged-usr became a no-op

2021-11-09 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #998867 [debootstrap] debootstrap: --no-merged-usr became a no-op Severity set to 'grave' from 'important' -- 998867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998867 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#998867: debootstrap: --no-merged-usr became a no-op

2021-11-09 Thread Julien Cristau
Control: severity -1 grave On Tue, Nov 09, 2021 at 07:49:03AM +0100, Johannes Schauer Marin Rodrigues wrote: > Package: debootstrap > Version: 1.0.126 > Severity: important > > Hi, > > since 1.0.126 the --no-merged-usr option became a no-op if for any code > name but >

Bug#998867: debootstrap: --no-merged-usr became a no-op

2021-11-08 Thread Johannes Schauer Marin Rodrigues
Package: debootstrap Version: 1.0.126 Severity: important Hi, since 1.0.126 the --no-merged-usr option became a no-op if for any code name but etch*|lenny|squeeze|wheezy|jessie*|stretch|ascii|buster|beowulf|bullseye This means that I cannot create a Debian chroot from Debian unstable from 10