From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] Python3: Bump to 3.7.0
Date: Sun, 19 Aug 2018 23:10:35 +0200 [thread overview]
Message-ID: <20180819231035.4d05c225@windsurf> (raw)
In-Reply-To: <20180819155655.65466d16@windsurf>
Hello,
On Sun, 19 Aug 2018 15:56:55 +0200, Thomas Petazzoni wrote:
> On Fri, 17 Aug 2018 11:46:07 -0700, Adam Duskett wrote:
> > From: Adam Duskett <aduskett@greenlots.com>
>
> This version bump is breaking host-python-vcversioner:
>
> http://autobuild.buildroot.net/?reason=host-python-vcversioner%
>
> Could you have a look ?
It is also breaking:
- kmod
http://autobuild.buildroot.net/results/591/5914d32f7a11faf0148eceab7ed852f67357b0b5/build-end.log
- host-meson
http://autobuild.buildroot.net/results/99e/99eb91573e74a39d395212f2c470ce55d0412ec0/build-end.log
The issues don't seem to be that trivial. Unless we fix them quickly,
I'm tempted to revert the bump to 3.7.0 until those issues are
resolved, as we are going to see a lot of autobuilder failures
otherwise.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-19 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 18:46 [Buildroot] [PATCH v3 1/1] Python3: Bump to 3.7.0 Adam Duskett
2018-08-17 21:35 ` Thomas Petazzoni
2018-08-18 9:20 ` Thomas Petazzoni
2018-10-12 13:36 ` Matthew Weber
2018-08-19 13:56 ` Thomas Petazzoni
2018-08-19 21:10 ` Thomas Petazzoni [this message]
[not found] ` <SN6PR14MB21263CD05F33E8BEAAFC5A11C7330@SN6PR14MB2126.namprd14.prod.outlook.com>
[not found] ` <SN6PR14MB21260D8517E2E6E173EE7582C7330@SN6PR14MB2126.namprd14.prod.outlook.com>
2018-08-19 21:17 ` Thomas Petazzoni
2018-08-25 21:52 ` Thomas Petazzoni
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=20180819231035.4d05c225@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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