From: "Sergey Torokhov" <torokhov-s-a@yandex.ru>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-python/markdown-include/
Date: Fri, 9 Dec 2022 17:41:39 +0000 (UTC) [thread overview]
Message-ID: <1670607635.c41e51a1a8ba58825a325e8140cb5f957a24751d.SergeyTorokhov@gentoo> (raw)
commit: c41e51a1a8ba58825a325e8140cb5f957a24751d
Author: Sergey Torokhov <torokhov-s-a <AT> yandex <DOT> ru>
AuthorDate: Fri Dec 9 17:40:35 2022 +0000
Commit: Sergey Torokhov <torokhov-s-a <AT> yandex <DOT> ru>
CommitDate: Fri Dec 9 17:40:35 2022 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=c41e51a1
dev-python/markdown-include: fix QA setuptools warning
Closes: https://bugs.gentoo.org/800161
Signed-off-by: Sergey Torokhov <torokhov-s-a <AT> yandex.ru>
dev-python/markdown-include/markdown-include-0.7.0.ebuild | 6 ++++++
dev-python/markdown-include/markdown-include-0.8.0.ebuild | 7 ++++++-
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/dev-python/markdown-include/markdown-include-0.7.0.ebuild b/dev-python/markdown-include/markdown-include-0.7.0.ebuild
index 8216f4438..2d4dbe8d5 100644
--- a/dev-python/markdown-include/markdown-include-0.7.0.ebuild
+++ b/dev-python/markdown-include/markdown-include-0.7.0.ebuild
@@ -3,6 +3,7 @@
EAPI=8
+DISTUTILS_USE_PEP517=setuptools
PYTHON_COMPAT=( python3_{8..10} )
inherit distutils-r1
@@ -16,3 +17,8 @@ KEYWORDS="~amd64 ~x86"
SLOT="0"
RDEPEND=">=dev-python/markdown-3.4[${PYTHON_USEDEP}]"
+
+src_prepare() {
+ sed -i "s/description-file/description_file/" setup.cfg || die
+ distutils-r1_src_prepare
+}
diff --git a/dev-python/markdown-include/markdown-include-0.8.0.ebuild b/dev-python/markdown-include/markdown-include-0.8.0.ebuild
index cb920be08..99f299300 100644
--- a/dev-python/markdown-include/markdown-include-0.8.0.ebuild
+++ b/dev-python/markdown-include/markdown-include-0.8.0.ebuild
@@ -3,7 +3,7 @@
EAPI=8
-#DISTUTILS_USE_PEP517=setuptools
+DISTUTILS_USE_PEP517=setuptools
PYTHON_COMPAT=( python3_{8..11} )
inherit distutils-r1
@@ -17,3 +17,8 @@ KEYWORDS="~amd64 ~x86"
SLOT="0"
RDEPEND=">=dev-python/markdown-3.4[${PYTHON_USEDEP}]"
+
+src_prepare() {
+ sed -i "s/description-file/description_file/" setup.cfg || die
+ distutils-r1_src_prepare
+}
next reply other threads:[~2022-12-09 17:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 17:41 Sergey Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-09 2:00 [gentoo-commits] repo/proj/guru:dev commit in: dev-python/markdown-include/ Anna Vyalkova
2023-03-18 12:07 Sergey Torokhov
2023-03-17 13:10 Anna Vyalkova
2023-02-26 22:31 Sergey Torokhov
2023-01-19 0:11 Sergey Torokhov
2022-12-09 17:46 Sergey Torokhov
2022-12-03 16:22 Sergey Torokhov
2022-10-28 21:46 Sergey Torokhov
2022-08-02 22:11 Sergey Torokhov
2022-02-23 12:13 Sergey Torokhov
2021-09-06 19:50 Sergey Torokhov
2021-05-24 11:06 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2021-05-24 10:01 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-11-20 16:03 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-11-20 16:03 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-04-28 17:30 Andrew Ammerlaan
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=1670607635.c41e51a1a8ba58825a325e8140cb5f957a24751d.SergeyTorokhov@gentoo \
--to=torokhov-s-a@yandex.ru \
--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