From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pyGPG/
Date: Wed, 3 May 2023 05:35:22 +0000 (UTC) [thread overview]
Message-ID: <1683092111.8da0d0ba21eef81ca711698918268ab721d1126a.sam@gentoo> (raw)
commit: 8da0d0ba21eef81ca711698918268ab721d1126a
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed May 3 05:35:11 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed May 3 05:35:11 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8da0d0ba
dev-python/pyGPG: mark ALLARCHES
Bug: https://bugs.gentoo.org/905424
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/pyGPG/metadata.xml | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-python/pyGPG/metadata.xml b/dev-python/pyGPG/metadata.xml
index 9f215a16d869..b04f3dcc2151 100644
--- a/dev-python/pyGPG/metadata.xml
+++ b/dev-python/pyGPG/metadata.xml
@@ -9,6 +9,7 @@
It also connects to gpg's status-fd output and makes all the status data
available as subclassed namedtuple instances.
</longdescription>
+ <stabilize-allarches/>
<upstream>
<remote-id type="github">dol-sen/pyGPG</remote-id>
</upstream>
next reply other threads:[~2023-05-03 5:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 5:35 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-03 6:33 [gentoo-commits] repo/gentoo:master commit in: dev-python/pyGPG/ Arthur Zamarin
2023-05-03 5:25 Sam James
2023-05-02 20:50 Sam James
2023-05-02 20:50 Sam James
2023-05-02 20:26 Sam James
2023-05-01 15:00 Sam James
2023-02-16 3:29 Sam James
2022-03-18 11:41 Michał Górny
2022-03-18 9:02 Arthur Zamarin
2022-03-17 7:45 Agostino Sarubbo
2022-03-16 23:53 Sam James
2022-03-15 17:56 Jakov Smolić
2022-03-15 11:27 Jakov Smolić
2022-03-15 11:27 Jakov Smolić
2022-02-02 15:22 Craig Andrews
2022-01-29 21:19 Michał Górny
2021-09-14 14:15 Yixun Lan
2021-07-11 13:00 Brian Dolbec
2021-06-01 10:44 Sam James
2021-02-13 21:27 Brian Dolbec
2020-04-18 17:55 Craig Andrews
2020-02-26 12:18 Michał Górny
2019-07-26 22:21 Aaron Bauman
2019-06-16 15:01 David Seifert
2019-06-16 15:01 David Seifert
2019-06-16 15:01 David Seifert
2017-07-30 9:15 Michał Górny
2017-05-12 15:19 Manuel Rüger
2017-04-29 11:39 Jeroen Roovers
2017-03-11 17:07 Agostino Sarubbo
2017-03-04 14:02 Agostino Sarubbo
2017-02-17 6:03 Markus Meier
2017-02-16 20:34 Michael Weber
2017-02-14 15:39 Agostino Sarubbo
2017-02-14 14:52 Agostino Sarubbo
2016-12-24 21:54 Brian Dolbec
2016-10-09 7:47 Pacho Ramos
2016-02-22 0:43 Stephen Klimaszewski
2016-01-23 19:28 Brian Dolbec
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=1683092111.8da0d0ba21eef81ca711698918268ab721d1126a.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