From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: python3-setuptools: update to 52.0.0.
Date: Thu, 28 Jan 2021 21:08:25 +0100 [thread overview]
Message-ID: <20210128200825.1ZoprEXYvAGHlTLlekCWtKjkROdw-QmWgoOpefXP6ts@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28261@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
There's a closed pull request on the void-packages repository
python3-setuptools: update to 52.0.0.
https://github.com/void-linux/void-packages/pull/28261
Description:
This release drops `easy_install`, which will cause hard failures when building python-module or python3-module templates that do not specify all of their setup_requires dependencies in `hostmakedepends`. This is a good thing; before, setuptools would fetch setup dependencies on its own, negatively impacting the reproducibility of package builds.
Still, I am going to run through rebuilds of some (most? all?) of the `python3-*` packages to check for build-time breakage.
prev parent reply other threads:[~2021-01-28 20:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 15:21 [PR PATCH] " ahesford
2021-01-28 13:10 ` ahesford
2021-01-28 14:20 ` ahesford
2021-01-28 14:20 ` ahesford
2021-01-28 14:20 ` ahesford
2021-01-28 14:20 ` ahesford
2021-01-28 14:44 ` ahesford
2021-01-28 14:48 ` ahesford
2021-01-28 15:43 ` ahesford
2021-01-28 15:44 ` [PR PATCH] [Updated] " ahesford
2021-01-28 16:02 ` ahesford
2021-01-28 16:03 ` ahesford
2021-01-28 16:15 ` ahesford
2021-01-28 16:15 ` [PR PATCH] [Updated] " ahesford
2021-01-28 19:36 ` ahesford
2021-01-28 19:50 ` [PR PATCH] [Updated] " ahesford
2021-01-28 19:51 ` ahesford
2021-01-28 20:03 ` [PR PATCH] [Updated] " ahesford
2021-01-28 20:08 ` ahesford [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=20210128200825.1ZoprEXYvAGHlTLlekCWtKjkROdw-QmWgoOpefXP6ts@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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).