From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/openapi-schema-validator/
Date: Sun, 5 Feb 2023 17:07:10 +0000 (UTC) [thread overview]
Message-ID: <1675616824.a8e16cc8ecc3b52ff06bd47e0b3353ff1a6036f2.mgorny@gentoo> (raw)
commit: a8e16cc8ecc3b52ff06bd47e0b3353ff1a6036f2
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 5 16:53:00 2023 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Feb 5 17:07:04 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a8e16cc8
dev-python/openapi-schema-validator: Bump to 0.4.3
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
dev-python/openapi-schema-validator/Manifest | 1 +
.../openapi-schema-validator-0.4.3.ebuild | 35 ++++++++++++++++++++++
2 files changed, 36 insertions(+)
diff --git a/dev-python/openapi-schema-validator/Manifest b/dev-python/openapi-schema-validator/Manifest
index 5bf68a4c9a6e..0d377cab10a4 100644
--- a/dev-python/openapi-schema-validator/Manifest
+++ b/dev-python/openapi-schema-validator/Manifest
@@ -3,3 +3,4 @@ DIST openapi-schema-validator-0.3.4.gh.tar.gz 16593 BLAKE2B 17882dff25d1bed05efa
DIST openapi-schema-validator-0.4.0.gh.tar.gz 17070 BLAKE2B 199476dd660ab3493fe9805dc915c42f05b2bc5ca0f1f9728aa1e5afe5a923e3f84d82511572e353ab19c15b3094460dcfbde5ef1d96ca834c1da24314223046 SHA512 ce61c112c528bac022e3feb959bfe5adbac000ec0b4956f678bf61f66efdbf3a5cf912a4dfa1512858b497fdadaf533532f5a580f28f6ceea831e6b5ac98d85e
DIST openapi-schema-validator-0.4.1.gh.tar.gz 17478 BLAKE2B 0c215589eb72f97205c565bf7cfc77096dd9cf2a7d05d2ea7946fcbc3c8c9acb5702635f6cfe520993139ce9713c426f01b98d34b3c962ac918989f7d87f22c9 SHA512 e437309a6e741eaefa6b49bb038bd5976288bd6559fc6957d7029d9c0fed36ee368ac5fb26133a0fe54366da77ec649b5e44eb6a7926d9d5c49573afdfa3309b
DIST openapi-schema-validator-0.4.2.gh.tar.gz 16785 BLAKE2B 9b1a301711087c8ff1d04ed3988ed8c7004088f8404ff103fee849b2f6f40e7492dd2daf0f6e009dcb5245cf33553bcfa4c441b66f0cbe98a7046f8bf4573ed9 SHA512 494c420d973dbe6b2b21181143f6bb16f7d4de4934eaae046fbe3bd625ab99bb4860e5c4806e01290ea701970bde741ccb6a506ddff1775b2f1b3364f4cad06e
+DIST openapi-schema-validator-0.4.3.gh.tar.gz 30639 BLAKE2B 370e3cc4e6c9892912dc77114ca867752f46afd1555f91a3721f41a9c4516fdffc0416f2f1028f4717ca8cc1a1ef2ec47607b7ef2b6578a0b01afb8ddb6660c8 SHA512 a930ecafe2e4c1d4d021a71fe9b8f35c496320e5c5198e2ccb57d82e01570430c4904cae7bc44578bc95be63cf5c709c5bef1d96014c3a66fca3b4495c5e455c
diff --git a/dev-python/openapi-schema-validator/openapi-schema-validator-0.4.3.ebuild b/dev-python/openapi-schema-validator/openapi-schema-validator-0.4.3.ebuild
new file mode 100644
index 000000000000..3c2a9d37941c
--- /dev/null
+++ b/dev-python/openapi-schema-validator/openapi-schema-validator-0.4.3.ebuild
@@ -0,0 +1,35 @@
+# Copyright 2022-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+DISTUTILS_USE_PEP517=poetry
+PYTHON_COMPAT=( pypy3 python3_{9..11} )
+
+inherit distutils-r1
+
+DESCRIPTION="OpenAPI schema validation for Python"
+HOMEPAGE="
+ https://github.com/p1c2u/openapi-schema-validator/
+ https://pypi.org/project/openapi-schema-validator/
+"
+SRC_URI="
+ https://github.com/p1c2u/openapi-schema-validator/archive/${PV}.tar.gz
+ -> ${P}.gh.tar.gz
+"
+
+LICENSE="BSD"
+SLOT="0"
+KEYWORDS="~amd64 ~arm ~arm64 ~ppc64 ~riscv ~x86"
+
+RDEPEND="
+ >=dev-python/jsonschema-4.0.0[${PYTHON_USEDEP}]
+ dev-python/rfc3339-validator[${PYTHON_USEDEP}]
+"
+
+distutils_enable_tests pytest
+
+src_prepare() {
+ sed -e '/--cov/d' -i pyproject.toml || die
+ distutils-r1_src_prepare
+}
next reply other threads:[~2023-02-05 17:07 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 17:07 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-27 21:01 [gentoo-commits] repo/gentoo:master commit in: dev-python/openapi-schema-validator/ Michał Górny
2025-01-25 10:05 Arthur Zamarin
2025-01-10 20:43 Michał Górny
2024-10-09 6:31 Michał Górny
2024-06-16 8:12 Petr Vaněk
2023-10-15 17:27 Michał Górny
2023-10-14 16:52 Arthur Zamarin
2023-10-05 13:56 Michał Górny
2023-09-21 5:28 Michał Górny
2023-09-14 5:27 WANG Xuerui
2023-09-10 5:27 WANG Xuerui
2023-08-13 16:10 Arthur Zamarin
2023-08-13 6:37 Joonas Niilola
2023-07-09 14:36 Michał Górny
2023-06-13 5:51 Michał Górny
2023-05-27 19:21 Arthur Zamarin
2023-04-22 16:18 Michał Górny
2023-04-22 11:31 Sam James
2023-03-17 13:33 Michał Górny
2023-03-11 9:53 Michał Górny
2023-03-11 9:53 Michał Górny
2023-03-11 8:34 Arthur Zamarin
2023-02-16 14:13 Michał Górny
2023-02-16 5:22 Sam James
2023-01-31 11:22 Michał Górny
2023-01-25 7:55 Michał Górny
2023-01-12 6:14 Michał Górny
2022-10-07 20:31 Michał Górny
2022-10-07 20:19 Sam James
2022-09-26 6:15 Michał Górny
2022-09-26 6:15 Michał Górny
2022-09-25 23:58 Sam James
2022-09-22 11:01 Michał Górny
2022-08-26 16:33 Arthur Zamarin
[not found] <1656147640.2230ccebb1ced4b41f51ffff9fe68d2fd498c769.ago@gentoo>
2022-06-25 9:01 ` Agostino Sarubbo
2022-06-25 8:54 Agostino Sarubbo
2022-06-24 5:16 Michał Górny
2022-05-24 19:03 Jakov Smolić
2022-05-24 19:03 Jakov Smolić
2022-05-24 17:06 Jakov Smolić
2022-05-24 16:52 Jakov Smolić
2022-05-24 16:52 Jakov Smolić
2022-05-24 6:16 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=1675616824.a8e16cc8ecc3b52ff06bd47e0b3353ff1a6036f2.mgorny@gentoo \
--to=mgorny@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