From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/sphinx-basic-ng/
Date: Sun, 11 Sep 2022 07:55:52 +0000 (UTC) [thread overview]
Message-ID: <1662882940.347d9afd4d94c215e98598e931cc9bc76e62cf94.ago@gentoo> (raw)
commit: 347d9afd4d94c215e98598e931cc9bc76e62cf94
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 11 07:55:40 2022 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Sun Sep 11 07:55:40 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=347d9afd
dev-python/sphinx-basic-ng: Stabilize 0.0.1_alpha12 sparc, #869551
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
dev-python/sphinx-basic-ng/sphinx-basic-ng-0.0.1_alpha12.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/sphinx-basic-ng/sphinx-basic-ng-0.0.1_alpha12.ebuild b/dev-python/sphinx-basic-ng/sphinx-basic-ng-0.0.1_alpha12.ebuild
index e8a6131cc845..12fb01926fbc 100644
--- a/dev-python/sphinx-basic-ng/sphinx-basic-ng-0.0.1_alpha12.ebuild
+++ b/dev-python/sphinx-basic-ng/sphinx-basic-ng-0.0.1_alpha12.ebuild
@@ -22,7 +22,7 @@ S=${WORKDIR}/${MY_P}
LICENSE="MIT"
SLOT="0"
-KEYWORDS="amd64 arm arm64 ~hppa ~ia64 ~m68k ~ppc ~ppc64 ~riscv ~s390 ~sparc x86"
+KEYWORDS="amd64 arm arm64 ~hppa ~ia64 ~m68k ~ppc ~ppc64 ~riscv ~s390 sparc x86"
IUSE="test"
RESTRICT="!test? ( test )"
next reply other threads:[~2022-09-11 7:55 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 7:55 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-19 20:07 [gentoo-commits] repo/gentoo:master commit in: dev-python/sphinx-basic-ng/ Michał Górny
2024-12-08 17:34 Arthur Zamarin
2024-05-27 19:33 Petr Vaněk
2023-08-15 9:32 Michał Górny
2023-08-15 7:34 Sam James
2023-08-12 21:53 Sam James
2023-08-12 0:10 Sam James
2023-08-12 0:10 Sam James
2023-08-12 0:10 Sam James
2023-08-11 19:22 Arthur Zamarin
2023-08-11 19:18 Arthur Zamarin
2023-08-11 19:15 Arthur Zamarin
2023-07-09 3:26 Michał Górny
2023-06-09 18:21 Arthur Zamarin
2023-04-05 15:58 Michał Górny
2023-04-05 12:53 Arthur Zamarin
2023-04-05 9:30 Arthur Zamarin
2023-04-05 8:26 Arthur Zamarin
2023-04-05 7:49 Arthur Zamarin
2023-04-05 7:40 Arthur Zamarin
2023-04-05 7:34 Arthur Zamarin
2023-04-05 7:17 Arthur Zamarin
2023-04-05 7:06 Arthur Zamarin
2023-02-02 18:46 Michał Górny
2022-10-07 7:03 Michał Górny
2022-09-17 5:56 Michał Górny
2022-09-17 5:38 Arthur Zamarin
2022-09-16 18:11 Arthur Zamarin
2022-09-16 13:11 Arthur Zamarin
2022-09-11 7:55 Agostino Sarubbo
2022-09-10 22:57 Jakov Smolić
2022-09-10 22:57 Jakov Smolić
2022-09-10 22:37 Jakov Smolić
2022-08-11 9:59 Michał Górny
2022-08-04 0:13 Sam James
2022-08-03 7:49 Agostino Sarubbo
2022-08-02 19:00 Arthur Zamarin
2022-08-02 18:47 Arthur Zamarin
2022-08-02 18:36 Arthur Zamarin
2022-08-02 17:52 Arthur Zamarin
2022-08-02 17:50 Arthur Zamarin
2022-08-02 17:50 Arthur Zamarin
2022-07-11 12:14 James Le Cuirot
2022-07-03 22:48 Sam James
2022-07-03 14:43 Jakov Smolić
2022-07-01 6:10 Arthur Zamarin
2022-07-01 6:02 Arthur Zamarin
2022-07-01 5:59 Arthur Zamarin
2022-07-01 5:54 Arthur Zamarin
2022-06-30 21:41 Sam James
2022-06-30 17:57 Arthur Zamarin
2022-06-30 6:56 Jakov Smolić
2022-06-29 18:11 Arthur Zamarin
2022-06-29 17:49 Sam James
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=1662882940.347d9afd4d94c215e98598e931cc9bc76e62cf94.ago@gentoo \
--to=ago@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