From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: update few python3 packages
Date: Sun, 13 Feb 2022 14:22:24 +0100 [thread overview]
Message-ID: <20220213132224.mS8nlIthv6vhckHlzmx9JlKe0CwlEnIvz0GeWgMvIjo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35376@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/pull/35376#issuecomment-1038113461
Comment:
Let me clarify: the upstream1.patch set has already been merged into master; the other patch just removes `loop=loop`, partially fixing the zeroMQ issue (at least in some cases, see issues 241 and 245 there).
Together, they make console at least usable, while now it is broken on Void, so I don't see any point in blocking the updates of other packages due to it. If you prefer I can remove the second patch, and leave it broken for the moment.
next prev parent reply other threads:[~2022-02-13 13:22 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 13:22 [PR PATCH] " dkwo
2022-02-03 13:23 ` ahesford
2022-02-03 13:30 ` dkwo
2022-02-03 13:32 ` [PR PATCH] [Updated] " dkwo
2022-02-03 13:46 ` dkwo
2022-02-03 13:47 ` dkwo
2022-02-03 13:58 ` [PR PATCH] [Updated] " dkwo
2022-02-03 14:07 ` dkwo
2022-02-03 14:30 ` ahesford
2022-02-03 15:27 ` dkwo
2022-02-03 15:27 ` [PR PATCH] [Updated] " dkwo
2022-02-13 10:35 ` dkwo
2022-02-13 10:46 ` dkwo
2022-02-13 12:41 ` ahesford
2022-02-13 13:22 ` dkwo [this message]
2022-02-13 18:49 ` ahesford
2022-02-14 9:58 ` [PR PATCH] [Updated] " dkwo
2022-02-14 10:00 ` dkwo
2022-02-14 10:08 ` dkwo
2022-02-21 9:42 ` [PR PATCH] [Updated] " dkwo
2022-02-28 12:49 ` dkwo
2022-03-11 17:38 ` dkwo
2022-03-11 17:41 ` dkwo
2022-03-14 19:24 ` [PR PATCH] [Updated] " dkwo
2022-03-14 20:22 ` [PR REVIEW] " paper42
2022-03-14 20:22 ` paper42
2022-03-14 20:22 ` paper42
2022-03-14 20:22 ` paper42
2022-03-14 20:23 ` paper42
2022-03-15 13:40 ` dkwo
2022-03-15 13:41 ` dkwo
2022-03-15 13:45 ` dkwo
2022-03-15 13:46 ` dkwo
2022-03-15 13:48 ` [PR PATCH] [Updated] " dkwo
2022-03-20 22:51 ` [PR REVIEW] " paper42
2022-03-20 22:51 ` paper42
2022-03-20 22:52 ` paper42
2022-03-21 7:46 ` dkwo
2022-03-21 7:51 ` dkwo
2022-03-21 7:54 ` dkwo
2022-03-21 8:07 ` dkwo
2022-03-21 8:11 ` dkwo
2022-03-21 8:19 ` dkwo
2022-03-21 8:23 ` [PR PATCH] [Updated] " dkwo
2022-03-21 8:23 ` dkwo
2022-03-21 10:10 ` [PR PATCH] [Updated] " dkwo
2022-04-11 17:08 ` dkwo
2022-04-11 17:09 ` dkwo
2022-04-23 19:14 ` [PR PATCH] [Updated] " dkwo
2022-06-11 14:11 ` dkwo
2022-08-22 16:17 ` dkwo
2022-08-22 16:50 ` dkwo
2022-11-21 2:11 ` github-actions
2022-11-21 15:50 ` dkwo
2022-11-21 17:08 ` ahesford
2022-11-25 21:59 ` dkwo
2022-11-25 22:28 ` ahesford
2022-12-05 22:55 ` [PR PATCH] [Updated] " dkwo
2022-12-05 22:57 ` dkwo
2022-12-05 23:01 ` [PR PATCH] [Updated] " dkwo
2022-12-08 16:46 ` dkwo
2022-12-08 16:47 ` dkwo
2022-12-12 13:24 ` [PR REVIEW] " ahesford
2022-12-12 13:24 ` ahesford
2022-12-12 18:37 ` ahesford
2022-12-12 18:42 ` ahesford
2022-12-12 19:11 ` [PR PATCH] [Updated] " dkwo
2022-12-12 19:12 ` [PR REVIEW] " dkwo
2022-12-12 19:12 ` dkwo
2022-12-12 19:13 ` dkwo
2022-12-12 19:44 ` [PR PATCH] [Closed]: " ahesford
2022-12-12 23:19 ` tornaria
2022-12-12 23:25 ` tornaria
2022-12-12 23:25 ` dkwo
2022-12-12 23:26 ` dkwo
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=20220213132224.mS8nlIthv6vhckHlzmx9JlKe0CwlEnIvz0GeWgMvIjo@z \
--to=dkwo@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).