From: "Matt Turner" <mattst88@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/jedi/
Date: Fri, 17 Jul 2020 04:18:53 +0000 (UTC) [thread overview]
Message-ID: <1594959500.2a5c256d844538978770bb4197699c48c1c851b4.mattst88@gentoo> (raw)
commit: 2a5c256d844538978770bb4197699c48c1c851b4
Author: Florian Schmaus <flo <AT> geekplace <DOT> eu>
AuthorDate: Tue Jun 2 08:48:43 2020 +0000
Commit: Matt Turner <mattst88 <AT> gentoo <DOT> org>
CommitDate: Fri Jul 17 04:18:20 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2a5c256d
dev-python/jedi: correct parso dependency
Jedi 0.17.1 requires parso >= 0.7.0.
Closes: https://bugs.gentoo.org/725984
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Florian Schmaus <flo <AT> geekplace.eu>
Closes: https://github.com/gentoo/gentoo/pull/16048
Signed-off-by: Matt Turner <mattst88 <AT> gentoo.org>
dev-python/jedi/{jedi-0.17.1.ebuild => jedi-0.17.1-r1.ebuild} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/jedi/jedi-0.17.1.ebuild b/dev-python/jedi/jedi-0.17.1-r1.ebuild
similarity index 97%
rename from dev-python/jedi/jedi-0.17.1.ebuild
rename to dev-python/jedi/jedi-0.17.1-r1.ebuild
index 00e52e0a540..59126ef7f00 100644
--- a/dev-python/jedi/jedi-0.17.1.ebuild
+++ b/dev-python/jedi/jedi-0.17.1-r1.ebuild
@@ -25,7 +25,7 @@ LICENSE="MIT
SLOT="0"
KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~ppc64 ~x86"
-RDEPEND=">=dev-python/parso-0.5.2[${PYTHON_USEDEP}]"
+RDEPEND=">=dev-python/parso-0.7.0[${PYTHON_USEDEP}]"
distutils_enable_sphinx docs \
dev-python/sphinx_rtd_theme
next reply other threads:[~2020-07-17 4:18 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 4:18 Matt Turner [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-08 9:36 [gentoo-commits] repo/gentoo:master commit in: dev-python/jedi/ Sam James
2023-11-16 16:44 Michał Górny
2023-11-05 20:58 Michał Górny
2023-11-05 19:10 Arthur Zamarin
2023-10-02 18:35 Arthur Zamarin
2023-08-31 5:13 Michał Górny
2023-08-31 4:21 Sam James
2023-07-30 17:51 Michał Górny
2023-01-07 18:36 Arthur Zamarin
2022-11-22 6:27 Arthur Zamarin
2022-11-06 7:59 Michał Górny
2022-11-06 7:24 Sam James
2022-05-27 19:45 Michał Górny
2022-05-27 9:07 Jakov Smolić
2022-04-25 12:11 Michał Górny
2022-04-25 12:11 Michał Górny
2022-04-25 12:11 Michał Górny
2021-09-05 1:18 Sam James
2021-09-05 1:18 Sam James
2021-08-26 3:00 Sam James
2021-08-24 23:21 Sam James
2021-08-24 18:58 Arthur Zamarin
2021-08-20 23:51 Sam James
2021-08-20 6:00 Agostino Sarubbo
2021-08-20 5:59 Agostino Sarubbo
2021-08-15 19:51 Sam James
2021-08-15 7:42 Michał Górny
2021-08-04 10:23 Sergei Trofimovich
2021-07-25 15:26 Sergei Trofimovich
2021-07-25 3:16 Matt Turner
2021-07-25 3:16 Matt Turner
2021-07-01 14:42 Michał Górny
2021-07-01 8:43 Michał Górny
2021-06-30 12:21 Michał Górny
2021-06-20 1:55 Sam James
2021-01-27 9:00 Michał Górny
2021-01-27 3:06 Sam James
2020-12-25 18:49 Michał Górny
2020-08-20 11:39 Michał Górny
2020-08-19 9:01 Sam James
2020-08-02 8:26 Michał Górny
2020-07-19 18:14 Michał Górny
2020-07-09 10:39 Michał Górny
2020-06-20 7:47 Michał Górny
2020-06-03 17:27 Michał Górny
2020-06-02 12:01 Michał Górny
2020-05-04 11:13 Michał Górny
2020-03-27 16:30 Michał Górny
2020-03-27 16:30 Michał Górny
2020-03-27 16:30 Michał Górny
2020-03-27 16:25 Joonas Niilola
2020-01-29 6:14 Joonas Niilola
2019-12-02 21:13 Aaron Bauman
2018-08-30 17:25 Michał Górny
2018-08-30 17:25 Michał Górny
2018-05-10 21:40 Patrice Clement
2018-04-22 1:35 Thomas Deutschmann
2018-03-21 20:24 Markus Meier
2018-03-12 0:51 Matt Turner
2018-03-04 22:40 Sergei Trofimovich
2017-09-01 10:28 Tim Harder
2017-09-01 10:28 Tim Harder
2017-06-23 7:04 Alexis Ballier
2017-05-03 9:26 Michał Górny
2017-04-26 8:20 Tim Harder
2017-02-16 20:47 Tim Harder
2016-05-22 15:59 Patrice Clement
2016-05-22 15:59 Patrice Clement
2016-01-25 15:11 Justin Lecher
2015-11-03 17:21 Justin Lecher
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=1594959500.2a5c256d844538978770bb4197699c48c1c851b4.mattst88@gentoo \
--to=mattst88@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