Re: [PULL 0/1] Require Python >= 3.5 to build QEMU

2019-11-06 Thread Alex Bennée
Peter Maydell writes: > On Wed, 6 Nov 2019 at 10:36, Daniel P. Berrangé wrote: >> At what point do we declare that NetBSD CI is broken and is no longer >> considered a supported platform from POV of blocking the merging of >> PULL requests ? It has been preventing the dropping of python2 for

Re: [PULL 0/1] Require Python >= 3.5 to build QEMU

2019-11-06 Thread Peter Maydell
On Wed, 6 Nov 2019 at 10:36, Daniel P. Berrangé wrote: > At what point do we declare that NetBSD CI is broken and is no longer > considered a supported platform from POV of blocking the merging of > PULL requests ? It has been preventing the dropping of python2 for > quite a while now. It isn't

Re: [PULL 0/1] Require Python >= 3.5 to build QEMU

2019-11-06 Thread Daniel P . Berrangé
On Tue, Nov 05, 2019 at 08:25:03PM +, Alex Bennée wrote: > > Eduardo Habkost writes: > > > On Thu, Oct 31, 2019 at 08:12:01AM +, Peter Maydell wrote: > >> On Fri, 25 Oct 2019 at 21:34, Eduardo Habkost wrote: > >> > > >> > The following changes since commit > >> >

Re: [PULL 0/1] Require Python >= 3.5 to build QEMU

2019-11-05 Thread Eduardo Habkost
On Tue, Nov 05, 2019 at 08:25:03PM +, Alex Bennée wrote: > > Eduardo Habkost writes: > > > On Thu, Oct 31, 2019 at 08:12:01AM +, Peter Maydell wrote: > >> On Fri, 25 Oct 2019 at 21:34, Eduardo Habkost wrote: > >> > > >> > The following changes since commit > >> >

Re: [PULL 0/1] Require Python >= 3.5 to build QEMU

2019-11-05 Thread Alex Bennée
Eduardo Habkost writes: > On Thu, Oct 31, 2019 at 08:12:01AM +, Peter Maydell wrote: >> On Fri, 25 Oct 2019 at 21:34, Eduardo Habkost wrote: >> > >> > The following changes since commit >> > 03bf012e523ecdf047ac56b2057950247256064d: >> > >> > Merge remote-tracking branch

Re: [PULL 0/1] Require Python >= 3.5 to build QEMU

2019-11-05 Thread Peter Maydell
On Tue, 5 Nov 2019 at 19:57, Eduardo Habkost wrote: > Fixing tests/vm/netbsd is being tricky. It looks like the > configure patch will have to wait until after QEMU 4.2.0. :( I think that makes sense at this point in the release cycle, yes. > > Have you tried a test run with Travis/etc/etc to

Re: [PULL 0/1] Require Python >= 3.5 to build QEMU

2019-11-05 Thread Eduardo Habkost
On Thu, Oct 31, 2019 at 08:12:01AM +, Peter Maydell wrote: > On Fri, 25 Oct 2019 at 21:34, Eduardo Habkost wrote: > > > > The following changes since commit 03bf012e523ecdf047ac56b2057950247256064d: > > > > Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into > > staging

Re: [PULL 0/1] Require Python >= 3.5 to build QEMU

2019-10-31 Thread Peter Maydell
On Fri, 25 Oct 2019 at 21:34, Eduardo Habkost 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: > >

[PULL 0/1] Require Python >= 3.5 to build QEMU

2019-10-25 Thread Eduardo Habkost
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