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/python-gnupg/
Date: Fri,  7 Jul 2023 00:45:53 +0000 (UTC)	[thread overview]
Message-ID: <1688690657.5a8c9cdfaba2fa2508a833afe7ce20d3a5410466.sam@gentoo> (raw)

commit:     5a8c9cdfaba2fa2508a833afe7ce20d3a5410466
Author:     Matoro Mahri <matoro <AT> users <DOT> noreply <DOT> github <DOT> com>
AuthorDate: Thu Jul  6 20:29:49 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Jul  7 00:44:17 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5a8c9cdf

dev-python/python-gnupg: Keyword 0.5.0 mips, #902731

Signed-off-by: Matoro Mahri <matoro <AT> users.noreply.github.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>

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

diff --git a/dev-python/python-gnupg/python-gnupg-0.5.0.ebuild b/dev-python/python-gnupg/python-gnupg-0.5.0.ebuild
index 6eea606b0973..066044812645 100644
--- a/dev-python/python-gnupg/python-gnupg-0.5.0.ebuild
+++ b/dev-python/python-gnupg/python-gnupg-0.5.0.ebuild
@@ -17,7 +17,7 @@ HOMEPAGE="
 SRC_URI="https://github.com/vsajip/python-gnupg/releases/download/${PV}/${P}.tar.gz"
 SRC_URI+=" verify-sig? ( https://github.com/vsajip/python-gnupg/releases/download/${PV}/${P}.tar.gz.asc )"
 
-KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~loong ~m68k ppc ppc64 ~riscv sparc x86"
+KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~loong ~m68k ~mips ppc ppc64 ~riscv sparc x86"
 LICENSE="BSD"
 SLOT="0"
 


             reply	other threads:[~2023-07-07  0:45 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07  0:45 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-12  6:36 [gentoo-commits] repo/gentoo:master commit in: dev-python/python-gnupg/ Sam James
2024-09-21  7:41 Michał Górny
2024-06-18 16:05 Petr Vaněk
2024-06-18 15:07 Petr Vaněk
2023-12-30 14:40 Michał Górny
2023-12-12 16:50 Michał Górny
2023-08-24 12:47 Michał Górny
2023-08-24 12:40 Sam James
2023-07-22 12:58 Arthur Zamarin
2023-06-07  9:27 Sam James
2023-06-07  9:27 Sam James
2023-04-08  6:47 Viorel Munteanu
2023-04-07 21:39 James Le Cuirot
2023-04-01  0:55 Sam James
2023-03-31 21:28 Sam James
2023-03-29 18:24 Arthur Zamarin
2023-03-29 14:58 Sam James
2023-03-29 11:24 Sam James
2023-03-29 11:24 Sam James
2023-03-29 11:24 Sam James
2023-03-29 11:05 Sam James
2023-03-29 11:05 Sam James
2023-03-29 11:03 Sam James
2022-11-30 10:18 WANG Xuerui
2022-10-07  7:03 Michał Górny
2022-09-26  6:15 Michał Górny
2022-09-25 23:58 Sam James
2022-08-24  0:21 Sam James
2022-07-14  4:16 Sam James
2022-06-28  4:03 Michał Górny
2022-06-27 23:32 Sam James
2022-05-27 19:08 Arthur Zamarin
2022-05-20 23:16 Sam James
2021-12-25 21:30 Michał Górny
2021-12-25 19:09 Jakov Smolić
2021-11-25  8:11 Michał Górny
2021-05-22 10:52 Michał Górny
2021-04-12 16:17 Michał Górny
2021-04-12 15:50 Sam James
2021-03-11 12:35 Michał Górny
2020-08-02 22:04 Sam James
2020-07-11  8:13 Michał Górny
2020-07-11  8:13 Michał Górny
2020-07-09  8:59 Agostino Sarubbo
2020-04-18 14:01 Sebastian Pipping
2020-03-03  9:18 Michał Górny
2019-12-20 12:50 Agostino Sarubbo
2019-12-18 14:57 Agostino Sarubbo
2019-12-17 18:40 Conrad Kostecki
2019-04-22 13:07 Anthony G. Basile
2019-04-08  2:18 Thomas Deutschmann
2019-02-15 16:22 Manuel Rüger
2018-06-24 19:21 Pacho Ramos
2018-04-29  7:35 Michał Górny
2018-02-04  4:11 Anthony G. Basile
2017-10-28 21:28 Patrice Clement
2017-08-05 21:08 Sergei Trofimovich
2017-06-03 16:14 Markus Meier
2016-06-09 10:19 Tiziano Müller
2015-09-25  7:36 Justin Lecher

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=1688690657.5a8c9cdfaba2fa2508a833afe7ce20d3a5410466.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