From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sec-keys/openpgp-keys-libidn/
Date: Tue, 26 Jul 2022 02:05:47 +0000 (UTC) [thread overview]
Message-ID: <1658801138.c62083e18f6fde67a7a190f2a8bc2195903c13fb.sam@gentoo> (raw)
commit: c62083e18f6fde67a7a190f2a8bc2195903c13fb
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 26 02:05:38 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jul 26 02:05:38 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c62083e1
sec-keys/openpgp-keys-libidn: Stabilize 20220621 ALLARCHES, #860945
Signed-off-by: Sam James <sam <AT> gentoo.org>
sec-keys/openpgp-keys-libidn/openpgp-keys-libidn-20220621.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sec-keys/openpgp-keys-libidn/openpgp-keys-libidn-20220621.ebuild b/sec-keys/openpgp-keys-libidn/openpgp-keys-libidn-20220621.ebuild
index 1facef7db6e9..c75e2b42b797 100644
--- a/sec-keys/openpgp-keys-libidn/openpgp-keys-libidn-20220621.ebuild
+++ b/sec-keys/openpgp-keys-libidn/openpgp-keys-libidn-20220621.ebuild
@@ -15,7 +15,7 @@ S="${WORKDIR}"
LICENSE="public-domain"
SLOT="0"
-KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~loong ~m68k ~mips ~ppc ppc64 ~riscv ~s390 sparc x86"
+KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc x86"
src_install() {
local files=( ${A} )
next reply other threads:[~2022-07-26 2:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 2:05 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-08 14:48 [gentoo-commits] repo/gentoo:master commit in: sec-keys/openpgp-keys-libidn/ Michał Górny
2024-02-08 14:43 Michał Górny
2024-01-14 2:46 Sam James
2022-07-26 4:26 Sam James
2022-07-26 2:05 Sam James
2022-07-26 2:05 Sam James
2022-07-26 2:05 Sam James
2022-07-26 1:36 Sam James
2022-07-26 1:36 Sam James
2022-06-21 22:01 Sam James
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=1658801138.c62083e18f6fde67a7a190f2a8bc2195903c13fb.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