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: Wed, 20 Jan 2021 08:26:52 +0000 (UTC)	[thread overview]
Message-ID: <1611131205.b1a010babf62cf1c224941802f7d395f766912e0.mgorny@gentoo> (raw)

commit:     b1a010babf62cf1c224941802f7d395f766912e0
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed Jan 20 08:13:40 2021 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Wed Jan 20 08:26:45 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b1a010ba

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

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

 dev-python/readthedocs-sphinx-ext/Manifest         |  1 +
 .../readthedocs-sphinx-ext-2.1.3.ebuild            | 27 ++++++++++++++++++++++
 2 files changed, 28 insertions(+)

diff --git a/dev-python/readthedocs-sphinx-ext/Manifest b/dev-python/readthedocs-sphinx-ext/Manifest
index c1383fc5248..f6457656af1 100644
--- a/dev-python/readthedocs-sphinx-ext/Manifest
+++ b/dev-python/readthedocs-sphinx-ext/Manifest
@@ -1,2 +1,3 @@
 DIST readthedocs-sphinx-ext-2.1.1.tar.gz 10181 BLAKE2B 01ca34befd0f18bb747d7f843e0cc394e19db4fe471f2bb21617b6dbdf4c1ad9721047185561f9bfbd8f770e1fefd5b560e65d7c5e2675c1bc8d74e08252eeb1 SHA512 5594e375133477ecdc1d22a78c0d4dac73c5e8c1715f4309a9674497ef860b07e8872bb4ba471fbffacd8bd22bc49741b8df54ad9ca9bb474acd9cdee72c8969
 DIST readthedocs-sphinx-ext-2.1.2.tar.gz 11709 BLAKE2B 9386d9c849c4287a0f52ce054e33d22afed0426b5d775a03c90b7c18021f2a2a9429334dc0231ec8d28d3b4437dcf4e3faf57a0c1e46cfb4690893b96560fa3a SHA512 c1fa8a2c1b1d50aa5039c0592a0960b1162c31f58769754a7fdbe4d85557428f3e0a3a509012077210d30d79a28463ab0624855036ffb45d0977e9e0e666622a
+DIST readthedocs-sphinx-ext-2.1.3.tar.gz 12261 BLAKE2B 3121b75c2a157a61727f4bc5b15b7a5d0aa23a177593fd7208d558de4ea9d89c48c788a843af833ab9dc79b05baa32231086ca6e4ea4c69ba793fb5001becb12 SHA512 f9b03de7a5ef8e6707960cb05b1be8115a55292820fe3fd43efc6d7843b9e55c8c537a53653967e1879ff27c5856ca66f145fc6e8f98891fc1f2682e425e2faf

diff --git a/dev-python/readthedocs-sphinx-ext/readthedocs-sphinx-ext-2.1.3.ebuild b/dev-python/readthedocs-sphinx-ext/readthedocs-sphinx-ext-2.1.3.ebuild
new file mode 100644
index 00000000000..68b9817de11
--- /dev/null
+++ b/dev-python/readthedocs-sphinx-ext/readthedocs-sphinx-ext-2.1.3.ebuild
@@ -0,0 +1,27 @@
+# Copyright 2020-2021 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+PYTHON_COMPAT=( python3_{7..9} pypy3 )
+inherit distutils-r1
+
+DESCRIPTION="Code specific for Read the Docs and Sphinx"
+HOMEPAGE="https://github.com/readthedocs/readthedocs-sphinx-ext"
+SRC_URI="mirror://pypi/${PN::1}/${PN}/${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
+
+RDEPEND="
+	>=dev-python/jinja-2.9[${PYTHON_USEDEP}]
+	dev-python/requests[${PYTHON_USEDEP}]"
+PDEPEND="
+	dev-python/sphinx[${PYTHON_USEDEP}]"
+BDEPEND="
+	test? ( ${PDEPEND} )"
+
+# unittest should be sufficient but tests are very verbose, so pytest's
+# output capture is most welcome
+distutils_enable_tests pytest


             reply	other threads:[~2021-01-20  8:26 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20  8:26 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-20 10:20 [gentoo-commits] repo/gentoo:master commit in: dev-python/readthedocs-sphinx-ext/ Michał Górny
2024-05-31 22:09 Petr Vaněk
2024-01-06  9:54 Michał Górny
2024-01-06  9:50 Michał Górny
2023-12-19 17:26 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-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=1611131205.b1a010babf62cf1c224941802f7d395f766912e0.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