On Tue, Mar 20, 2018 at 01:46:43PM +0100, Andrea Bolognani wrote: > On Tue, 2018-03-20 at 12:40 +0000, Daniel P. Berrangé wrote: > > On Tue, Mar 20, 2018 at 01:38:50PM +0100, Andrea Bolognani wrote: > > > On Tue, 2018-03-20 at 11:12 +0000, Daniel P. Berrangé wrote: > > > > While current RHEL are py2, future RHEL should be expected to > > > > use Python 3 too > > > > > [...] > > > I think we should cross that bridge when we come to it, eg. when a > > > RHEL release that uses Python 3 as the default Python is released. > > > > > > We're probably going to have to go through the spec file and > > > reassess most package relationships at that point anyway. > > > > We've already crossed the bridge & done this work > > > > commit b2ab38bfdc765bbcb56b89b55dfee6b406fc8c29 > > Author: Jiri Denemark <jdenemar@xxxxxxxxxx> > > Date: Fri Feb 9 14:08:45 2018 +0100 > > > > spec: Prepare for future RHEL > > Fair enough, I must have missed that. > > Do you want me to post a v2 of the patch, or can I adjust the %if > condition as suggested (along with the comment) and add your R-b? Sure, feel free to push make the suggested change & have my R-b 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@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
