public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-testinfra/
Date: Fri, 11 Jun 2021 16:32:57 +0000 (UTC)	[thread overview]
Message-ID: <1623429168.ce21e3f6763f60f512de08415874ce8dd3de9159.marecki@gentoo> (raw)

commit:     ce21e3f6763f60f512de08415874ce8dd3de9159
Author:     Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Fri Jun 11 16:28:45 2021 +0000
Commit:     Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Fri Jun 11 16:32:48 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ce21e3f6

dev-python/pytest-testinfra: initial import

Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>

 dev-python/pytest-testinfra/Manifest               |  1 +
 dev-python/pytest-testinfra/metadata.xml           | 19 +++++++++++++
 .../pytest-testinfra/pytest-testinfra-6.3.0.ebuild | 32 ++++++++++++++++++++++
 3 files changed, 52 insertions(+)

diff --git a/dev-python/pytest-testinfra/Manifest b/dev-python/pytest-testinfra/Manifest
new file mode 100644
index 00000000000..37bc260fa2e
--- /dev/null
+++ b/dev-python/pytest-testinfra/Manifest
@@ -0,0 +1 @@
+DIST pytest-testinfra-6.3.0.tar.gz 76309 BLAKE2B 95b4a6ac5ea3c3db2afdd537209bfeb2c188ec7c7935b73e831733fbbf2540b8769d1187338b3b9c9da997cd653e800004e7199537d95530967cd73a15cb2c2e SHA512 ff0add6bdadac92f6f997a94734d69d39598bc8d1f7689a6b269e59bc886825fcf8a42968c2d34a9ad7e77ed0112bf4044afede8e0dca2bbddc76c9c5612ae92

diff --git a/dev-python/pytest-testinfra/metadata.xml b/dev-python/pytest-testinfra/metadata.xml
new file mode 100644
index 00000000000..75d52d73c62
--- /dev/null
+++ b/dev-python/pytest-testinfra/metadata.xml
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+	<longdescription>
+		With Testinfra you can write unit tests in Python to test actual state of your servers
+		configured by management tools like Salt, Ansible, Puppet, Chef and so on.
+
+		Testinfra aims to be a Serverspec equivalent in Python.
+	</longdescription>
+	<maintainer type="person">
+		<email>marecki@gentoo.org</email>
+		<name>Marek Szuba</name>
+	</maintainer>
+	<stabilize-allarches/>
+	<upstream>
+		<remote-id type="github">pytest-dev/pytest-testinfra</remote-id>
+		<remote-id type="pypi">pytest-testinfra</remote-id>
+	</upstream>
+</pkgmetadata>

diff --git a/dev-python/pytest-testinfra/pytest-testinfra-6.3.0.ebuild b/dev-python/pytest-testinfra/pytest-testinfra-6.3.0.ebuild
new file mode 100644
index 00000000000..8081571a974
--- /dev/null
+++ b/dev-python/pytest-testinfra/pytest-testinfra-6.3.0.ebuild
@@ -0,0 +1,32 @@
+# Copyright 1999-2021 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+PYTHON_COMPAT=( python3_{8..9} )
+
+inherit distutils-r1
+
+DESCRIPTION="Write unit tests in Python to test actual state of your servers"
+HOMEPAGE="https://github.com/pytest-dev/pytest-testinfra"
+SRC_URI="mirror://pypi/${P:0:1}/${PN}/${P}.tar.gz"
+
+LICENSE="Apache-2.0"
+SLOT="0"
+KEYWORDS="~amd64"
+
+RDEPEND="dev-python/pytest[${PYTHON_USEDEP}]"
+BDEPEND="dev-python/setuptools_scm[${PYTHON_USEDEP}]
+	test? (
+		app-admin/ansible[${PYTHON_USEDEP}]
+		app-admin/salt[${PYTHON_USEDEP}]
+		dev-python/paramiko[${PYTHON_USEDEP}]
+		dev-python/pywinrm[${PYTHON_USEDEP}]
+	)"
+
+distutils_enable_tests pytest
+
+pkg_postinst() {
+	elog "For the list of available connection back-ends and their dependencies,"
+	elog "please consult https://testinfra.readthedocs.io/en/latest/backends.html"
+}


             reply	other threads:[~2021-06-11 16:33 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11 16:32 Marek Szuba [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-15 13:30 [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-testinfra/ Marek Szuba
2021-07-01 11:02 Marek Szuba
2021-10-17  9:20 Michał Górny
2021-12-07 23:27 Michał Górny
2022-01-11 18:38 Marek Szuba
2022-02-11  9:42 Michał Górny
2022-03-26 22:31 Marek Szuba
2022-04-12 17:34 Michał Górny
2022-05-16 13:27 Michał Górny
2022-05-31  7:16 Jakov Smolić
2022-06-05  5:46 Michał Górny
2022-06-20  6:22 Michał Górny
2022-09-26  1:01 Marek Szuba
2022-11-23  0:00 Marek Szuba
2022-12-03  9:09 Michał Górny
2023-01-07 18:27 Arthur Zamarin
2023-01-08  5:06 Michał Górny
2023-01-10 14:15 Michał Górny
2023-02-24 21:19 Marek Szuba
2023-02-26 11:37 Marek Szuba
2023-03-17 15:23 Michał Górny
2023-05-20  5:34 Michał Górny
2023-05-22  5:53 Michał Górny
2023-06-27  9:08 Jakov Smolić
2023-06-27 11:36 Michał Górny
2023-08-25  9:49 Michał Górny
2023-09-25 18:31 Arthur Zamarin
2023-09-25 18:57 Michał Górny
2023-11-14  4:34 Michał Górny
2023-11-23 20:34 Arthur Zamarin
2023-11-24 19:17 Michał Górny
2023-12-09 14:58 Michał Górny
2023-12-09 15:13 Michał Górny
2024-02-15 12:19 Michał Górny
2024-02-27 15:43 Michał Górny
2024-03-06 17:37 Marek Szuba
2024-03-16 11:41 Arthur Zamarin
2024-03-16 17:06 Arthur Zamarin
2024-03-16 17:11 Michał Górny
2024-05-27  4:17 Michał Górny
2024-06-12  7:05 Arthur Zamarin
2024-06-12  7:42 Michał Górny

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=1623429168.ce21e3f6763f60f512de08415874ce8dd3de9159.marecki@gentoo \
    --to=marecki@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