From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/kernelshark/
Date: Sat, 3 Feb 2024 13:32:57 +0000 (UTC) [thread overview]
Message-ID: <1706967054.6b25d63c7a8e9c40de54de64ced904daa5f7674b.dlan@gentoo> (raw)
commit: 6b25d63c7a8e9c40de54de64ced904daa5f7674b
Author: Yixun Lan <dlan <AT> gentoo <DOT> org>
AuthorDate: Thu Feb 1 01:09:59 2024 +0000
Commit: Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Sat Feb 3 13:30:54 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6b25d63c
dev-util/kernelshark: fix libtracecmd dep
Closes: https://bugs.gentoo.org/909439
Signed-off-by: Yixun Lan <dlan <AT> gentoo.org>
.../{kernelshark-2.2.1.ebuild => kernelshark-2.2.1-r1.ebuild} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-util/kernelshark/kernelshark-2.2.1.ebuild b/dev-util/kernelshark/kernelshark-2.2.1-r1.ebuild
similarity index 95%
rename from dev-util/kernelshark/kernelshark-2.2.1.ebuild
rename to dev-util/kernelshark/kernelshark-2.2.1-r1.ebuild
index b90ab79d56d5..79925ca48471 100644
--- a/dev-util/kernelshark/kernelshark-2.2.1.ebuild
+++ b/dev-util/kernelshark/kernelshark-2.2.1-r1.ebuild
@@ -25,7 +25,7 @@ SLOT="0"
IUSE="custom-optimization doc"
DEPEND="
- >=dev-util/trace-cmd-3.0.2
+ || ( >=dev-libs/libtracecmd-1.1.2 <dev-util/trace-cmd-3.2 )
dev-libs/json-c:=
dev-qt/qtcore:5=
dev-qt/qtnetwork:5=
next reply other threads:[~2024-02-03 13:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 13:32 Yixun Lan [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-14 12:09 [gentoo-commits] repo/gentoo:master commit in: dev-util/kernelshark/ Yixun Lan
2025-01-13 17:12 Andreas Sturmlechner
2024-07-08 18:57 Yixun Lan
2024-02-04 4:19 Yixun Lan
2023-07-01 13:28 Yixun Lan
2023-01-28 15:25 Yixun Lan
2022-09-23 13:14 Yixun Lan
2022-09-23 13:14 Yixun Lan
2021-02-13 10:27 David Seifert
2020-05-14 22:25 Aaron Bauman
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=1706967054.6b25d63c7a8e9c40de54de64ced904daa5f7674b.dlan@gentoo \
--to=dlan@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