public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pyenchant/
Date: Sun,  1 Aug 2021 08:08:46 +0000 (UTC)	[thread overview]
Message-ID: <1627805322.e67be2aa4e7f75705d8371bb89d61f9f4e8ab22d.ago@gentoo> (raw)

commit:     e67be2aa4e7f75705d8371bb89d61f9f4e8ab22d
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Sun Aug  1 08:08:42 2021 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Sun Aug  1 08:08:42 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e67be2aa

dev-python/pyenchant: ppc64 stable wrt bug #805416

Package-Manager: Portage-3.0.20, Repoman-3.0.2
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

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

diff --git a/dev-python/pyenchant/pyenchant-3.2.1.ebuild b/dev-python/pyenchant/pyenchant-3.2.1.ebuild
index 22ca3716005..e6471cde2d1 100644
--- a/dev-python/pyenchant/pyenchant-3.2.1.ebuild
+++ b/dev-python/pyenchant/pyenchant-3.2.1.ebuild
@@ -16,7 +16,7 @@ SRC_URI="
 
 LICENSE="LGPL-2.1"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 arm ~arm64 ~hppa ~ia64 ~ppc ~ppc64 ~riscv ~sparc ~x86"
+KEYWORDS="~alpha ~amd64 arm ~arm64 ~hppa ~ia64 ~ppc ppc64 ~riscv ~sparc ~x86"
 
 RDEPEND="app-text/enchant:*"
 BDEPEND="


             reply	other threads:[~2021-08-01  8:08 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-01  8:08 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-06 14:03 [gentoo-commits] repo/gentoo:master commit in: dev-python/pyenchant/ Ionen Wolkens
2024-05-18  7:26 Michał Górny
2023-11-07 16:02 Michał Górny
2023-11-07 16:02 Michał Górny
2022-06-27  9:29 Michał Górny
2022-06-27  8:27 Agostino Sarubbo
2022-06-27  7:37 Agostino Sarubbo
2022-06-27  7:35 Agostino Sarubbo
2022-06-27  7:34 Agostino Sarubbo
2022-06-26 18:22 Arthur Zamarin
2022-06-26 17:24 Arthur Zamarin
2022-06-26 17:13 Arthur Zamarin
2022-05-26  8:07 Michał Górny
2022-05-26  8:07 Michał Górny
2022-04-26  2:58 Sam James
2021-11-15  8:46 Michał Górny
2021-11-15  8:42 Agostino Sarubbo
2021-11-14 20:30 Sam James
2021-11-14  9:06 Agostino Sarubbo
2021-11-14  3:21 Sam James
2021-11-13 19:50 Sam James
2021-11-13 19:50 Sam James
2021-11-13  9:26 Arthur Zamarin
2021-10-06  7:46 Michał Górny
2021-09-04 21:57 Michał Górny
2021-08-03 15:36 Agostino Sarubbo
2021-08-03 10:57 Agostino Sarubbo
2021-08-02  4:03 Agostino Sarubbo
2021-08-01  8:09 Agostino Sarubbo
2021-07-31 22:12 Sam James
2021-06-24 18:40 Michał Górny
2021-06-05 17:59 Michał Górny
2021-01-18 14:55 Michał Górny
2021-01-18 14:53 Sam James
2021-01-15  0:01 Sam James
2021-01-14 23:59 Sam James
2021-01-13 21:55 Sam James
2021-01-13 21:55 Sam James
2021-01-13 19:34 Sam James
2021-01-13 19:06 Sam James
2020-12-14 12:29 Michał Górny
2020-09-27  6:42 Matt Turner
2020-08-22 12:29 Michał Górny
2020-08-22 11:39 Michał Górny
2020-08-22 11:26 Agostino Sarubbo
2020-08-22  5:50 Agostino Sarubbo
2020-08-19  3:34 Michał Górny
2020-08-18 21:53 Sergei Trofimovich
2020-08-02  8:52 Michał Górny
2020-07-19 12:39 Sam James
2020-07-18 13:31 Sam James
2020-07-11 19:55 Sergei Trofimovich
2020-06-12 18:24 Michał Górny
2020-05-20  9:30 Michał Górny
2020-04-11 11:30 Michał Górny
2020-04-11  7:49 Michał Górny
2020-02-08  9:28 Mart Raudsepp
2020-02-02 19:35 Mart Raudsepp
2019-12-30 21:54 Piotr Karbowski
2019-12-04  6:48 Aaron Bauman
2019-07-29 20:02 Aaron Bauman
2019-03-11 21:03 Andreas Sturmlechner
2018-07-28 17:22 Louis Sautier
2018-07-28 17:22 Louis Sautier
2017-09-28 13:42 Michael Palimaka
2017-09-08 20:53 Markus Meier
2017-02-13  9:13 Zac Medico
2016-09-05 21:50 Manuel Rüger
2016-01-30 16:20 Ian Delaney

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=1627805322.e67be2aa4e7f75705d8371bb89d61f9f4e8ab22d.ago@gentoo \
    --to=ago@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