From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/sequoia-chameleon-gnupg/
Date: Tue, 25 Apr 2023 19:01:47 +0000 (UTC) [thread overview]
Message-ID: <1682449279.ab588b7660dc2e8d7da25594aa7fc393e37bdc1c.sam@gentoo> (raw)
commit: ab588b7660dc2e8d7da25594aa7fc393e37bdc1c
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Apr 25 19:01:19 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Apr 25 19:01:19 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ab588b76
app-crypt/sequoia-chameleon-gnupg: Keyword 0.2.0 arm64, #905014
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-crypt/sequoia-chameleon-gnupg/sequoia-chameleon-gnupg-0.2.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-crypt/sequoia-chameleon-gnupg/sequoia-chameleon-gnupg-0.2.0.ebuild b/app-crypt/sequoia-chameleon-gnupg/sequoia-chameleon-gnupg-0.2.0.ebuild
index 5b7c38538af6..8d540fb60c0f 100644
--- a/app-crypt/sequoia-chameleon-gnupg/sequoia-chameleon-gnupg-0.2.0.ebuild
+++ b/app-crypt/sequoia-chameleon-gnupg/sequoia-chameleon-gnupg-0.2.0.ebuild
@@ -306,7 +306,7 @@ LICENSE+="
|| ( GPL-2 GPL-3 LGPL-3 )
"
SLOT="0"
-KEYWORDS="~amd64"
+KEYWORDS="~amd64 ~arm64"
# See e.g. https://gitlab.com/sequoia-pgp/sequoia-chameleon-gnupg/-/issues/8
# Even though that's fixed as of >0.2.0, tests still completely fail inside
# Portage. Not yet sure why/how. They do better outside, although some fail
next reply other threads:[~2023-04-25 19:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 19:01 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-24 22:04 [gentoo-commits] repo/gentoo:master commit in: app-crypt/sequoia-chameleon-gnupg/ Sam James
2025-04-07 7:07 Sam James
2025-03-07 2:38 Sam James
2025-02-10 1:33 Sam James
2025-02-10 1:33 Sam James
2025-02-04 17:33 Florian Schmaus
2025-01-04 10:30 Florian Schmaus
2025-01-04 10:30 Florian Schmaus
2025-01-04 10:30 Florian Schmaus
2024-07-03 4:41 Sam James
2024-06-24 4:00 Sam James
2024-06-03 0:44 Sam James
2024-06-03 0:44 Sam James
2024-06-03 0:44 Sam James
2024-04-29 1:11 Sam James
2024-04-29 0:06 Sam James
2024-03-07 20:21 Sam James
2024-03-07 20:21 Sam James
2024-02-29 4:06 Sam James
2024-02-29 4:06 Sam James
2023-12-24 2:55 Sam James
2023-12-24 2:55 Sam James
2023-11-25 8:38 Sam James
2023-11-25 5:28 Sam James
2023-08-19 15:50 Sam James
2023-07-26 4:40 Sam James
2023-07-23 23:55 Sam James
2023-05-23 9:33 Sam James
2023-05-20 3:49 Sam James
2023-02-11 2:21 Sam James
2023-02-08 19:56 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=1682449279.ab588b7660dc2e8d7da25594aa7fc393e37bdc1c.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