Your message dated Fri, 30 Oct 2026 10:23:00 +0300
with message-id <[email protected]>
and subject line Re: Bug#1146845: /etc/qemu-ifup has an undeclared dependency
on net-tools
has caused the Debian Bug report #1146845,
regarding /etc/qemu-ifup has an undeclared dependency on net-tools
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 [email protected]
immediately.)
--
1146845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1146845
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-system-common
Version: 1:10.0.11+ds-0+deb13u1
qemu-system-common's /etc/qemu-ifup depends on ifconfig from net-tools,
but this dependency is not declared anywhere.
The effect is that VM networking can break (without any diagnostice that
I ever found) if net-tools is not installed. This is a reasonable
configuration since it is largely supplanted by iproute2.
Either the package should declare the dependency, or qemu-ifup should be
rewritten to use ip(8).
$ dpkg -L qemu-system-common|xargs grep ifconfig 2>/dev/null
/etc/qemu-ifup: ifconfig "$1" 0.0.0.0 up
$ sha256sum /etc/qemu-ifup
d4fd5cf3e6c293bec0ccbffd73b10d960d62ad65fa5e5cbd5fbad0a9661d40c8
/etc/qemu-ifup
$ dpkg -s qemu-system-common | grep net-tools
$ dpkg -S /usr/sbin/ifconfig
net-tools: /usr/sbin/ifconfig
ttfn/rjk
--- End Message ---
--- Begin Message ---
On 9/7/26 10:38, Richard Kettlewell wrote:
On 06/09/2026 10:59, Richard Kettlewell wrote:
Package: qemu-system-common
Version: 1:10.0.11+ds-0+deb13u1
qemu-system-common's /etc/qemu-ifup depends on ifconfig from net-tools, but
this dependency is not declared anywhere.
I think this is wrong, in fact. Although installing net-tools got my VM networking working again, it has now broken again. So I think there is some
other issue.
net-tools is entirely optional. Actually this script might be adjusted these
days.
Long time ago main network configuration was net-tools (ifconfig, route, etc).
Later I modified qemu-ifup to use ether iproute2 or net-tools, whichever is
installed. Today, net-tools is entirely optional, and qemu-ifup will work
with either net-tools or iproute2, but it's difficult on a modern system not
to have iproute2, and it is preferred by this script anyway (if iproute is
installed, it will be used instead of net-tools).
So indeed, your issue is something else. I can only guess it depends on the
presence of default route at the time your VM is started.
But overall, qemu-ifup is more a (simplistic) example than a real thing. You
should use some real way to configure networking, suitable for your particular
system configuration. There's #572784 about that, filed back in 2010, and is
still open - open because no one bothered to address it, most people use
virt-manager who manages networking too.
Maybe I should drop this script entirely..
Thanks,
/mjt
--- End Message ---