public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Georgy Yakovlev" <gyakovlev@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/reflink/
Date: Sun, 26 Jun 2022 10:57:26 +0000 (UTC)	[thread overview]
Message-ID: <1656241041.d70e7e9cf3c972c7a85be57a314f148790058035.gyakovlev@gentoo> (raw)

commit:     d70e7e9cf3c972c7a85be57a314f148790058035
Author:     Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 26 10:56:55 2022 +0000
Commit:     Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
CommitDate: Sun Jun 26 10:57:21 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d70e7e9c

dev-python/reflink: drop 0.2.1-r2

Signed-off-by: Georgy Yakovlev <gyakovlev <AT> gentoo.org>

 dev-python/reflink/reflink-0.2.1-r2.ebuild | 48 ------------------------------
 1 file changed, 48 deletions(-)

diff --git a/dev-python/reflink/reflink-0.2.1-r2.ebuild b/dev-python/reflink/reflink-0.2.1-r2.ebuild
deleted file mode 100644
index 11eb61de3fe4..000000000000
--- a/dev-python/reflink/reflink-0.2.1-r2.ebuild
+++ /dev/null
@@ -1,48 +0,0 @@
-# Copyright 2019-2022 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-
-DISTUTILS_USE_PEP517=setuptools
-PYTHON_COMPAT=( python3_{8..11} )
-DISTUTILS_IN_SOURCE_BUILD=1
-
-inherit distutils-r1
-
-DESCRIPTION="Python wrapper around the reflink system calls"
-HOMEPAGE="https://gitlab.com/rubdos/pyreflink"
-SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
-
-LICENSE="MIT"
-SLOT="0"
-KEYWORDS="~amd64 ~ppc64 ~x86"
-
-RDEPEND="virtual/python-cffi[${PYTHON_USEDEP}]"
-DEPEND="${RDEPEND}"
-BDEPEND="${RDEPEND}
-	test? ( sys-fs/btrfs-progs )
-"
-
-distutils_enable_sphinx docs
-distutils_enable_tests pytest
-
-python_prepare_all() {
-	sed -e 's|'\''pytest-runner'\'',\?||' -i setup.py || die
-	distutils-r1_python_prepare_all
-}
-
-python_test() {
-	local notestmsg="Tests need FEATURES='-usersandbox -userpriv -sandbox'"
-	if [[ ${EUID} != 0 ]]; then
-		ewarn "${notestmsg}"
-	elif
-		has sandbox ${FEATURES}; then
-			ewarn "${notestmsg}"
-	else
-		pushd "${BUILD_DIR}"/lib >/dev/null || die
-		# module import will fail with any other directory structure
-		cp -rv "${S}"/tests ./ || die
-		pytest -vv || die "Tests fail with ${EPYTHON}"
-		popd >/dev/null || die
-	fi
-}


             reply	other threads:[~2022-06-26 10:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-26 10:57 Georgy Yakovlev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-27 18:57 [gentoo-commits] repo/gentoo:master commit in: dev-python/reflink/ Michał Górny
2024-03-13 15:13 Michał Górny
2024-03-13 15:05 Arthur Zamarin
2024-02-24 10:26 Michał Górny
2024-02-14 17:25 Michał Górny
2024-02-14 17:25 Michał Górny
2023-06-11  9:21 Michał Górny
2023-03-16  4:07 Michał Górny
2022-11-04 18:23 Arthur Zamarin
2022-06-22 13:22 Agostino Sarubbo
2022-06-21  5:35 Sam James
2022-06-16  8:09 Michał Górny
2022-05-29 18:38 Arthur Zamarin
2022-05-29 18:38 Arthur Zamarin
2022-02-13 22:59 Jakov Smolić
2021-04-18  0:36 Georgy Yakovlev
2020-06-09  3:20 Georgy Yakovlev
2020-02-21  8:55 Georgy Yakovlev
2019-01-27 23:29 Georgy Yakovlev

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=1656241041.d70e7e9cf3c972c7a85be57a314f148790058035.gyakovlev@gentoo \
    --to=gyakovlev@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