From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/structlog/
Date: Wed, 29 Nov 2023 04:23:28 +0000 (UTC) [thread overview]
Message-ID: <1701231667.e36c37e85b781d9dc9b88e0dbcdda7c08ee5f534.sam@gentoo> (raw)
commit: e36c37e85b781d9dc9b88e0dbcdda7c08ee5f534
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 29 04:18:48 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Nov 29 04:21:07 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e36c37e8
dev-python/structlog: Keyword 23.2.0 s390, #912839
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/structlog/structlog-23.2.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/structlog/structlog-23.2.0.ebuild b/dev-python/structlog/structlog-23.2.0.ebuild
index f9aab61d6b49..d196d1c98773 100644
--- a/dev-python/structlog/structlog-23.2.0.ebuild
+++ b/dev-python/structlog/structlog-23.2.0.ebuild
@@ -16,7 +16,7 @@ HOMEPAGE="
LICENSE="|| ( Apache-2.0 MIT )"
SLOT="0"
-KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~loong ~mips ppc ppc64 ~riscv ~sparc x86"
+KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~loong ~mips ppc ppc64 ~riscv ~s390 ~sparc x86"
BDEPEND="
dev-python/hatch-fancy-pypi-readme[${PYTHON_USEDEP}]
next reply other threads:[~2023-11-29 4:23 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 4:23 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-10 11:16 [gentoo-commits] repo/gentoo:master commit in: dev-python/structlog/ Michał Górny
2024-08-10 10:28 Michał Górny
2024-08-03 16:48 Jakov Smolić
2024-08-03 8:45 Michał Górny
2024-08-03 8:30 Jakov Smolić
2024-08-03 6:37 Michał Górny
2024-08-03 6:24 Michał Górny
2024-07-18 1:56 Michał Górny
2024-06-14 1:53 Michał Górny
2024-06-13 18:46 Arthur Zamarin
2024-06-12 10:29 Arthur Zamarin
2024-06-12 8:42 Jakov Smolić
2024-06-12 7:34 Arthur Zamarin
2024-06-12 7:00 Arthur Zamarin
2024-06-12 6:44 Arthur Zamarin
2024-05-28 4:27 Michał Górny
2024-05-18 9:41 Michał Górny
2024-01-25 11:37 Michał Górny
2024-01-25 5:48 Sam James
2024-01-24 20:34 Arthur Zamarin
2024-01-24 19:05 Michał Górny
2024-01-24 19:05 Michał Górny
2024-01-24 19:05 Michał Górny
2024-01-24 18:59 Michał Górny
2024-01-23 16:53 Michał Górny
2024-01-13 12:02 Sam James
2024-01-13 11:15 Sam James
2024-01-13 9:59 Arthur Zamarin
2024-01-13 9:29 Arthur Zamarin
2024-01-13 9:29 Arthur Zamarin
2024-01-09 7:02 Michał Górny
2023-12-29 17:08 Arthur Zamarin
2023-11-28 5:27 Arthur Zamarin
2023-11-28 5:27 Arthur Zamarin
2023-11-28 5:27 Arthur Zamarin
2023-11-01 16:05 Michał Górny
2023-11-01 12:23 Arthur Zamarin
2023-10-29 20:22 Sam James
2023-10-29 20:22 Sam James
2023-10-29 20:21 Sam James
2023-10-29 20:21 Sam James
2023-10-29 20:21 Sam James
2023-10-10 5:05 Michał Górny
2023-09-22 8:51 Arthur Zamarin
2023-09-09 9:35 WANG Xuerui
2023-08-24 18:04 Jakov Smolić
2023-08-22 20:19 Sam James
2023-08-22 17:06 Sam James
2023-06-01 14:59 Michał Górny
2023-04-08 6:08 Michał Górny
2023-04-07 4:19 Michał Górny
2023-02-10 11:53 Bernard Cafarelli
2023-02-10 8:15 Bernard Cafarelli
2023-02-09 23:27 Bernard Cafarelli
2019-04-09 3:14 Austin English
2018-06-26 18:09 Pacho Ramos
2016-06-08 19:02 Austin English
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=1701231667.e36c37e85b781d9dc9b88e0dbcdda7c08ee5f534.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