public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/adblock/
Date: Fri, 14 Oct 2022 11:57:03 +0000 (UTC)	[thread overview]
Message-ID: <1665748599.40a9c7fd01f15066f6b3f091cdb4367cc511c732.ionen@gentoo> (raw)

commit:     40a9c7fd01f15066f6b3f091cdb4367cc511c732
Author:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Fri Oct 14 11:20:04 2022 +0000
Commit:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Fri Oct 14 11:56:39 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=40a9c7fd

dev-python/adblock: skip test using dev-python/toml

Deprecated and test is intended for upstream, checking that the
changelog's version matches Cargo.toml doesn't mean much here.

Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>

 dev-python/adblock/adblock-0.6.0.ebuild | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/dev-python/adblock/adblock-0.6.0.ebuild b/dev-python/adblock/adblock-0.6.0.ebuild
index 517d704e4f5e..eb67379a38c4 100644
--- a/dev-python/adblock/adblock-0.6.0.ebuild
+++ b/dev-python/adblock/adblock-0.6.0.ebuild
@@ -83,18 +83,22 @@ LICENSE="Apache-2.0 Apache-2.0-with-LLVM-exceptions MIT MPL-2.0"
 SLOT="0"
 KEYWORDS="amd64 ~arm64 ~x86"
 
-BDEPEND="test? ( dev-python/toml[${PYTHON_USEDEP}] )"
-
 distutils_enable_tests pytest
 
 QA_FLAGS_IGNORED=".*/adblock.*.so"
 
 DOCS=( CHANGELOG.md README.md )
 
+EPYTEST_IGNORE=(
+	# not very meaningful here (e.g. validates changelog),
+	# and needs the deprecated dev-python/toml
+	tests/test_metadata.py
+)
+
 src_compile() {
 	distutils-r1_src_compile
 
-	# tests try to find Cargo.toml + adblock/adblock.pyi in current
-	# directory but will fail if pytest finds init in ./adblock
+	# prevent pytest from using ./adblock that lack the built module
+	# but the keep directory given tests check ./adblock/adblock.pyi
 	rm adblock/__init__.py || die
 }


             reply	other threads:[~2022-10-14 11:57 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 11:57 Ionen Wolkens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-14 20:29 [gentoo-commits] repo/gentoo:master commit in: dev-python/adblock/ Ionen Wolkens
2024-05-11 11:35 Ionen Wolkens
2023-08-06  7:53 Ionen Wolkens
2023-06-20  3:11 Ionen Wolkens
2023-06-18 18:47 Michał Górny
2023-05-27 15:55 Ionen Wolkens
2023-04-22  6:53 Ionen Wolkens
2022-08-07 13:59 Ionen Wolkens
2022-08-07 13:59 Ionen Wolkens
2022-07-18  0:22 Ionen Wolkens
2022-06-16 13:59 Ionen Wolkens
2022-06-02 15:07 Ionen Wolkens
2022-05-16 18:40 Ionen Wolkens
2022-05-16 18:40 Ionen Wolkens
2022-05-16  6:45 Ionen Wolkens
2022-04-25 12:11 Michał Górny
2022-03-14 11:43 Ionen Wolkens
2022-03-14 11:43 Ionen Wolkens
2022-03-01 13:57 Ionen Wolkens
2022-01-17 10:18 Ionen Wolkens
2022-01-14  9:58 Ionen Wolkens
2021-12-16 19:11 Ionen Wolkens
2021-12-16 19:11 Ionen Wolkens
2021-12-04  0:44 Ionen Wolkens
2021-10-22 14:35 Agostino Sarubbo
2021-10-19  0:12 Sam James
2021-10-15 15:53 Ionen Wolkens
2021-10-15 15:53 Ionen Wolkens
2021-10-15 15:53 Ionen Wolkens
2021-10-15 15:53 Ionen Wolkens
2021-08-14 21:01 Michał Górny
2021-07-20 16:01 Stefan Strogin
2021-07-18 15:08 Stefan Strogin
2021-06-22 21:37 Stefan Strogin

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=1665748599.40a9c7fd01f15066f6b3f091cdb4367cc511c732.ionen@gentoo \
    --to=ionen@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