From: "Luca Barbato" <lu_zero@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/uutils/
Date: Thu, 28 Jul 2022 07:26:30 +0000 (UTC) [thread overview]
Message-ID: <1658993093.97bb4cb5ee3ecc34c2d55c9d83aa02b8021d9c46.lu_zero@gentoo> (raw)
commit: 97bb4cb5ee3ecc34c2d55c9d83aa02b8021d9c46
Author: Luca Barbato <lu_zero <AT> gentoo <DOT> org>
AuthorDate: Thu Jul 28 07:21:09 2022 +0000
Commit: Luca Barbato <lu_zero <AT> gentoo <DOT> org>
CommitDate: Thu Jul 28 07:24:53 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=97bb4cb5
sys-apps/uutils: add QA_FLAGS_IGNORED
A rust application normally does not have C components.
Signed-off-by: Luca Barbato <lu_zero <AT> gentoo.org>
sys-apps/uutils/uutils-0.0.14.ebuild | 1 +
1 file changed, 1 insertion(+)
diff --git a/sys-apps/uutils/uutils-0.0.14.ebuild b/sys-apps/uutils/uutils-0.0.14.ebuild
index 13b3ea88d8e8..8f7dcc97f333 100644
--- a/sys-apps/uutils/uutils-0.0.14.ebuild
+++ b/sys-apps/uutils/uutils-0.0.14.ebuild
@@ -253,6 +253,7 @@ SRC_URI+=" $(cargo_crate_uris)"
# License set may be more restrictive as OR is not respected
# use cargo-license for a more accurate license picture
LICENSE="Apache-2.0 Apache-2.0-with-LLVM-exceptions BSD BSD-2 CC0-1.0 ISC MIT Unlicense"
+QA_FLAGS_IGNORED=".*"
BDEPEND=">=virtual/rust-1.56.0"
next reply other threads:[~2022-07-28 7:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 7:26 Luca Barbato [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-22 8:46 [gentoo-commits] repo/gentoo:master commit in: sys-apps/uutils/ Sam James
2023-02-08 18:05 Sam James
2023-02-08 18:05 Sam James
2022-08-24 1:43 Sam James
2022-07-31 9:29 Luca Barbato
2022-07-31 9:29 Luca Barbato
2022-07-27 20:47 Luca Barbato
2022-04-04 12:07 Luca Barbato
2022-02-01 10:27 Luca Barbato
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=1658993093.97bb4cb5ee3ecc34c2d55c9d83aa02b8021d9c46.lu_zero@gentoo \
--to=lu_zero@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