Re: [libvirt] [jenkins-ci PATCH 0/3] Drop CentOS 6, which makes some nice cleanups possible
On Fri, 2018-04-06 at 14:43 +0100, Daniel P. Berrangé wrote: > > > It just occurred to me that libvirt.org is running on CentOS 6, and we > > > rely on being able to run configure, make & make dist there, so that > > > we can do things like publish the website, create nightly snapshots, > > > etc. So even if we don't support /running/ libvirt on CentOS 6, we'll > > > need to make sure we can at least do minimal builds - doesn't need > > > hypervisors enabled, as long as make dist still works. So I think it > > > is probably worth keeping at least the core libvirt build on CentOS 6 > > > CI, even if we turn off the sub-project like language bindings. > > > > Alternatively, we can upgrade libvirt.org to centos 7. > > Not something I would do myself - would have to be DV who decides to > do that. Seems to me like that's the way to go. I don't think we want to have any ifs or buts in our support matrix: it should be very clear-cut in order to preserve our sanity, and also to ensure people looking at the project from outside don't get confused by mixed signals. If DV doesn't have time to take care of upgrading but also doesn't have a problem with the idea, I wouldn't mind looking into it myself. -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [jenkins-ci PATCH 0/3] Drop CentOS 6, which makes some nice cleanups possible
On Fri, Apr 06, 2018 at 03:38:34PM +0200, Michal Privoznik wrote: > On 04/06/2018 03:20 PM, Daniel P. Berrangé wrote: > > On Fri, Apr 06, 2018 at 01:58:07PM +0200, Andrea Bolognani wrote: > >> This applies on top of > >> > >> https://www.redhat.com/archives/libvir-list/2018-April/msg00410.html > >> > >> and, of course, should only be pushed after > >> > >> https://www.redhat.com/archives/libvir-list/2018-April/msg00326.html > >> > >> or a follow-up version has been pushed. > > > > It just occurred to me that libvirt.org is running on CentOS 6, and we > > rely on being able to run configure, make & make dist there, so that > > we can do things like publish the website, create nightly snapshots, > > etc. So even if we don't support /running/ libvirt on CentOS 6, we'll > > need to make sure we can at least do minimal builds - doesn't need > > hypervisors enabled, as long as make dist still works. So I think it > > is probably worth keeping at least the core libvirt build on CentOS 6 > > CI, even if we turn off the sub-project like language bindings. > > > > Alternatively, we can upgrade libvirt.org to centos 7. Not something I would do myself - would have to be DV who decides to do that. 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 :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [jenkins-ci PATCH 0/3] Drop CentOS 6, which makes some nice cleanups possible
On 04/06/2018 03:20 PM, Daniel P. Berrangé wrote: > On Fri, Apr 06, 2018 at 01:58:07PM +0200, Andrea Bolognani wrote: >> This applies on top of >> >> https://www.redhat.com/archives/libvir-list/2018-April/msg00410.html >> >> and, of course, should only be pushed after >> >> https://www.redhat.com/archives/libvir-list/2018-April/msg00326.html >> >> or a follow-up version has been pushed. > > It just occurred to me that libvirt.org is running on CentOS 6, and we > rely on being able to run configure, make & make dist there, so that > we can do things like publish the website, create nightly snapshots, > etc. So even if we don't support /running/ libvirt on CentOS 6, we'll > need to make sure we can at least do minimal builds - doesn't need > hypervisors enabled, as long as make dist still works. So I think it > is probably worth keeping at least the core libvirt build on CentOS 6 > CI, even if we turn off the sub-project like language bindings. > Alternatively, we can upgrade libvirt.org to centos 7. Michal -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [jenkins-ci PATCH 0/3] Drop CentOS 6, which makes some nice cleanups possible
On Fri, Apr 06, 2018 at 01:58:07PM +0200, Andrea Bolognani wrote: > This applies on top of > > https://www.redhat.com/archives/libvir-list/2018-April/msg00410.html > > and, of course, should only be pushed after > > https://www.redhat.com/archives/libvir-list/2018-April/msg00326.html > > or a follow-up version has been pushed. It just occurred to me that libvirt.org is running on CentOS 6, and we rely on being able to run configure, make & make dist there, so that we can do things like publish the website, create nightly snapshots, etc. So even if we don't support /running/ libvirt on CentOS 6, we'll need to make sure we can at least do minimal builds - doesn't need hypervisors enabled, as long as make dist still works. So I think it is probably worth keeping at least the core libvirt build on CentOS 6 CI, even if we turn off the sub-project like language bindings. 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 :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
