public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/breathe/
Date: Sun, 15 Mar 2020 12:17:06 +0000 (UTC)	[thread overview]
Message-ID: <1584274561.ff6551ae2f9b9f8fa64756929b3e10e4040e64f7.zlogene@gentoo> (raw)

commit:     ff6551ae2f9b9f8fa64756929b3e10e4040e64f7
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 15 12:16:01 2020 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun Mar 15 12:16:01 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ff6551ae

dev-python/breathe: Add ~arm keyword wrt bug #709752

Package-Manager: Portage-2.3.89, Repoman-2.3.20
RepoMan-Options: --include-arches="arm"
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>

 dev-python/breathe/breathe-4.6.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/breathe/breathe-4.6.0.ebuild b/dev-python/breathe/breathe-4.6.0.ebuild
index 5aa8a0808ea..a55de22e45d 100644
--- a/dev-python/breathe/breathe-4.6.0.ebuild
+++ b/dev-python/breathe/breathe-4.6.0.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="~amd64 ~ppc64 ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~amd64 ~arm ~ppc64 ~x86 ~amd64-linux ~x86-linux"
 IUSE=""
 
 RDEPEND="


             reply	other threads:[~2020-03-15 12:17 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 12:17 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-14 15:55 [gentoo-commits] repo/gentoo:master commit in: dev-python/breathe/ Michał Górny
2024-05-08 12:16 Michał Górny
2024-05-08  8:51 Michał Górny
2023-06-01  4:07 Michał Górny
2023-04-05  7:39 Arthur Zamarin
2023-03-01  6:16 Michał Górny
2022-12-23 11:25 Michał Górny
2022-07-24 20:28 Michał Górny
2022-07-24 19:13 Sam James
2022-06-21  6:00 Michał Górny
2022-05-18 11:16 Andrew Ammerlaan
2022-03-15 11:16 Michał Górny
2022-03-15 10:37 Jakov Smolić
2022-02-14 21:37 Michał Górny
2022-02-14  8:32 Michał Górny
2022-01-30  7:22 Michał Górny
2021-10-16  5:59 Michał Górny
2021-10-15 22:42 Sam James
2021-09-15 20:26 Michał Górny
2021-06-05 21:01 Michał Górny
2021-06-05 12:56 Michał Górny
2021-05-07  8:04 Michał Górny
2021-05-06 11:12 Michał Górny
2021-05-06 10:06 Sam James
2021-05-01  7:45 Michał Górny
2021-04-23  7:25 Michał Górny
2021-04-10  8:04 Michał Górny
2021-03-30  7:49 Michał Górny
2021-03-19 21:39 Michał Górny
2021-03-19 20:14 Sam James
2021-03-14 22:39 Michał Górny
2021-03-14 22:33 Sam James
2021-02-16 17:08 Michał Górny
2021-02-06 14:26 Sam James
2021-02-06 14:20 Sam James
2021-02-06 14:15 Sam James
2021-02-06 13:27 Sam James
2021-02-06  1:10 Sam James
2021-02-06  1:10 Sam James
2021-01-14 20:09 Sergei Trofimovich
2020-12-27 12:51 Sergei Trofimovich
2020-12-24 22:06 Sergei Trofimovich
2020-12-22 21:04 Sam James
2020-12-22 21:03 Sam James
2020-12-16 17:18 Michał Górny
2020-12-16 10:09 Michał Górny
2020-12-13 12:15 Michał Górny
2020-12-13  8:58 Sam James
2020-12-11 23:07 Sergei Trofimovich
2020-12-05  9:52 Michał Górny
2020-10-31  9:47 Joonas Niilola
2020-10-31  9:47 Joonas Niilola
2020-09-29 21:25 Sergei Trofimovich
2020-09-13  8:44 Sergei Trofimovich
2020-08-11 11:00 Agostino Sarubbo
2020-07-12  1:51 Sam James
2020-06-01  4:16 Matt Turner
2020-05-31 15:17 Sergei Trofimovich
2020-05-28 18:20 Sergei Trofimovich
2020-05-02 13:30 Mart Raudsepp
2020-04-04 10:52 Sergei Trofimovich
2020-03-26 13:49 Michał Górny
2020-03-26 13:49 Michał Górny
2020-03-25 11:17 Joonas Niilola
2020-03-01 18:36 Matthias Maier
2020-02-16  7:13 Georgy Yakovlev
2019-03-26 18:52 Aaron Bauman
2018-06-27 20:44 Pacho Ramos
2017-02-26 18:02 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=1584274561.ff6551ae2f9b9f8fa64756929b3e10e4040e64f7.zlogene@gentoo \
    --to=zlogene@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