From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] python-setuptools: bump to 40.0.0
Date: Mon, 20 Aug 2018 22:30:35 +0200 [thread overview]
Message-ID: <20180820223035.2e74e325@windsurf> (raw)
In-Reply-To: <20180820201142.20383-1-aduskett@gmail.com>
Hello,
On Mon, 20 Aug 2018 13:11:42 -0700, Adam Duskett wrote:
> From: Adam Duskett <aduskett@greenlots.com>
>
> With the introduction of Python 3.7.0, setuptools also needs to be updated.
> Without the update, several packages will fail to build or install with a
> ValueError: bad marshal data (unknown type code).
>
> Updating setuptools to 40.0.0 version fixes this issue.
>
> Even though 40.1.0 is out, updating to 40.0.0 is recommended as it seems like
> 40.1.0 breaks version detection on some python packages such as
> python-cryptography which will error out with a complaint that setuptools is too
> old, even though it's at 40.1.0. Using 40.0.0 fixes the issue.
>
> Fixes:
> http://autobuild.buildroot.net/results/636/636da0febe02f991095965d52cc4a8b2da644777/
> http://autobuild.buildroot.net/results/5f6/5f659130a6a32a4c43d6ed2c3b559df77ae18249/
> Signed-off-by: Adam Duskett <aduskett@greenlots.com>
> ---
> package/python-setuptools/python-setuptools.hash | 2 +-
> package/python-setuptools/python-setuptools.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-08-20 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 20:11 [Buildroot] [PATCH 1/1] python-setuptools: bump to 40.0.0 Adam Duskett
2018-08-20 20:30 ` Thomas Petazzoni [this message]
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=20180820223035.2e74e325@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