Package: ifupdown2
Version: 3.0.0-1.1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Istalling and using ifupdown2 when not using systemd, the /ru/network etc.
directories isn't setup and ifup fails with errors relating to the fact it
can't check for a similar process running concuretly
* What exactly did you do (or not do) that was effective (or
ineffective)?
The solution is to download
https://github.com/CumulusNetworks/ifupdown2/blob/master/etc/init.d/networking
into the /etc/init.d directory and running update-rc.d
* What was the outcome of this action?A
That action fixed the issue
* What outcome did you expect instead?
The file included by default by the packaging system
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 12.9
merged-usr: no
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-33-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_ZA:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages ifupdown2 depends on:
ii iproute2 6.13.0-1~bpo12+1
ii python3 3.11.2-1+b1
ifupdown2 recommends no packages.
Versions of packages ifupdown2 suggests:
pn bridge-utils <none>
ii ethtool 1:6.1-1
ii isc-dhcp-client 4.4.3-P1-2
pn python3-gvgen <none>
pn python3-mako <none>
-- Configuration Files:
/etc/network/ifupdown2/addons.conf changed [not included]
/etc/network/ifupdown2/ifupdown2.conf changed [not included]
-- no debconf information