From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/python-engineio/
Date: Fri, 29 Apr 2022 04:05:08 +0000 (UTC) [thread overview]
Message-ID: <1651205086.123277a84fe001e4bddaef5cf775c9606ac4a8eb.sam@gentoo> (raw)
commit: 123277a84fe001e4bddaef5cf775c9606ac4a8eb
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Apr 29 04:04:46 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Apr 29 04:04:46 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=123277a8
dev-python/python-engineio: restore websocket dependency
Closes: https://bugs.gentoo.org/841425
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../{python-engineio-4.3.2-r1.ebuild => python-engineio-4.3.2-r2.ebuild} | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-python/python-engineio/python-engineio-4.3.2-r1.ebuild b/dev-python/python-engineio/python-engineio-4.3.2-r2.ebuild
similarity index 97%
rename from dev-python/python-engineio/python-engineio-4.3.2-r1.ebuild
rename to dev-python/python-engineio/python-engineio-4.3.2-r2.ebuild
index a7da39134dd9..60800b43a242 100644
--- a/dev-python/python-engineio/python-engineio-4.3.2-r1.ebuild
+++ b/dev-python/python-engineio/python-engineio-4.3.2-r2.ebuild
@@ -24,6 +24,7 @@ KEYWORDS="~amd64 ~x86"
RDEPEND="
dev-python/aiohttp[${PYTHON_USEDEP}]
dev-python/requests[${PYTHON_USEDEP}]
+ dev-python/websocket-client[${PYTHON_USEDEP}]
"
# Can use eventlet, werkzeug, or gevent, but no tests for werkzeug
# eventlet doesn't yet support Python 3.10, so let's work around it
next reply other threads:[~2022-04-29 4:05 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 4:05 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-16 4:54 [gentoo-commits] repo/gentoo:master commit in: dev-python/python-engineio/ Michał Górny
2024-10-14 4:11 Michał Górny
2024-06-30 17:00 Michał Górny
2024-06-30 17:00 Michał Górny
2024-05-19 6:02 Michał Górny
2024-02-26 14:25 Michał Górny
2024-02-06 3:07 Michał Górny
2024-01-07 6:16 Michał Górny
2023-12-30 18:32 Michał Górny
2023-12-29 4:38 Michał Górny
2023-12-29 4:38 Michał Górny
2023-11-23 20:11 Michał Górny
2023-10-15 3:26 Michał Górny
2023-09-14 17:21 Arthur Zamarin
2023-09-13 15:47 Michał Górny
2023-09-04 2:48 Michał Górny
2023-08-23 19:25 Michał Górny
2023-08-21 16:45 Michał Górny
2023-08-21 16:44 Michał Górny
2023-07-24 11:33 Michał Górny
2023-07-06 3:31 Michał Górny
2023-07-06 3:31 Michał Górny
2023-04-20 3:12 Michał Górny
2023-04-09 7:44 Arthur Zamarin
2023-04-08 6:08 Michał Górny
2023-03-17 5:32 Michał Górny
2022-11-17 18:07 Michał Górny
2022-10-21 14:34 Michał Górny
2022-10-21 14:34 Michał Górny
2022-08-04 17:55 Arthur Zamarin
2022-07-05 6:07 Michał Górny
2022-05-13 15:00 Michał Górny
2022-04-28 4:05 Sam James
2022-04-24 17:47 Arthur Zamarin
2022-04-24 17:47 Arthur Zamarin
2022-01-11 18:03 Arthur Zamarin
2021-10-27 8:29 Michał Górny
2021-10-17 9:25 Michał Górny
2021-08-02 5:44 Michał Górny
2021-05-15 21:18 Michał Górny
2021-04-16 8:30 Michał Górny
2021-03-11 12:55 Sam James
2021-03-11 12:55 Sam James
2021-03-11 12:24 Michał Górny
2021-03-11 8:48 Michał Górny
2020-04-22 1:20 Zac Medico
2020-04-22 1:17 Zac Medico
2020-03-28 21:11 Michał Górny
2020-02-05 20:47 Michał Górny
2018-07-03 21:54 Zac Medico
2018-04-13 9:53 Zac Medico
2017-09-24 23:08 Zac Medico
2017-05-03 7:37 Michał Górny
2017-04-28 18:35 Zac Medico
2017-04-28 4:15 Zac Medico
2017-03-15 8:36 Zac Medico
2017-01-26 4:09 Zac Medico
2016-10-12 6:49 Zac Medico
2016-10-12 6:49 Zac Medico
2016-06-29 18:18 Patrick Lauer
2016-03-12 11:40 Patrick Lauer
2016-02-27 0:49 Zac Medico
2016-01-12 0:38 Zac Medico
2015-12-22 21:49 Zac Medico
2015-12-07 21:15 Zac Medico
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=1651205086.123277a84fe001e4bddaef5cf775c9606ac4a8eb.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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