From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/jupyter-server/
Date: Sat, 27 Jul 2024 06:49:42 +0000 (UTC) [thread overview]
Message-ID: <1722062977.86ae7c7e3425d4c22c23ce85be0db153704e1ef3.arthurzam@gentoo> (raw)
commit: 86ae7c7e3425d4c22c23ce85be0db153704e1ef3
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 27 06:49:37 2024 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Jul 27 06:49:37 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=86ae7c7e
dev-python/jupyter-server: Stabilize 2.14.2 ALLARCHES, #936710
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
dev-python/jupyter-server/jupyter-server-2.14.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/jupyter-server/jupyter-server-2.14.2.ebuild b/dev-python/jupyter-server/jupyter-server-2.14.2.ebuild
index f3b40005cedc..d9c36c44ae83 100644
--- a/dev-python/jupyter-server/jupyter-server-2.14.2.ebuild
+++ b/dev-python/jupyter-server/jupyter-server-2.14.2.ebuild
@@ -17,7 +17,7 @@ HOMEPAGE="
LICENSE="BSD"
SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~loong ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
+KEYWORDS="amd64 arm arm64 ~loong ppc ppc64 ~riscv ~s390 sparc x86"
RDEPEND="
>=dev-python/anyio-3.1.0[${PYTHON_USEDEP}]
next reply other threads:[~2024-07-27 6:49 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-27 6:49 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-27 9:44 [gentoo-commits] repo/gentoo:master commit in: dev-python/jupyter-server/ Michał Górny
2024-07-13 4:46 Michał Górny
2024-07-12 10:36 Michał Górny
2024-06-15 8:42 Michał Górny
2024-06-15 8:40 Arthur Zamarin
2024-05-31 4:22 Michał Górny
2024-04-27 8:26 Michał Górny
2024-04-27 6:53 Michał Górny
2024-04-12 3:35 Michał Górny
2024-03-22 4:38 Michał Górny
2024-03-21 20:42 Arthur Zamarin
2024-03-04 14:52 Michał Górny
2024-02-17 21:17 Sam James
2024-02-03 19:09 Sam James
2024-02-03 10:59 Sam James
2024-02-03 10:54 Sam James
2024-02-03 10:46 Sam James
2024-02-03 10:11 Arthur Zamarin
2024-02-03 8:42 Arthur Zamarin
2024-01-19 5:10 Michał Górny
2024-01-19 5:10 Michał Górny
2024-01-18 19:48 Sam James
2024-01-17 2:46 Ionen Wolkens
2024-01-16 19:22 Michał Górny
2024-01-11 15:24 Michał Górny
2024-01-10 4:42 Michał Górny
2024-01-04 4:35 Michał Górny
2023-12-30 14:32 Michał Górny
2023-12-30 14:25 Arthur Zamarin
2023-12-22 5:14 Ionen Wolkens
2023-12-15 15:50 Arthur Zamarin
2023-12-15 10:30 Arthur Zamarin
2023-12-08 19:51 Arthur Zamarin
2023-12-07 11:58 Michał Górny
2023-12-06 6:51 Michał Górny
2023-12-05 7:33 Arthur Zamarin
2023-12-02 20:28 Sam James
2023-12-02 9:38 Arthur Zamarin
2023-11-28 5:26 Michał Górny
2023-11-21 19:05 Michał Górny
2023-11-20 15:02 Michał Górny
2023-11-15 17:10 Michał Górny
2023-11-15 16:34 Arthur Zamarin
2023-11-15 14:46 Michał Górny
2023-11-14 1:38 Sam James
2023-11-14 0:38 Sam James
2023-11-13 17:41 Michał Górny
2023-10-26 13:37 Michał Górny
2023-10-25 9:05 Michał Górny
2023-10-25 7:43 Michał Górny
2023-10-25 7:03 Arthur Zamarin
2023-10-25 5:54 Michał Górny
2023-10-24 19:23 Arthur Zamarin
2023-10-24 19:15 Arthur Zamarin
2023-10-24 18:44 Michał Górny
2023-10-24 17:51 Michał Górny
2023-10-16 13:56 Michał Górny
2023-10-03 7:20 Arthur Zamarin
2023-10-03 5:38 Arthur Zamarin
2023-10-03 1:55 Sam James
2023-09-26 15:23 Arthur Zamarin
2023-09-08 18:50 Arthur Zamarin
2023-09-07 20:16 Sam James
2023-08-31 13:22 Michał Górny
2023-08-20 16:04 Michał Górny
2023-08-05 12:37 Arthur Zamarin
2023-07-24 20:04 WANG Xuerui
2023-07-24 11:01 Jakov Smolić
2023-07-21 14:50 Arthur Zamarin
2023-07-21 13:05 Arthur Zamarin
2023-07-21 11:41 Arthur Zamarin
2023-07-21 7:25 Andrew Ammerlaan
2023-04-28 15:41 Michał Górny
2023-04-28 15:24 Arthur Zamarin
2023-03-29 13:34 Andrew Ammerlaan
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=1722062977.86ae7c7e3425d4c22c23ce85be0db153704e1ef3.arthurzam@gentoo \
--to=arthurzam@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