Your message dated Tue, 12 Jan 2016 11:22:29 +0100
with message-id <20160112102227.ga12...@sh73.dev.logilab.fr>
and subject line Re: Bug#810785: ifupdown breaks debootstrap of Debian
has caused the Debian Bug report #810785,
regarding ifupdown breaks debootstrap of Debian
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 ow...@bugs.debian.org
immediately.)
--
810785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ifupdown
Version: 0.8.5
Severity: critical
Justification: breaks the whole system
User: de...@kali.org
debootstrap of stretch currently fails due to ifupdown:
$ sudo debootstrap --components=main,contrib,non-free stretch stretch
http://ftp.debian.org/debian
[...]
I: Unpacking libxapian22v5...
W: Failure while installing base packages. This will be re-attempted up
to five times.
W: See /home/rhertzog/tmp/stretch/debootstrap/debootstrap.log for details
(possibly the package /var/cache/apt/archives/ifupdown_0.8.6_amd64.deb is
at fault)
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)
The problem is that stretch still has systemd 228-2 and 228-4 is unlikely
to migrate quickly since it just got updated and seems to have a new RC bug.
I'm not sure what's the best way forward... possibly upload something to
testing-proposed-updates to drop that breaks temporarily until the package
migrates (and ensure 0.8.7 does not migrate before systemd).
Or force migrate the new systemd despite the age and the bug...
Ccing release team and systemd maintainers to have their opinion.
-- System Information:
Debian Release: stretch/sid
APT prefers squeeze-lts
APT policy: (500, 'squeeze-lts'), (500, 'oldoldstable'), (500, 'unstable'),
(500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages ifupdown depends on:
ii adduser 3.113+nmu3
ii init-system-helpers 1.24
ii iproute2 4.3.0-1
ii libc6 2.21-6
ii lsb-base 9.20150917
Versions of packages ifupdown recommends:
ii isc-dhcp-client [dhcp-client] 4.3.3-5
Versions of packages ifupdown suggests:
ii ppp 2.4.7-1+1
pn rdnssd <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, Jan 12, 2016 at 11:15:25 +0100, Martin Pitt wrote:
> Hello Raphaël,
>
> Weird, why did britney migrate ifupdown to testing despite being
> uninstallable? This sounds like a major britney bug -- ifupdown and
> systemd were clearly meant to go in together, as the Breaks: indicate.
>
ifupdown is not uninstallable (systemd is not essential), and britney
doesn't check co-installability ATM.
Anyway, this isn't a bug in ifupdown, I don't think there's anything to
do other than waiting for systemd to migrate, which it will do on its
own. Closing.
Cheers,
Julien
--
Julien Cristau <julien.cris...@logilab.fr>
Logilab http://www.logilab.fr/
Informatique scientifique & gestion de connaissances
--- End Message ---
