public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Florian Schmaus" <flow@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: dev-python/cryptg/
Date: Tue, 24 Jan 2023 09:10:54 +0000 (UTC)	[thread overview]
Message-ID: <1674500240.62f9449a5a10b57c79244f3d96aec27d9716cf53.flow@gentoo> (raw)

commit:     62f9449a5a10b57c79244f3d96aec27d9716cf53
Author:     Julien Roy <julien <AT> jroy <DOT> ca>
AuthorDate: Mon Jan 23 18:57:20 2023 +0000
Commit:     Florian Schmaus <flow <AT> gentoo <DOT> org>
CommitDate: Mon Jan 23 18:57:20 2023 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=62f9449a

dev-python/cryptg: update QA_FLAGS_IGNORED

Closes: https://bugs.gentoo.org/891731
Closes: https://bugs.gentoo.org/891733
Signed-off-by: Julien Roy <julien <AT> jroy.ca>

 dev-python/cryptg/cryptg-0.4.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/cryptg/cryptg-0.4.ebuild b/dev-python/cryptg/cryptg-0.4.ebuild
index 82d9baee4..a25b13f6b 100644
--- a/dev-python/cryptg/cryptg-0.4.ebuild
+++ b/dev-python/cryptg/cryptg-0.4.ebuild
@@ -88,4 +88,4 @@ BDEPEND="dev-python/setuptools-rust"
 
 # rust does not use *FLAGS from make.conf, silence portage warning
 # update with proper path to binaries this crate installs, omit leading /
-QA_FLAGS_IGNORED="usr/bin/${PN}"
+QA_FLAGS_IGNORED="usr/lib/python3\..*/site-packages/cryptg/cryptg.cpython-.*.so"


             reply	other threads:[~2023-01-24  9:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24  9:10 Florian Schmaus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-29 22:14 [gentoo-commits] repo/proj/guru:master commit in: dev-python/cryptg/ David Roman
2024-10-29 10:53 David Roman
2024-10-22 15:55 David Roman
2024-04-13 17:09 [gentoo-commits] repo/proj/guru:dev " Julien Roy
2024-04-13 17:15 ` [gentoo-commits] repo/proj/guru:master " Julien Roy
2023-01-22  8:21 Viorel Munteanu
2023-01-22  8:21 Viorel Munteanu

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=1674500240.62f9449a5a10b57c79244f3d96aec27d9716cf53.flow@gentoo \
    --to=flow@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