From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Fam Zheng" <fam@euphon.net>, "Thomas Huth" <thuth@redhat.com>,
"Ed Maste" <emaste@freebsd.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Li-Wen Hsu" <lwhsu@freebsd.org>
Subject: Re: [PULL 0/1] Require Python >= 3.5 to build QEMU
Date: Tue, 5 Nov 2019 16:57:48 -0300 [thread overview]
Message-ID: <20191105195748.GG3812@habkost.net> (raw)
In-Reply-To: <CAFEAcA-F0iB2vzi3Z0J9FPAt6JpuMh+V0wsfXWLuAGX5_d69xw@mail.gmail.com>
On Thu, Oct 31, 2019 at 08:12:01AM +0000, Peter Maydell wrote:
> On Fri, 25 Oct 2019 at 21:34, Eduardo Habkost <ehabkost@redhat.com> wrote:
> >
> > The following changes since commit 03bf012e523ecdf047ac56b2057950247256064d:
> >
> > Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging (2019-10-25 14:59:53 +0100)
> >
> > are available in the Git repository at:
> >
> > git://github.com/ehabkost/qemu.git tags/python-next-pull-request
> >
> > for you to fetch changes up to d24e417866f85229de1b75bc5c0a1d942451a842:
> >
> > configure: Require Python >= 3.5 (2019-10-25 16:34:57 -0300)
> >
> > ----------------------------------------------------------------
> > Require Python >= 3.5 to build QEMU
> >
> > ----------------------------------------------------------------
>
> I can't apply this until we've fixed the tests/vm netbsd setup to
> not use Python 2.
Fixing tests/vm/netbsd is being tricky. It looks like the
configure patch will have to wait until after QEMU 4.2.0. :(
>
> Have you tried a test run with Travis/etc/etc to check that none of
> those CI configs need updating to have python3 available ?
I have tested this pull request on Shippable, and I will take a
look at Travis. I'd appreciate help from the CI system
maintainers (CCed) for the rest, as I don't have accounts in all
our CI systems.
Do we expect maintainers to test their pull requests in all CI
systems listed at the QEMU wiki[1]? Do we have an official list
of CI systems that you consider to be pull request blockers?
[1] https://wiki.qemu.org/Testing#Continuous_Integration
--
Eduardo
next prev parent reply other threads:[~2019-11-05 19:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 20:34 [PULL 0/1] Require Python >= 3.5 to build QEMU Eduardo Habkost
2019-10-25 20:34 ` [PULL 1/1] configure: Require Python >= 3.5 Eduardo Habkost
2019-10-31 8:12 ` [PULL 0/1] Require Python >= 3.5 to build QEMU Peter Maydell
2019-11-05 19:57 ` Eduardo Habkost [this message]
2019-11-05 20:10 ` Peter Maydell
2019-11-05 20:25 ` Alex Bennée
2019-11-05 20:36 ` Eduardo Habkost
2019-11-06 10:36 ` Daniel P. Berrangé
2019-11-06 11:17 ` Peter Maydell
2019-11-06 11:48 ` Alex Bennée
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=20191105195748.GG3812@habkost.net \
--to=ehabkost@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=emaste@freebsd.org \
--cc=fam@euphon.net \
--cc=lwhsu@freebsd.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.