FS#30748 - [libvirt] [virt-manager] /usr/bin/nc vs. /usr/bin/nc.openbsd
Attached to Project:
Community Packages
Opened by jstjohn (jstjohn) - Wednesday, 18 July 2012, 23:14 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 19 November 2012, 15:10 GMT
Opened by jstjohn (jstjohn) - Wednesday, 18 July 2012, 23:14 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 19 November 2012, 15:10 GMT
|
Details
Description: I think that something needs to be done
regarding the use of /usr/bin/nc vs. /usr/bin/nc.openbsd.
When I try to connect to a remote RHEL server using
qemu+ssh, I get a 'file not found' error and cannot connect
because virt-manager is looking for /usr/bin/nc.openbsd
which doesn't exist on the remote RHEL system. The comments
for
I propose that the libvirt and virt-manager package maintainers for Arch, RHEL, CentOS, Fedora, Debian, etc. come into agreement about what path should be used, and that patched packages meeting an agreed-upon standard get pushed out to the official repos for all distros. I'm guessing that this may not be the easiest thing to get done, and I would guess that a distro like RHEL has inflexible standards that it must follow, which means everyone else may need to replicate how they package these. Perhaps a better solution would be for *all* distros to standardize on using /usr/bin/nc OR for *all* distros to ship a symlink from /usr/bin/nc.openbsd to /usr/bin/nc. I much prefer the former. Additional info: * package versions: libvirt-0.9.13-2 and virt-manager-0.9.3-1 from [community] * This is related to Steps to reproduce: * Try connecting via qemu+ssh to a remote RHEL server from an up-to-date Arch install. |
This task depends upon
If not adding a conflict with it and using nc as executable should work.