Package: libvirt-daemon-system Version: 3.0.0-4 Followup-For: Bug #538799 Dear Maintainer, the problem is still there and debian seems to default to nc6, which also isn't compatible. What about changing the netcat path both on server and client side to something like /usr/lib/libvirt/nc.libvirt and symlinking this to nc.openbsd, which is a dependency on the daemon package, while the client doesn't need to care about the server side implementation but can expect a working binary in /usr/lib/libvirt/nc.libvirt?
with kind regards, Alexander Schier -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (900, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libvirt-daemon-system depends on: ii adduser 3.115 ii debconf [debconf-2.0] 1.5.61 ii gettext-base 0.19.8.1-2 ii init-system-helpers 1.48 ii iptables 1.6.0+snapshot20161117-6 ii libapparmor1 2.11.0-3 ii libaudit1 1:2.6.7-2 ii libblkid1 2.29.2-1 ii libc6 2.24-11+deb9u1 ii libcap-ng0 0.7.7-3+b1 ii libdbus-1-3 1.10.18-1 ii libdevmapper1.02.1 2:1.02.137-2 ii libnl-3-200 3.2.27-2 ii libnl-route-3-200 3.2.27-2 ii libnuma1 2.0.11-2.1 ii librados2 10.2.5-7.2 ii librbd1 10.2.5-7.2 ii libselinux1 2.6-3+b1 ii libvirt-clients 3.0.0-4 ii libvirt-daemon 3.0.0-4 ii libvirt0 3.0.0-4 ii libxml2 2.9.4+dfsg1-2.2+deb9u1 ii libyajl2 2.1.0-2+b3 ii logrotate 3.11.0-0.1 ii lsb-base 9.20161125 ii policykit-1 0.105-18 Versions of packages libvirt-daemon-system recommends: ii bridge-utils 1.5-13 ii dmidecode 3.0-4 ii dnsmasq-base 2.76-5+b1 ii ebtables 2.0.10.4-3.5+b1 ii iproute2 4.9.0-1 ii parted 3.2-17 Versions of packages libvirt-daemon-system suggests: pn apparmor <none> pn auditd <none> pn nfs-common <none> pn pm-utils <none> pn radvd <none> ii systemd 232-25+deb9u1 pn systemtap <none> pn zfsutils <none> -- debconf information excluded
