Re: [PATCH] python 3.5 compatibility

["Daniel P. Berrangé" <berrange@redhat.com>]

On Tue, Dec 01, 2020 at 04:59:23PM +0100, Enrico Weigelt, metux IT consult wrote:
> On 01.12.20 07:33, Markus Armbruster wrote:
> 
> > Which has oldstable status.  Good for running the old and stable
> > software packaged by it (such as QEMU 2.8), and old (and hopefully
> > stable) software of similar vintage.
> 
> It's still heavily used out in the field, and officially supported.
> But that's just one example.
> 
> Perhaps I should add some more details on the situation: I'm using
> (specially built) qemu with ptxdist/dkit - not the distro package.
> The idea w/ ptxdist is that you just pull the trigger and it builds
> everything needed for some project. Qemu is built specifically for
> the configured target. Perhaps you've noticed I'm also doing development
> of new qemu features - something that one doesn't want to do on old
> versions.
> 
> > Have you considered upgrading to stable?
> 
> This would solve the problem just for me alone, not for others out
> there, who're working w/ the BSP. And asking everybody (especially in
> enterprise environments) to do a full release upgrade just for one
> single tool (qemu) isn't someting that works easily.
> 
> If you insist in having python3.6 a hard requirement for qemu, you're
> putting me into the situation of having to do lots of backport work
> for quite long time (until everybody really did the upgrade). :(

python3.6 is just the one problem you've currently hit. In order to keep
the burden of maintaining support for old software under control we have
a well defined set of platforms that we target. When a particular version
of a distro drops off our list, we will bump the minimum versions of any
software we depend on. In this case you've hit python3.6 so far, but we
are liable to bump other minimum versions too which will also impact
this old distro. So I'm afraid it will be a loosing battle to stay on
this old distro, while building cutting edge QEMU.

I appreciate this isn't the answer you want to hear, but we've defined
our support platform matrix to try to balance multiple competing factors
and unfortunately this means distros are going to periodically get dropped
by new QEMU as they get older.

One possible way you can mitigate this is to make use of containers for
your development and deployment. eg even tough you're using an old
Devuan, you can use docker/podman to build and deploy QEMU inside a
stable Devuan container.

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 :|