From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-cpp/opentelemetry-cpp/
Date: Sun, 5 Nov 2023 19:19:21 +0000 (UTC) [thread overview]
Message-ID: <1699211944.916148a28d2ccf1e8bff979d3dc55ff764d4727b.arthurzam@gentoo> (raw)
commit: 916148a28d2ccf1e8bff979d3dc55ff764d4727b
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sun Nov 5 19:19:04 2023 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sun Nov 5 19:19:04 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=916148a2
dev-cpp/opentelemetry-cpp: Keyword 1.6.0 ppc64, #842642
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
dev-cpp/opentelemetry-cpp/opentelemetry-cpp-1.6.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-cpp/opentelemetry-cpp/opentelemetry-cpp-1.6.0.ebuild b/dev-cpp/opentelemetry-cpp/opentelemetry-cpp-1.6.0.ebuild
index 1cc3fa743214..44c3c51a3682 100644
--- a/dev-cpp/opentelemetry-cpp/opentelemetry-cpp-1.6.0.ebuild
+++ b/dev-cpp/opentelemetry-cpp/opentelemetry-cpp-1.6.0.ebuild
@@ -14,7 +14,7 @@ SRC_URI="https://github.com/open-telemetry/${PN}/archive/refs/tags/v${PV}.tar.gz
LICENSE="Apache-2.0"
SLOT="0"
-KEYWORDS="amd64 ~arm64"
+KEYWORDS="amd64 ~arm64 ~ppc64"
IUSE="+jaeger prometheus test"
RDEPEND="
next reply other threads:[~2023-11-05 19:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 19:19 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-01 12:52 [gentoo-commits] repo/gentoo:master commit in: dev-cpp/opentelemetry-cpp/ Sam James
2024-12-01 12:52 Sam James
2024-12-01 12:52 Sam James
2024-01-03 18:52 Arthur Zamarin
2023-05-01 1:43 Sam James
2022-08-19 18:31 Patrick McLean
2022-05-18 18:45 Patrick McLean
2022-05-05 16:03 Patrick McLean
2022-05-05 7:32 Arthur Zamarin
2022-05-04 22:53 Patrick McLean
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=1699211944.916148a28d2ccf1e8bff979d3dc55ff764d4727b.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