On Tue, Jun 05, 2018 at 06:50:53PM +0200, Andrea Bolognani wrote:
On Tue, 2018-06-05 at 14:38 +0200, Michal Privoznik wrote:
On 06/05/2018 02:04 PM, Daniel P. Berrangé wrote:
On Tue, Jun 05, 2018 at 01:55:54PM +0200, Michal Privoznik wrote:
We are building with GnuTLS everywhere because GnuTLS is widely available. Also, it is desirable to prefer cryptographically strong PRNG over "/dev/urandom" which is just a fallback.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com> --- configure.ac | 2 -- m4/virt-gnutls.m4 | 4 ---- 2 files changed, 6 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Thanks, I've pushed these.
Well, this is awkward:
https://ci.centos.org/view/libvirt/job/libvirt-master-build-website/124/syst...
We don't actually build libvirt on CentOS 6 anymore, just the documentation and release archives, ie. what's necessary to keep libvirt.org (which is still on that OS) running; still, after this patch the configure step will very understandably fail, and I can't imagine things going over much better on the actual live instance of the website: no nightlies[1] today, I'm afraid!
I'm likewise afraid I don't have any bright ideas on how to solve this, so any input on the matter will be very much appreciated.
We can't use docker on centos6 either and believe it or not the host doesn't have hardware virt either. I could possibly setup libvirt lxc to run the jobs though. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|