[Pkg-libvirt-maintainers] Bug#538799: libvirt-bin: remote connections fail with netcat-traditional

[Robert Kawecki]

Hi,
I ran into this problem today and would like to suggest a partial
resolution.
Upon installation, libvirt-bin should check whether netcat-openbsd is
the currently active alternative for netcat. In case it is not, a
warning should be displayed, informing the system administrator that
they will not be able to use remote SSH connections to the current
system unless they configure the client appropriately or update the
alternatives system accordingly.
Of course, it has the drawback of working only when libvirt-bin is
installed after an offending netcat which might have overridden the
settings, but it will at least catch some of the cases, instead of
looking like a bug in virt-manager or whatever frontend the client uses.
I'm convinced that this is the most sane solution at the moment.
Also, a trigger to notify libvirt-bin of installation of any netcat
could be utilized to warn the admin of a possible problem.