qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
	Eric Blake <eblake@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Cleber Rosa <crosa@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] configure: Require Python 2.7 or newer
Date: Fri, 8 Jun 2018 15:40:23 +0100	[thread overview]
Message-ID: <20180608144023.GS18233@redhat.com> (raw)
In-Reply-To: <24e7a171-33b6-e9ca-9d9c-d61a7a2c5047@amsat.org>

On Fri, Jun 08, 2018 at 11:37:36AM -0300, Philippe Mathieu-Daudé wrote:
> Cc'ing Eric
> 
> On 06/08/2018 11:30 AM, Eduardo Habkost wrote:
> > All of the supported build platforms documented in qemu-doc.texi
> > should already support Python 2.7.
> 
> https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg05173.html
> 
>   On 08/25/2017 11:40 AM, Peter Maydell wrote:
>   > Our choices about our dependencies are generally driven by "what
>   > are the versions available on the oldest distros which we wish
>   > to support building QEMU on", which typically is whatever the
>   > long-term-support versions of Ubuntu, SUSE, Redhat, etc are.
>   >
>   > Has somebody checked what that means for our Python version
>   > requirements?
> 
>   At least this one:
> 
>   RHEL/CentOS 6: Python-2.6.6

RHEL6 is no longer a target we care about and is being explicitly
broken as a result of the min glib bump:

  https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg02104.html

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

  reply	other threads:[~2018-06-08 14:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-08 14:30 [Qemu-devel] [PATCH] configure: Require Python 2.7 or newer Eduardo Habkost
2018-06-08 14:37 ` Philippe Mathieu-Daudé
2018-06-08 14:40   ` Daniel P. Berrangé [this message]
2018-06-08 14:59     ` Philippe Mathieu-Daudé
2018-06-08 14:37 ` Daniel P. Berrangé
2018-06-08 14:55   ` Eduardo Habkost
2018-06-08 15:07     ` Daniel P. Berrangé
2018-06-08 15:03 ` Eduardo Habkost
2018-06-08 15:07 ` Daniel P. Berrangé
2018-06-08 16:14 ` Cleber Rosa
2018-06-08 19:19 ` John Snow
2018-06-11 13:52 ` Stefan Hajnoczi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180608144023.GS18233@redhat.com \
    --to=berrange@redhat.com \
    --cc=crosa@redhat.com \
    --cc=eblake@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).