libvirt: fix control socket path

[the-eater]

If you use unix control sockets instead of TCP the path of the socket will be incorrectly build and you'll get errors like:

Failed to bind socket to 'libvirt//var/run/libvirt/-sock': No such file or directory

Included patch fixes that. is also send to upstream but idk how this ancient system of patches via mailing lists work tbh, so don't know if it came through

[the-eater]

Original build failed on The job exceeded the maximum log length, and has been terminated. and it tried to compile it's dependencies instead of installing them???

[the-eater]

package templates and repo are out of sync for x86-64 and I have 0 control over it