From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/ansi2html/
Date: Sun, 10 May 2020 09:26:47 +0000 (UTC) [thread overview]
Message-ID: <1589102802.333b9fcdd8b2418dc864814e135a80ea9f3b2ee1.zlogene@gentoo> (raw)
commit: 333b9fcdd8b2418dc864814e135a80ea9f3b2ee1
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun May 10 09:25:59 2020 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun May 10 09:26:42 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=333b9fcd
dev-python/ansi2html: arm stable wrt bug #721756
Package-Manager: Portage-2.3.99, Repoman-2.3.22
RepoMan-Options: --include-arches="arm"
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
dev-python/ansi2html/ansi2html-1.5.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/ansi2html/ansi2html-1.5.2.ebuild b/dev-python/ansi2html/ansi2html-1.5.2.ebuild
index 75a78c6ab41..1b2b66b4b9d 100644
--- a/dev-python/ansi2html/ansi2html-1.5.2.ebuild
+++ b/dev-python/ansi2html/ansi2html-1.5.2.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
LICENSE="LGPL-3+"
SLOT="0"
-KEYWORDS="amd64 ~arm ~x86"
+KEYWORDS="amd64 arm ~x86"
IUSE="test"
RESTRICT="!test? ( test )"
next reply other threads:[~2020-05-10 9:26 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 9:26 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-13 8:01 [gentoo-commits] repo/gentoo:master commit in: dev-python/ansi2html/ Michał Górny
2024-07-13 7:27 Arthur Zamarin
2024-06-22 19:09 Sebastian Pipping
2024-05-17 14:26 Michał Górny
2023-12-30 22:23 Sam James
2023-12-30 14:40 Michał Górny
2023-12-11 17:42 Michał Górny
2023-12-05 4:20 Michał Górny
2023-11-05 18:04 Michał Górny
2023-11-05 17:55 Michał Górny
2023-11-05 16:47 Arthur Zamarin
2023-11-05 14:45 Sebastian Pipping
2023-03-16 3:44 Michał Górny
2022-08-09 5:51 Michał Górny
2022-08-08 19:50 Arthur Zamarin
2022-07-09 16:12 Sebastian Pipping
2022-07-07 19:11 Arthur Zamarin
2022-07-07 19:11 Arthur Zamarin
2022-06-25 16:37 Jakov Smolić
2022-04-30 17:43 Sebastian Pipping
2022-03-15 11:16 Michał Górny
2022-03-15 9:59 Jakov Smolić
2022-02-04 12:04 Michał Górny
2022-01-31 18:15 Sebastian Pipping
2021-06-05 12:36 Michał Górny
2020-12-22 18:24 Michał Górny
2020-12-22 17:08 Thomas Deutschmann
2020-12-21 22:36 Sam James
2020-12-21 22:36 Sam James
2020-11-18 14:21 Sebastian Pipping
2020-10-25 21:48 Sam James
2020-10-25 21:34 Thomas Deutschmann
2020-10-21 21:45 Michał Górny
2020-09-16 22:31 Louis Sautier
2020-07-08 13:08 Michał Górny
2020-05-21 0:36 Sebastian Pipping
2020-05-10 9:26 Mikle Kolyada
2020-05-10 9:26 Mikle Kolyada
2020-03-17 7:23 Michał Górny
2019-12-29 13:06 David Seifert
2018-10-22 18:51 Sebastian Pipping
2018-10-20 15:09 Sebastian Pipping
2018-06-26 16:15 Mikle Kolyada
2018-06-24 12:37 Jason Zaman
2018-04-25 12:58 Sebastian Pipping
2018-04-14 0:10 Sebastian Pipping
2018-01-14 23:58 Sebastian Pipping
2017-12-05 5:44 Markus Meier
2017-10-21 16:17 Pacho Ramos
2017-02-22 22:18 Sebastian Pipping
2016-07-23 18:40 Patrice Clement
2016-07-23 18:40 Patrice Clement
2016-03-12 11:40 Patrick Lauer
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=1589102802.333b9fcdd8b2418dc864814e135a80ea9f3b2ee1.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