Bug#765076: general: No way to have a clean chroot for building packages

[Santiago Vila <sanvila@unex.es>]

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.

Thanks.