From: "Andrew Ammerlaan" <andrewammerlaan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/check-manifest/
Date: Fri, 10 Jun 2022 14:30:11 +0000 (UTC) [thread overview]
Message-ID: <1654871400.d5731755018dc3548022aa0592012c928b1973d3.andrewammerlaan@gentoo> (raw)
commit: d5731755018dc3548022aa0592012c928b1973d3
Author: Andrew Ammerlaan <andrewammerlaan <AT> gentoo <DOT> org>
AuthorDate: Fri Jun 10 14:08:57 2022 +0000
Commit: Andrew Ammerlaan <andrewammerlaan <AT> gentoo <DOT> org>
CommitDate: Fri Jun 10 14:30:00 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d5731755
dev-python/check-manifest: import from ::guru
Closes: https://bugs.gentoo.org/848147
Signed-off-by: Andrew Ammerlaan <andrewammerlaan <AT> gentoo.org>
dev-python/check-manifest/Manifest | 1 +
.../check-manifest/check-manifest-0.48.ebuild | 37 ++++++++++++++++++++++
dev-python/check-manifest/metadata.xml | 16 ++++++++++
3 files changed, 54 insertions(+)
diff --git a/dev-python/check-manifest/Manifest b/dev-python/check-manifest/Manifest
new file mode 100644
index 000000000000..3b26630be303
--- /dev/null
+++ b/dev-python/check-manifest/Manifest
@@ -0,0 +1 @@
+DIST check-manifest-0.48.tar.gz 34732 BLAKE2B 9142ec4b4fb4ea96662ae5f1335127b2adb2c148e29d287384335e4b15f82597451bd7cfde856e80c485e00de20bd5591551b0e0a8446870c57d7ea3eb658708 SHA512 79df1ef54e2af669ce08b87d3ca9eb58bc02c6541687be11b270a30f83d89982583a470aff2c6bde0454476b27258c268cabfbb0f90c1188212375d0f95328d9
diff --git a/dev-python/check-manifest/check-manifest-0.48.ebuild b/dev-python/check-manifest/check-manifest-0.48.ebuild
new file mode 100644
index 000000000000..2b989bb74fbb
--- /dev/null
+++ b/dev-python/check-manifest/check-manifest-0.48.ebuild
@@ -0,0 +1,37 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+PYTHON_COMPAT=( python3_{8..11} )
+DISTUTILS_USE_PEP517=setuptools
+inherit distutils-r1
+
+DESCRIPTION="Tool to check the completeness of MANIFEST.in for Python packages"
+HOMEPAGE="
+ https://github.com/mgedmin/check-manifest
+ https://pypi.org/project/check-manifest/
+"
+SRC_URI="https://github.com/mgedmin/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64"
+
+RDEPEND="
+ dev-python/build[${PYTHON_USEDEP}]
+ dev-python/tomli[${PYTHON_USEDEP}]
+"
+DEPEND="
+ ${RDEPEND}
+ test? (
+ dev-python/mock[${PYTHON_USEDEP}]
+ )
+"
+
+EPYTEST_DESELECT=(
+ # Need internet
+ tests.py::Tests::test_build_sdist_pep517_isolated
+)
+
+distutils_enable_tests pytest
diff --git a/dev-python/check-manifest/metadata.xml b/dev-python/check-manifest/metadata.xml
new file mode 100644
index 000000000000..5257512406a0
--- /dev/null
+++ b/dev-python/check-manifest/metadata.xml
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+
+<pkgmetadata>
+ <maintainer type="project">
+ <email>python@gentoo.org</email>
+ </maintainer>
+ <upstream>
+ <remote-id type="github">mgedmin/check-manifest</remote-id>
+ <remote-id type="pypi">check-manifest</remote-id>
+ </upstream>
+ <longdescription lang="en">
+ Are you a Python developer? Have you uploaded packages to the Python Package Index? Have you accidentally uploaded broken packages with some files missing? If so, check-manifest is for you.
+ </longdescription>
+ <stabilize-allarches/>
+</pkgmetadata>
next reply other threads:[~2022-06-10 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 14:30 Andrew Ammerlaan [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-18 7:18 [gentoo-commits] repo/gentoo:master commit in: dev-python/check-manifest/ Ulrich Müller
2022-10-12 19:22 Sam James
2022-12-06 6:02 Michał Górny
2023-05-27 9:44 Arthur Zamarin
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=1654871400.d5731755018dc3548022aa0592012c928b1973d3.andrewammerlaan@gentoo \
--to=andrewammerlaan@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