From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-setuptools: update to 52.0.0.
Date: Thu, 28 Jan 2021 14:10:30 +0100 [thread overview]
Message-ID: <20210128131030.exCxFaUAR0u9RHHiVNRNnO8bQQJNItcjosk706IakaE@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: 1566 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/28261#issuecomment-769042088
Comment:
Of 726 packages rebuilt through the following loop:
```zsh
foreach I (srcpkgs/python3-*)
pkg=$(basename $(realpath -e $I))
[ -n "$pkg" ] || continue
{ ./xbps-src show-hostmakedepends $pkg | grep -q python3-setuptools } || continue
grep -q " $pkg\$" setuptools.dependants && continue
if ./xbps-src pkg -f -m /tmp/masterdir.x86_64 "$pkg"; then
echo "- [x] $pkg" >> setuptools.dependants
else
echo "- [ ] $pkg" >> setuptools.dependants
fi
./xbps-src -m /tmp/masterdir.x86_64 clean
end
```
The following 29 failed to rebuild:
- [ ] python3-Flask-User
- [ ] python3-PGPy
- [ ] python3-aiohttp-sse-client
- [ ] python3-alsa
- [ ] python3-audioread
- [ ] python-dateutil
- [ ] python3-ffmpeg-python
- [ ] python3-gitchangelog
- [ ] python3-guessit
- [ ] python3-humanize
- [ ] python3-irc
- [ ] python3-jaraco.classes
- [ ] python3-jaraco.collections
- [ ] python3-jaraco.functools
- [ ] python3-jaraco.text
- [ ] python3-keyring
- [ ] python3-keyrings-alt
- [ ] python3-keyutils
- [ ] python3-marisa-trie
- [ ] python3-numexpr
- [ ] python3-pluggy
- [ ] python3-portend
- [ ] python3-pylast
- [ ] python3-pysol_cards
- [ ] python3-pytest-qt
- [ ] python3-rebulk
- [ ] python3-testtools
- [ ] python3-treq
- [ ] python3-zope.security
I'm working through this list to resolve these issues. If I'm overlooking any packages that build with setuptools, please leave a comment.
next prev parent reply other threads:[~2021-01-28 13:10 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 [this message]
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 ` [PR PATCH] [Closed]: " ahesford
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=20210128131030.exCxFaUAR0u9RHHiVNRNnO8bQQJNItcjosk706IakaE@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).