[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#765076: marked as done (init should not be Essential)

Your message dated Sun, 19 Jun 2016 18:19:09 +0100
with message-id <20160619171908.GA23691@perpetual.pseudorandom.co.uk>
and subject line Re: Bug#765076: general: No way to have a clean chroot for building packages
has caused the Debian Bug report #765076,
regarding init should not be Essential
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

765076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765076
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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 libcap2-bin libcryptsetup4 libdevmapper1.02.1 libkmod2 libncursesw5 libprocps3
  libudev1 procps systemd systemd-sysv udev
0 upgraded, 15 newly installed, 0 to remove and 0 not upgraded.
Need to get 4614 kB of archives.
After this operation, 21.9 MB of additional disk space will be used.
Do you want to continue? [Y/n] 

I'm not sure what package is to blame here (which is why I'm using
"general"). Maybe it is the introduction of a new essential package
called "init", combined with the fact that apt-get insists that all
essential packages should be installed.

In either case, the end result is that I'm forced to install init
packages in a chroot which is used to build packages, something that
didn't happen in wheezy. This is clearly a regression and I hope that
it is fixed before the release of jessie.

Please reassign/clone as appropriate.


--- End Message ---
--- Begin Message ---
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 the case in jessie due to the transitional packages necessary
to move from sysvinit to systemd-sysv|sysvinit-core. In stretch, it
should now be possible again: init is non-Essential, and has dropped
from Priority: required to Priority: important.


--- End Message ---

Reply to: