On Sun, Jun 19, 2016 at 06:19:09PM +0100, Simon McVittie wrote:
> Package: init
> Version: 1.34
>
> On Mon, 13 Oct 2014 at 13:12:42 +0200, Santiago Vila wrote:
> > Before systemd arrived, it was possible to have a chroot free from
> > init packages (not needed to build packages).
>
> This was
Control: reassign -1 general
Control: retitle -1 init should not be Essential
On Tue, Dec 16, 2014 at 12:04:17 +0100, Holger Levsen wrote:
control: reassign -1 debootstrap
control: retitle -1 variant=buildd should not install init systems
Hi,
On Montag, 13. Oktober 2014, Joey Hess wrote:
control: reassign -1 debootstrap
control: retitle -1 variant=buildd should not install init systems
Hi,
On Montag, 13. Oktober 2014, Joey Hess wrote:
It seems reasonable for debootstrap --variant=buildd to omit any init
systems, if it doesn't already.
seems reasonable indeed, reassigning
control: reassign -1 general
signature.asc
Description: This is a digitally signed message part.
Package: general
Before systemd arrived, it was possible to have a chroot free from
init packages (not needed to build packages).
Now if I do apt-get dist-upgrade inside a minimal chroot (using
schroot here), I get this:
The following NEW packages will be installed:
acl adduser dmsetup init
On 2014-10-13 13:12, Santiago Vila wrote:
Package: general
Before systemd arrived, it was possible to have a chroot free from
init packages (not needed to build packages).
[...]
In either case, the end result is that I'm forced to install init
packages in a chroot which is used to
On Mon, Oct 13, 2014 at 01:43:29PM +0200, Niels Thykier wrote:
In Wheezy, sysvinit was essential, so you would have the same issue in
stable (just with a different init system).
Oops. You are right. So this is not really a regression, only an
undesirable feature that we have had in the system
On Oct 13, Santiago Vila sanv...@unex.es wrote:
Oops. You are right. So this is not really a regression, only an
undesirable feature that we have had in the system for a long time.
I would be happy to fix it FWIW, but I am not sure that there is
a way to do it outside of debootstrap which will
On Mon, Oct 13, 2014 at 02:34:39PM +0200, Marco d'Itri wrote:
On Oct 13, Santiago Vila sanv...@unex.es wrote:
Oops. You are right. So this is not really a regression, only an
undesirable feature that we have had in the system for a long time.
I would be happy to fix it FWIW, but I am not
Santiago Vila wrote:
Before systemd arrived, it was possible to have a chroot free from
init packages (not needed to build packages).
It seems reasonable for debootstrap --variant=buildd to omit any init
systems, if it doesn't already.
--
see shy jo
signature.asc
Description: Digital
Hi,
Joey Hess jo...@debian.org writes:
Santiago Vila wrote:
Before systemd arrived, it was possible to have a chroot free from
init packages (not needed to build packages).
It seems reasonable for debootstrap --variant=buildd to omit any init
systems, if it doesn't already.
It seems a bit
control: reassign -1 debootstrap
control: retitle -1 variant=buildd should not install init systems
Hi,
On Montag, 13. Oktober 2014, Joey Hess wrote:
It seems reasonable for debootstrap --variant=buildd to omit any init
systems, if it doesn't already.
seems reasonable indeed, reassigning
Holger Levsen hol...@layer-acht.org (2014-10-13):
control: reassign -1 debootstrap
control: retitle -1 variant=buildd should not install init systems
Hi,
On Montag, 13. Oktober 2014, Joey Hess wrote:
It seems reasonable for debootstrap --variant=buildd to omit any init
systems, if it
13 matches
Mail list logo
