Bug#810785: ifupdown breaks debootstrap of Debian

[Julian Andres Klode]

On Tue, Jan 12, 2016 at 11:01:11AM +0100, Guus Sliepen wrote:
> severity 810785 serious
> thanks
> 
> On Tue, Jan 12, 2016 at 10:23:49AM +0100, Raphaël Hertzog wrote:
> 
> > Severity: critical
> > Justification: breaks the whole system
> 
> While it is very annoying, it doesn't *break* the whole system. Also, it
> is only a problem when debootstrapping testing, so it still works fine
> in a lot of other situations.
> 
> But the problem is in any case not in the ifupdown package itself;
> ifupdown has correct Breaks: headers. The package was moved to testing
> because it actually is installable (although on a normal testing system,
> trying to upgrade ifupdown to the latest version will cause sysvinit to
> be installed and systemd removed). So I rather believe the problem is
> that debootstrap doesn't handle the situation correctly:
> 
> > debootstrap.log contains this:
> > 
> > dpkg: regarding .../ifupdown_0.8.6_amd64.deb containing ifupdown:
> >  ifupdown breaks systemd (<< 228-3~)
> >   systemd (version 228-2+b1) is present and triggered.
> > 
> > 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.

-- 
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.