From: "James Le Cuirot" <chewi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/ddt/
Date: Thu, 30 Nov 2023 21:43:39 +0000 (UTC) [thread overview]
Message-ID: <1701380606.1f9e10d4e5ac998c2f17ca29b9ee92574f17ced7.chewi@gentoo> (raw)
commit: 1f9e10d4e5ac998c2f17ca29b9ee92574f17ced7
Author: James Le Cuirot <chewi <AT> gentoo <DOT> org>
AuthorDate: Thu Nov 30 21:41:27 2023 +0000
Commit: James Le Cuirot <chewi <AT> gentoo <DOT> org>
CommitDate: Thu Nov 30 21:43:26 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1f9e10d4
dev-python/ddt: Keyword 1.7.0 for ~m68k
The tests pass.
Signed-off-by: James Le Cuirot <chewi <AT> gentoo.org>
dev-python/ddt/ddt-1.7.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/ddt/ddt-1.7.0.ebuild b/dev-python/ddt/ddt-1.7.0.ebuild
index d42a40656231..3d120ddfed31 100644
--- a/dev-python/ddt/ddt-1.7.0.ebuild
+++ b/dev-python/ddt/ddt-1.7.0.ebuild
@@ -20,7 +20,7 @@ SRC_URI="
LICENSE="MIT"
SLOT="0"
-KEYWORDS="amd64 arm arm64 hppa ~riscv sparc x86"
+KEYWORDS="amd64 arm arm64 hppa ~m68k ~riscv sparc x86"
BDEPEND="
test? (
next reply other threads:[~2023-11-30 21:43 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 21:43 James Le Cuirot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-10 17:01 [gentoo-commits] repo/gentoo:master commit in: dev-python/ddt/ Michał Górny
2024-03-13 15:02 Michał Górny
2024-03-13 13:50 Arthur Zamarin
2024-02-26 4:35 Michał Górny
2024-01-25 4:43 Michał Górny
2024-01-25 0:42 Sam James
2024-01-23 15:08 Sam James
2024-01-18 19:48 Sam James
2024-01-18 19:48 Sam James
2024-01-18 18:52 Arthur Zamarin
2024-01-18 18:52 Arthur Zamarin
2024-01-18 18:37 Arthur Zamarin
2024-01-18 18:03 Arthur Zamarin
2024-01-03 8:35 Michał Górny
2023-12-16 2:45 Sam James
2023-12-11 4:33 Arthur Zamarin
2023-12-08 12:54 Arthur Zamarin
2023-12-02 11:06 Arthur Zamarin
2023-12-02 9:24 Arthur Zamarin
2023-12-01 3:30 Sam James
2023-11-29 14:42 Arthur Zamarin
2023-11-29 14:08 Arthur Zamarin
2023-11-29 11:15 Michał Górny
2023-11-29 11:04 Michał Górny
2023-11-29 10:04 Michał Górny
2023-11-29 10:03 Michał Górny
2023-11-08 13:49 Sam James
2023-11-08 13:49 Sam James
2023-11-08 13:49 Sam James
2023-11-08 13:37 Jakov Smolić
2023-11-08 8:08 Arthur Zamarin
2023-11-08 8:08 Arthur Zamarin
2023-11-08 6:38 Michał Górny
2023-05-31 16:05 Michał Górny
2022-11-30 10:18 WANG Xuerui
2022-09-11 5:31 Michał Górny
2022-09-10 22:57 Jakov Smolić
2022-08-11 8:50 Michał Górny
2022-06-24 11:33 Arthur Zamarin
2022-06-24 11:32 Arthur Zamarin
2022-05-24 6:16 Michał Górny
2022-05-16 14:23 Andrew Ammerlaan
2022-01-08 13:39 Arthur Zamarin
2022-01-05 17:57 Arthur Zamarin
2022-01-04 3:22 Sam James
2022-01-03 18:28 Arthur Zamarin
2021-11-27 9:38 James Le Cuirot
2021-11-26 15:33 Arthur Zamarin
2021-10-31 20:09 Arthur Zamarin
2021-10-31 17:55 Sam James
2021-10-05 8:27 Michał Górny
2021-09-27 22:16 Michał Górny
2021-09-23 15:35 Marek Szuba
2021-09-07 17:04 Sam James
2021-07-25 3:16 Matt Turner
2021-05-26 6:49 Agostino Sarubbo
2021-05-24 1:34 Joshua Kinard
2021-05-18 16:02 Michał Górny
2021-04-25 9:18 Sergei Trofimovich
2021-04-25 9:18 Sergei Trofimovich
2021-04-25 9:18 Sergei Trofimovich
2021-04-12 16:17 Michał Górny
2021-04-12 15:50 Sam James
2021-03-13 7:41 Michał Górny
2021-02-16 8:25 Sergei Trofimovich
2021-01-24 0:07 Sam James
2020-05-31 21:00 Michał Górny
2020-04-28 16:01 Michał Górny
2020-03-26 20:35 Michał Górny
2020-03-26 20:35 Michał Górny
2020-03-26 20:35 Michał Górny
2020-03-26 20:35 Michał Górny
2019-12-07 1:54 Patrick McLean
2018-01-27 23:33 Matt Thode
2018-01-03 9:11 Michał Górny
2017-06-02 2:59 Matt Thode
2017-05-11 13:09 Manuel Rüger
2017-03-22 16:03 Matt Thode
2016-07-18 9:32 Patrick Lauer
2016-02-18 15:23 Patrick Lauer
2015-11-10 8:24 Agostino Sarubbo
2015-11-10 8:19 Agostino Sarubbo
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=1701380606.1f9e10d4e5ac998c2f17ca29b9ee92574f17ced7.chewi@gentoo \
--to=chewi@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