Package: ifupdown2
Version: 1.2.2-1
Severity: critical
Tags: patch
Justification: breaks the whole system

Hi Julien,

(for others who might also stumble accros this problem I open a bug here
 besides the PR on github)

we noticed that ifupdown2 fails to start and therefore fails to
configure any interfaces when /var/tmp is not present when starting
networking.service. This may happen when /var is on a separate file
system.

PR 87 addresses this issue with a dependency in the service file on the
/var/tmp filesystem. See https://github.com/CumulusNetworks/ifupdown2/pull/87
for a patch :-)

Best
Max

-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ifupdown2 depends on:
ii  iproute2            4.19.0-2
ii  python              2.7.15-3
ii  python-argcomplete  1.8.1-1
ii  python-ipaddr       2.2.0-1

ifupdown2 recommends no packages.

Versions of packages ifupdown2 suggests:
pn  bridge-utils          <none>
ii  ethtool               1:4.19-1
ii  isc-dhcp-client       4.4.1-2
pn  python-gvgen          <none>
pn  python-mako           <none>
pn  python-pkg-resources  <none>

-- no debconf information

Reply via email to