On Tue, Jan 12, 2016 at 12:16:29PM +0100, Guus Sliepen wrote: > On Tue, Jan 12, 2016 at 11:24:00AM +0100, Julian Andres Klode wrote: > > > > > dpkg: error processing archive > > > > /var/cache/apt/archives/ifupdown_0.8.6_amd64.deb (--unpack): > > > > installing ifupdown would break systemd, and > > > > deconfiguration is not permitted (--auto-deconfigure might help) > > > > > > Maybe debootstrap should ensure dpkg is called with --auto-deconfigure? > > > > So, you want an unconfigured init system or other unconfigured packages in > > the base system? Really? > > > > That does not make any sense at all. > > No; what happens is that apt knows that it can upgrade two packages at > the same time, where one of them Breaks: the old version of the other > package. But dpkg processes packages individually, and when the old > version of the other package is still installed, and dpkg tries to > upgrade the first package, it notices the Breaks. It can temporarily > deconfigure the other package, continue upgrading the first, then > upgrading the other package and (re)configuring it.
Yes it can. When *upgrading*. We are *NOT* upgrading, but bootstrapping a new system here. > > This is actually what happens when you are just doing an apt-get > dist-upgrade on a testing system. The problem with debootstrap is that > this --auto-deconfigure option is somehow not passed to dpkg. We are talking about bootstrapping, not upgrading. Automatic deconfiguration of packages is entirely irrelevant here. Please think first. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to (`inline'). Thank you.