public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/myst_parser/
Date: Mon,  7 Feb 2022 11:31:24 +0000 (UTC)	[thread overview]
Message-ID: <1644233459.438cca8fe57ac4292de77165203702a58f68e825.sam@gentoo> (raw)

commit:     438cca8fe57ac4292de77165203702a58f68e825
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Feb  7 11:30:59 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Feb  7 11:30:59 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=438cca8f

dev-python/myst_parser: Keyword 0.16.1_p20220119 ppc64, #831852

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-python/myst_parser/myst_parser-0.16.1_p20220119.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/myst_parser/myst_parser-0.16.1_p20220119.ebuild b/dev-python/myst_parser/myst_parser-0.16.1_p20220119.ebuild
index 809fca7557e4..f0803b676b38 100644
--- a/dev-python/myst_parser/myst_parser-0.16.1_p20220119.ebuild
+++ b/dev-python/myst_parser/myst_parser-0.16.1_p20220119.ebuild
@@ -21,7 +21,7 @@ S="${WORKDIR}/MyST-Parser-${COMMIT}"
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~amd64 ~arm ~ia64 ~ppc ~x86"
+KEYWORDS="~amd64 ~arm ~ia64 ~ppc ~ppc64 ~x86"
 
 RDEPEND="
 	<dev-python/docutils-0.18[${PYTHON_USEDEP}]


             reply	other threads:[~2022-02-07 11:31 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 11:31 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-13 11:51 [gentoo-commits] repo/gentoo:master commit in: dev-python/myst_parser/ Michał Górny
2022-11-04  8:38 Michał Górny
2022-11-04  8:23 Arthur Zamarin
2022-10-07  7:03 Michał Górny
2022-09-27 18:25 Arthur Zamarin
2022-07-11 17:45 Michał Górny
2022-07-11 16:32 Arthur Zamarin
2022-07-11 12:14 James Le Cuirot
2022-07-10 23:08 Sam James
2022-07-10 22:28 Sam James
2022-07-10 20:02 Arthur Zamarin
2022-07-10 19:40 Arthur Zamarin
2022-07-10 18:51 Arthur Zamarin
2022-07-10 18:48 Arthur Zamarin
2022-07-10 18:04 Arthur Zamarin
2022-07-03 18:15 Arthur Zamarin
2022-06-30 17:57 Arthur Zamarin
2022-06-29 18:11 Arthur Zamarin
2022-06-28 15:44 Arthur Zamarin
2022-06-24 15:46 Michał Górny
2022-06-17 13:07 Jakov Smolić
2022-06-10  5:29 Jakov Smolić
2022-06-08 12:21 Jakov Smolić
2022-06-08  8:13 Jakov Smolić
2022-06-08  7:44 Jakov Smolić
2022-06-08  7:24 Jakov Smolić
2022-06-08  5:35 Michał Górny
2022-05-29 19:16 Arthur Zamarin
2022-05-21 17:35 Jakov Smolić
2022-04-18  8:19 Michał Górny
2022-04-16 15:36 Arthur Zamarin
2022-03-20 20:38 Arthur Zamarin
2022-03-20 20:38 Arthur Zamarin
2022-03-17 20:08 Sam James
2022-03-15  9:38 Jakov Smolić
2022-03-14 18:33 Agostino Sarubbo
2022-03-12 19:21 Arthur Zamarin
2022-03-06  8:52 Agostino Sarubbo
2022-03-06  8:50 Agostino Sarubbo
2022-02-27 10:52 Michał Górny
2022-02-11 21:18 Michał Górny
2022-02-09 14:18 Yixun Lan
2022-02-07 22:29 Sam James
2022-02-07 11:36 Sam James
2022-02-07 11:32 Sam James
2022-02-07 11:30 Sam James
2022-02-07 11:18 Sam James
2022-02-07  8:33 Sam James
2022-01-23 18:50 Arthur Zamarin

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=1644233459.438cca8fe57ac4292de77165203702a58f68e825.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