Re: [Xen-devel] Python version requirements vs qemu-upstream

[Anthony PERARD <anthony.perard@xxxxxxxxxx>]

On Wed, Jan 15, 2014 at 10:48:09AM +0000, Ian Campbell wrote:
> On Wed, 2014-01-15 at 10:21 +0000, Jan Beulich wrote:
> > >>> On 15.01.14 at 11:03, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> > > On Wed, 2014-01-15 at 09:27 +0000, Jan Beulich wrote:
> > >> According to our own documentation, even Python 2.3 is supported
> > >> for building,
> > > 
> > > It might be time to consider reving that.
> > 
> > Post 4.4 perhaps, but I don't think now is the right time to consider
> > anything like that. IMO we ought to fix the build instead.
> 
> I think revving the minimum requirement to Python 2.4 would be a
> perfectly acceptable thing to do at this stage in the release, it's
> nothing more than a change to the README.
> 
> From the rest of your mail I agree that going further than that and
> requiring 2.5+ would be wrong for 4.4.
> 
> > > Current state of some distros:
> > > 
> > > Debian Squeeze (oldstable): 2.6
> > > Debian Wheezy (stable): 2.7
> > > RHEL 5.9: 2.4
> > > RHEL 4.8: 2.3
> > > SLES 11SP3: 2.6
> > > SLES 10SP4: 2.4
> > > 
> > > So by bumping to a minimum version of 2.4 we would be dropping support
> > > for RHEL4 dom0 userspace -- Personally I think that would be acceptable,
> > > it's now RHEL's old-old-stable (unless RHEL7 happened while I wasn't
> > > paying attention, which is possible).
> > > 
> > > Bumping further than 2.4 would mean dropping RHEL5 and SLES10, neither
> > > of which seem desirable to drop unnecessarily. (If there were known
> > > issues with 2.4 then I would be inclined to re-evaluate that though)
> > 
> > As said - I encountered the issue here with 2.4 (on SLE10).
> 
> Sorry, I misunderstood and thought this was an issue with 2.3
> somewhere. 
> 
> Given that it is 2.4 and Qemu's configure script explicitly says that
> 2.4 is what they want I think it would be worth sending the fix to qemu
> upstream -- at worst they say no and bump their requirement (at which
> point we'd have to have a think about what to do).

It's look like the fix is already upstream. Here in the 1.6 stable
branch:
http://git.qemu.org/?p=qemu.git;a=commit;h=0ca1774b619dc53db5eb1419d12efcd433f9fe3d

-- 
Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel