public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/readthedocs-sphinx-ext/
Date: Tue, 19 Dec 2023 17:26:01 +0000 (UTC)	[thread overview]
Message-ID: <1703006757.dd66609e05adaa59d8d0b88313092b7291e3b145.mgorny@gentoo> (raw)

commit:     dd66609e05adaa59d8d0b88313092b7291e3b145
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 19 17:09:33 2023 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Tue Dec 19 17:25:57 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dd66609e

dev-python/readthedocs-sphinx-ext: Bump to 2.2.5

Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>

 dev-python/readthedocs-sphinx-ext/Manifest         |  1 +
 .../readthedocs-sphinx-ext-2.2.5.ebuild            | 30 ++++++++++++++++++++++
 2 files changed, 31 insertions(+)

diff --git a/dev-python/readthedocs-sphinx-ext/Manifest b/dev-python/readthedocs-sphinx-ext/Manifest
index b935b3c6573f..5d3f6877e464 100644
--- a/dev-python/readthedocs-sphinx-ext/Manifest
+++ b/dev-python/readthedocs-sphinx-ext/Manifest
@@ -1,2 +1,3 @@
 DIST readthedocs-sphinx-ext-2.2.3.tar.gz 12176 BLAKE2B 9467e3d08baa15fe64ce0a718e922e4f8dc6c0bd76fd8a53f4bae66114bbd043bbcca71a2b7b152a162d7ca89b102668ccdc9ab9b0904e0caf2e0ff953fc489c SHA512 f8c9b2b62c73307906fc61a2dacc0c9079c1b81920718fbd2c60a45e22da7e581b9fa60aca83003081753603cb904187cae6075922a62616554c8fcc4c1d7991
 DIST readthedocs-sphinx-ext-2.2.4.tar.gz 12474 BLAKE2B 1911f2a161d38c89b96d194bc5eaa1d015f2a9ef1350e9f01d50a2f575f8486618ae79f12b3b6a15a61ffe85a0c6d9f1f1560fa663ba1faa6aeda916a6cc9f05 SHA512 010116cb842cbf0a389d7e94196bf6122422584a843ff549d96384a8424f12458aec6493e412e28c9158082ca624fa2ff8d8cbbfc7d7c3e7e61aa69bef40c4b2
+DIST readthedocs-sphinx-ext-2.2.5.tar.gz 12303 BLAKE2B 55e67a96b8e5c4fef9d0768a4e514da924969628349d210b1cba6d8167c288bb4b6792486a80176fb01df7f8889b3f7b59ff30cb4ea487943e4bfe0d6942488f SHA512 d096803bb3d065236502d790ddd9efbf281854177dee7043f8bf2292cb124aea636b0d036e23ea3f23643484faaf2fd5e1b8636a2ed7973674cf5d5584f39bf3

diff --git a/dev-python/readthedocs-sphinx-ext/readthedocs-sphinx-ext-2.2.5.ebuild b/dev-python/readthedocs-sphinx-ext/readthedocs-sphinx-ext-2.2.5.ebuild
new file mode 100644
index 000000000000..00dffbb4b59c
--- /dev/null
+++ b/dev-python/readthedocs-sphinx-ext/readthedocs-sphinx-ext-2.2.5.ebuild
@@ -0,0 +1,30 @@
+# Copyright 2020-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+DISTUTILS_USE_PEP517=setuptools
+PYPI_NO_NORMALIZE=1
+PYTHON_COMPAT=( python3_{10..12} pypy3 )
+
+inherit distutils-r1 pypi
+
+DESCRIPTION="Code specific for Read the Docs and Sphinx"
+HOMEPAGE="
+	https://github.com/readthedocs/readthedocs-sphinx-ext/
+	https://pypi.org/project/readthedocs-sphinx-ext/
+"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
+
+RDEPEND="
+	>=dev-python/jinja-2.9[${PYTHON_USEDEP}]
+	dev-python/requests[${PYTHON_USEDEP}]
+	dev-python/sphinx[${PYTHON_USEDEP}]
+"
+
+# unittest should be sufficient but tests are very verbose, so pytest's
+# output capture is most welcome
+distutils_enable_tests pytest


             reply	other threads:[~2023-12-19 17:26 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 17:26 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-31 22:09 [gentoo-commits] repo/gentoo:master commit in: dev-python/readthedocs-sphinx-ext/ Petr Vaněk
2024-01-06  9:54 Michał Górny
2024-01-06  9:50 Michał Górny
2023-12-14 13:58 Michał Górny
2023-10-28 15:23 Michał Górny
2023-10-27 19:32 Sam James
2023-09-27  5:56 Michał Górny
2023-07-10  1:47 Michał Górny
2023-07-09 16:51 Arthur Zamarin
2023-06-30  2:46 Michał Górny
2023-06-07  4:40 Michał Górny
2023-06-01 16:32 Arthur Zamarin
2023-06-01 16:32 Arthur Zamarin
2023-03-17 15:25 Michał Górny
2022-11-25 13:52 Michał Górny
2022-11-25 13:47 Arthur Zamarin
2022-10-26  4:03 Michał Górny
2022-10-22 15:58 Michał Górny
2022-10-22 15:52 Arthur Zamarin
2022-09-19  6:42 Michał Górny
2022-09-16  9:09 Arthur Zamarin
2022-08-27 10:11 WANG Xuerui
2022-07-02 12:15 Arthur Zamarin
2022-07-02 12:15 Arthur Zamarin
2022-06-13  8:23 Michał Górny
2022-06-02  6:42 Michał Górny
2022-05-25  7:12 Michał Górny
2022-05-12  7:13 Michał Górny
2022-04-15 15:15 Arthur Zamarin
2022-04-15 15:14 Arthur Zamarin
2022-03-16 10:06 Michał Górny
2021-09-26 22:28 James Le Cuirot
2021-06-04 12:23 Michał Górny
2021-04-21 19:25 Michał Górny
2021-04-21 18:55 Sam James
2021-03-18  9:12 Michał Górny
2021-02-19  8:58 Michał Górny
2021-02-19  2:54 Sam James
2021-01-20  8:26 Michał Górny
2021-01-06 10:00 Michał Górny
2020-12-13  0:16 Sam James
2020-11-08 21:45 Sam James
2020-11-02 14:48 Michał Górny
2020-11-02 11:59 Sam James
2020-10-03 12:16 Sergei Trofimovich
2020-08-19  0:55 Sam James
2020-07-24 14:31 Michał Górny
2020-07-24 14:31 Michał Górny
2020-07-13 20:57 Sam James
2020-07-11  9:16 Michał Górny
2020-07-11  9:16 Michał Górny
2020-07-10  6:30 Michał Górny
2020-07-09  8:41 Agostino Sarubbo
2020-07-09  8:27 Agostino Sarubbo
2020-07-09  8:16 Agostino Sarubbo
2020-07-09  8:04 Agostino Sarubbo
2020-06-17  6:56 Michał Górny
2020-05-27  7:03 Michał Górny
2020-05-04 11:49 Michał Górny
2020-04-22  8:15 Michał Górny
2020-04-22  8:15 Michał Górny
2020-04-04 10:52 Sergei Trofimovich
2020-04-04 10:52 Sergei Trofimovich
2020-04-04 10:30 Sergei Trofimovich
2020-04-04 10:30 Sergei Trofimovich
2020-03-29 21:21 Sergei Trofimovich
2020-03-29 21:21 Sergei Trofimovich
2020-03-16  4:10 Matt Turner
2020-03-16  4:10 Matt Turner
2020-03-14 18:14 Mikle Kolyada
2020-03-12 14:05 Mart Raudsepp
2020-03-11  7:21 Sergei Trofimovich
2020-03-11  7:21 Sergei Trofimovich
2020-03-05 18:06 Michał Górny
2020-03-03  7:01 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=1703006757.dd66609e05adaa59d8d0b88313092b7291e3b145.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