From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/blazesym_c/
Date: Tue, 29 Apr 2025 08:13:18 +0000 (UTC) [thread overview]
Message-ID: <1745914364.77c45a04fe796eb219f90e34d9d89d3ad1a12fdf.dlan@gentoo> (raw)
commit: 77c45a04fe796eb219f90e34d9d89d3ad1a12fdf
Author: Holger Hoffstätte <holger <AT> applied-asynchrony <DOT> com>
AuthorDate: Mon Apr 28 10:32:39 2025 +0000
Commit: Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Tue Apr 29 08:12:44 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=77c45a04
dev-libs/blazesym_c: address QA warning regarding LDFLAGS
Also clarify comment about test restrictions.
Closes: https://bugs.gentoo.org/954808
Closes: https://github.com/gentoo/gentoo/pull/41819
Signed-off-by: Holger Hoffstätte <holger <AT> applied-asynchrony.com>
Signed-off-by: Yixun Lan <dlan <AT> gentoo.org>
dev-libs/blazesym_c/blazesym_c-0.1.1.ebuild | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/dev-libs/blazesym_c/blazesym_c-0.1.1.ebuild b/dev-libs/blazesym_c/blazesym_c-0.1.1.ebuild
index 01d8f1357015..ef625fd38afd 100644
--- a/dev-libs/blazesym_c/blazesym_c-0.1.1.ebuild
+++ b/dev-libs/blazesym_c/blazesym_c-0.1.1.ebuild
@@ -38,13 +38,18 @@ LICENSE+="
SLOT="0"
KEYWORDS="~amd64"
-# many failures (WIP)
+# Currently suffers from (at least):
+# - problems with crate tarball
+# - hardcoded/hand-rolled multilib assumptions
+# - possibly sandbox
RESTRICT="test"
BDEPEND="
dev-util/cargo-c
"
+QA_FLAGS_IGNORED="usr/lib64/libblazesym_c.so.${PV}"
+
src_prepare() {
default
next reply other threads:[~2025-04-29 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 8:13 Yixun Lan [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-18 14:38 [gentoo-commits] repo/gentoo:master commit in: dev-libs/blazesym_c/ 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=1745914364.77c45a04fe796eb219f90e34d9d89d3ad1a12fdf.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