From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-arch/csnappy/
Date: Mon, 20 Jun 2022 17:57:04 +0000 (UTC) [thread overview]
Message-ID: <1655747814.86d782a4686573a9c07ddb3bac6140d0d2cba38e.arthurzam@gentoo> (raw)
commit: 86d782a4686573a9c07ddb3bac6140d0d2cba38e
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 20 17:56:54 2022 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Mon Jun 20 17:56:54 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=86d782a4
app-arch/csnappy: Keyword 0_pre20220804 sparc, #849581
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
app-arch/csnappy/csnappy-0_pre20220804.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-arch/csnappy/csnappy-0_pre20220804.ebuild b/app-arch/csnappy/csnappy-0_pre20220804.ebuild
index 2355abb6c39a..d56db9277a1b 100644
--- a/app-arch/csnappy/csnappy-0_pre20220804.ebuild
+++ b/app-arch/csnappy/csnappy-0_pre20220804.ebuild
@@ -16,7 +16,7 @@ S="${WORKDIR}"/${PN}-${MY_COMMIT}
LICENSE="BSD"
# 0/${PV} b/c of the SONAME situation (see below).
SLOT="0/${PV}"
-KEYWORDS="~amd64 ~ppc ~ppc64 ~x86"
+KEYWORDS="~amd64 ~ppc ~ppc64 ~sparc ~x86"
# https://github.com/zeevt/csnappy/issues/33
# No SONAME yet.
next reply other threads:[~2022-06-20 17:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 17:57 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 14:09 [gentoo-commits] repo/gentoo:master commit in: app-arch/csnappy/ Arthur Zamarin
2023-01-02 5:37 Sam James
2023-01-02 5:37 Sam James
2023-01-02 5:37 Sam James
2023-01-02 5:37 Sam James
2022-06-28 15:44 Arthur Zamarin
2022-06-09 19:39 Arthur Zamarin
2022-06-06 7:38 Florian Schmaus
2022-06-05 12:47 Jakov Smolić
2022-06-04 20:00 Jakov Smolić
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=1655747814.86d782a4686573a9c07ddb3bac6140d0d2cba38e.arthurzam@gentoo \
--to=arthurzam@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