Bug#998867: marked as done (debootstrap: --no-merged-usr became a no-op)

2021-11-28 Thread Debian Bug Tracking System
Your message dated Sun, 28 Nov 2021 12:03:25 + with message-id and subject line Bug#998867: fixed in debootstrap 1.0.126+nmu1 has caused the Debian Bug report #998867, regarding debootstrap: --no-merged-usr became a no-op to be marked as done. This means that you claim that the problem has

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 repository

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

Processed: Re: debootstrap: --no-merged-usr became a no-op

2021-11-18 Thread Debian Bug Tracking System
Processing control commands: > affects -1 mmdebstrap Bug #998867 [debootstrap] debootstrap: --no-merged-usr became a no-op Added indication that 998867 affects mmdebstrap -- 998867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998867 Debian Bug Tracking System Contact ow...@bugs.debian.

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 h

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 that

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

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.

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 b

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

Bug#872725: installation-reports: When installing with a encrypted swap, device was saved as /dev/sda2 in /etc/crypttab, but on first boot devices had been switched (sda became sdb, and vice versa).

2017-08-20 Thread Cyril Brulebois
Hi Julien, Julien Lecomte (2017-08-20): > Boot method: CD on USB flashdrive > Image version: latest debian 9 available on site (as of 2017-08-19) > Date: 2017-08-20 > > Machine: built > Partitions: cf. below > > Initial boot: [O] > Detect network card:[O] > Configure network:

Bug#872725: installation-reports: When installing with a encrypted swap, device was saved as /dev/sda2 in /etc/crypttab, but on first boot devices had been switched (sda became sdb, and vice versa).

2017-08-20 Thread Julien Lecomte
Package: installation-reports Severity: important Dear Maintainer, -- Package-specific info: Boot method: CD on USB flashdrive Image version: latest debian 9 available on site (as of 2017-08-19) Date: 2017-08-20 Machine: built Partitions: cf. below Initial boot: [O] Detect network ca

Bug#382424: D-I hangs: /cdrom became /media/cdrom0

2006-08-24 Thread Geert Stappers
retitle 382424 D-I hangs: /cdrom became /media/cdrom0 thanks # clone 382424 -1 # reassign -1 apt On Wed, Aug 23, 2006 at 08:58:23PM +0200, Jens Seidel wrote: > > I can now reproduce it and found also the problem: > APT is not able to mount a Debian CD, since APT searchs by default in

Processed: Re: Bug#382424: D-I hangs: /cdrom became /media/cdrom0

2006-08-24 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > retitle 382424 D-I hangs: /cdrom became /media/cdrom0 Bug#382424: D-I hangs (APT fails to mount the CD) Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system adminis

became

2004-05-20 Thread Dianne
Mullen, Govenment don't want me to sell UndergroundCD !Check Your spouse and staff Investigate Your Own CREDIT-HISTORY hacking someone PC! Disappear in your city bannedcd2004 http://www.9008hosting.com/cd/ piece,admitted without hindrance.