From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/readme_renderer/
Date: Tue, 10 Dec 2019 19:25:49 +0000 (UTC) [thread overview]
Message-ID: <1576005934.cc52bf9cf33c5c501d85eddd3232cb0c50f2f09d.slyfox@gentoo> (raw)
commit: cc52bf9cf33c5c501d85eddd3232cb0c50f2f09d
Author: Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Tue Dec 10 17:13:28 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Tue Dec 10 19:25:34 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cc52bf9c
dev-python/readme_renderer: keyworded 24.0-r1 for sparc, bug #700918
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="sparc"
Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
dev-python/readme_renderer/readme_renderer-24.0-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/readme_renderer/readme_renderer-24.0-r1.ebuild b/dev-python/readme_renderer/readme_renderer-24.0-r1.ebuild
index f000d90c102..281788626d7 100644
--- a/dev-python/readme_renderer/readme_renderer-24.0-r1.ebuild
+++ b/dev-python/readme_renderer/readme_renderer-24.0-r1.ebuild
@@ -12,7 +12,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
LICENSE="Apache-2.0"
SLOT="0"
-KEYWORDS="~amd64 ~hppa ~x86"
+KEYWORDS="~amd64 ~hppa ~sparc ~x86"
RDEPEND="
>=dev-python/bleach-2.1.0[${PYTHON_USEDEP}]
next reply other threads:[~2019-12-10 19:25 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 19:25 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-16 4:07 [gentoo-commits] repo/gentoo:master commit in: dev-python/readme_renderer/ Michał Górny
2022-12-10 9:03 Michał Górny
2022-12-10 8:55 Arthur Zamarin
2022-11-01 5:19 Michał Górny
2022-10-08 20:10 Michał Górny
2022-10-08 16:03 Arthur Zamarin
2022-09-25 6:39 Arthur Zamarin
2022-09-06 20:35 Michał Górny
2022-09-06 18:35 Arthur Zamarin
2022-09-06 17:54 Arthur Zamarin
2022-08-07 8:11 Michał Górny
2022-05-27 19:48 Michał Górny
2022-05-27 9:07 Jakov Smolić
2022-05-24 6:16 Michał Górny
2022-04-25 16:50 Sam James
2022-04-20 7:47 Michał Górny
2022-04-09 18:39 Michał Górny
2022-04-09 16:47 Arthur Zamarin
2022-03-14 17:04 Michał Górny
2022-03-09 19:13 Arthur Zamarin
2022-01-13 21:53 Michał Górny
2022-01-13 19:27 Arthur Zamarin
2022-01-10 19:50 Michał Górny
2022-01-10 19:40 Arthur Zamarin
2021-12-14 10:21 Michał Górny
2021-12-10 17:12 Arthur Zamarin
2021-10-31 20:29 Michał Górny
2021-10-31 20:29 Michał Górny
2021-10-31 17:55 Sam James
2021-09-30 21:50 Michał Górny
2021-07-28 23:38 Marek Szuba
2021-06-02 16:26 Michał Górny
2021-03-25 19:09 Michał Górny
2021-03-25 14:23 Sam James
2021-02-23 7:43 Michał Górny
2020-11-28 15:26 Sam James
2020-11-26 8:26 Michał Górny
2020-11-26 6:56 Agostino Sarubbo
2020-11-16 8:22 Michał Górny
2020-11-16 1:15 Sam James
2020-10-21 6:58 Michał Górny
2020-10-10 5:54 Michał Górny
2020-07-25 8:31 Michał Górny
2020-07-14 15:57 Sam James
2020-07-14 13:19 Sam James
2020-07-11 8:13 Michał Górny
2020-07-11 8:13 Michał Górny
2020-07-09 8:59 Agostino Sarubbo
2020-07-09 7:06 Sergei Trofimovich
2020-07-05 9:27 Sergei Trofimovich
2020-07-02 17:05 Sergei Trofimovich
2020-07-01 12:21 Michał Górny
2020-06-01 20:30 Michał Górny
2020-05-31 10:04 Sergei Trofimovich
2020-05-30 14:37 Michał Górny
2020-05-30 11:51 Michał Górny
2020-05-27 21:15 Michał Górny
2020-05-27 20:45 Michał Górny
2020-05-04 11:49 Michał Górny
2020-05-03 19:02 Agostino Sarubbo
2020-03-29 7:04 Michał Górny
2020-03-17 2:09 Matt Turner
2020-03-17 1:37 Matt Turner
2020-03-04 5:01 Michał Górny
2020-02-03 11:31 Agostino Sarubbo
2020-01-31 13:45 Agostino Sarubbo
2019-12-04 22:28 Patrick McLean
2019-08-24 3:55 Tim Harder
2017-08-20 2:17 Tim Harder
2017-05-13 22:28 Tim Harder
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=1576005934.cc52bf9cf33c5c501d85eddd3232cb0c50f2f09d.slyfox@gentoo \
--to=slyfox@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