public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/recommonmark/
Date: Sat, 30 Jun 2018 19:30:59 +0000 (UTC)	[thread overview]
Message-ID: <1530387036.738afc6a229f891236ffbce7b79eb388118a29f1.leio@gentoo> (raw)

commit:     738afc6a229f891236ffbce7b79eb388118a29f1
Author:     Roy Bamford <neddyseagoon <AT> gentoo <DOT> org>
AuthorDate: Sat Jun 30 19:28:20 2018 +0000
Commit:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Sat Jun 30 19:30:36 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=738afc6a

dev-python/recommonmark: added ~arm64 keyword

Package-Manager: Portage-2.3.40, Repoman-2.3.9

 dev-python/recommonmark/recommonmark-0.4.0.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-python/recommonmark/recommonmark-0.4.0.ebuild b/dev-python/recommonmark/recommonmark-0.4.0.ebuild
index 999927bcac1..70feb3a9e23 100644
--- a/dev-python/recommonmark/recommonmark-0.4.0.ebuild
+++ b/dev-python/recommonmark/recommonmark-0.4.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
@@ -13,7 +13,7 @@ LICENSE="MIT"
 SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 SLOT="0"
-KEYWORDS="amd64 x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 ~arm64 x86 ~amd64-linux ~x86-linux"
 RDEPEND="
 	dev-python/docutils[${PYTHON_USEDEP}]
 	<=dev-python/CommonMark-0.5.4[${PYTHON_USEDEP}]


             reply	other threads:[~2018-06-30 19:31 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30 19:30 Mart Raudsepp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-09  9:21 [gentoo-commits] repo/gentoo:master commit in: dev-python/recommonmark/ Petr Vaněk
2023-06-01 16:32 Arthur Zamarin
2023-03-22  5:30 Sam James
2023-03-21  5:43 Michał Górny
2023-03-21  5:43 Michał Górny
2022-07-02 12:24 Arthur Zamarin
2022-07-02 12:23 Arthur Zamarin
2022-05-29 18:53 Arthur Zamarin
2022-05-29 18:53 Arthur Zamarin
2022-04-25 19:22 Sam James
2022-01-02 11:52 James Le Cuirot
2021-07-01 14:06 Marek Szuba
2021-06-05 18:14 Michał Górny
2021-03-14 22:39 Michał Górny
2021-03-14 22:33 Sam James
2021-02-11 10:05 Michał Górny
2021-02-11  9:30 Sam James
2021-02-06 22:37 Sam James
2020-05-17  8:04 Michał Górny
2020-05-11 17:48 Michał Górny
2020-05-06 20:18 Sergei Trofimovich
2020-05-06 17:34 Sergei Trofimovich
2020-05-06  7:18 Sergei Trofimovich
2020-05-06  7:01 Sergei Trofimovich
2020-03-29  7:04 Michał Górny
2020-03-29  7:04 Michał Górny
2020-03-29  7:04 Michał Górny
2020-03-25 15:27 Agostino Sarubbo
2020-03-25 13:27 Agostino Sarubbo
2020-03-25 13:12 Agostino Sarubbo
2020-03-25 12:36 Agostino Sarubbo
2020-03-24 21:46 Michał Górny
2020-03-24 21:46 Michał Górny
2019-12-16 17:27 Sebastian Pipping
2019-04-09  1:32 Aaron Bauman
2019-03-16 18:40 Sergei Trofimovich
2019-03-02 21:30 Matt Turner
2019-03-02 20:02 Matt Turner
2019-02-15 17:05 Mikle Kolyada
2019-02-15 15:46 Thomas Deutschmann
2019-02-13 12:46 Michał Górny
2019-02-12 21:03 Sergei Trofimovich
2019-02-12  8:52 Mikle Kolyada
2019-02-12  8:11 Sergei Trofimovich
2019-02-11 23:36 Sergei Trofimovich
2019-02-10 23:52 Matt Turner
2019-02-10 23:52 Matt Turner
2019-02-10 23:10 Matt Turner
2019-02-10  7:46 Mikle Kolyada
2018-11-28 22:16 Matt Turner
2018-11-25 10:27 Mikle Kolyada
2018-11-07 22:41 Sergei Trofimovich
2018-10-28 10:19 Sergei Trofimovich
2018-10-18 16:39 Michał Górny
2018-10-18 16:39 Michał Górny
2018-10-18  4:32 Matt Turner
2018-10-18  4:32 Matt Turner
2018-09-20  8:43 Michał Górny
2017-09-30  0:31 Matt Thode
2017-07-15 16:22 Tobias Klausmann
2017-04-28 17:00 Manuel Rüger
2017-01-02 16:13 Sebastien Fabbro

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=1530387036.738afc6a229f891236ffbce7b79eb388118a29f1.leio@gentoo \
    --to=leio@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