From: "Matthew Thode" <prometheanfire@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/voluptuous/
Date: Sat, 2 May 2020 04:31:01 +0000 (UTC) [thread overview]
Message-ID: <1588393853.ae36b4b117dfed9f63a98124533ea0d9edf3948c.prometheanfire@gentoo> (raw)
commit: ae36b4b117dfed9f63a98124533ea0d9edf3948c
Author: Andrew Udvare <audvare <AT> gmail <DOT> com>
AuthorDate: Fri May 1 22:45:50 2020 +0000
Commit: Matthew Thode <prometheanfire <AT> gentoo <DOT> org>
CommitDate: Sat May 2 04:30:53 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ae36b4b1
dev-python/voluptuous: add python3_8 to PYTHON_COMPAT
Signed-off-by: Andrew Udvare <audvare <AT> gmail.com>
Signed-off-by: Matthew Thode <prometheanfire <AT> gentoo.org>
.../{voluptuous-0.11.1.ebuild => voluptuous-0.11.1-r1.ebuild} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/voluptuous/voluptuous-0.11.1.ebuild b/dev-python/voluptuous/voluptuous-0.11.1-r1.ebuild
similarity index 92%
rename from dev-python/voluptuous/voluptuous-0.11.1.ebuild
rename to dev-python/voluptuous/voluptuous-0.11.1-r1.ebuild
index f4517ddae71..7cdce4236c2 100644
--- a/dev-python/voluptuous/voluptuous-0.11.1.ebuild
+++ b/dev-python/voluptuous/voluptuous-0.11.1-r1.ebuild
@@ -2,7 +2,7 @@
# Distributed under the terms of the GNU General Public License v2
EAPI=6
-PYTHON_COMPAT=( python{2_7,3_6,3_7} )
+PYTHON_COMPAT=( python{2_7,3_6,3_7,3_8} )
inherit distutils-r1
next reply other threads:[~2020-05-02 4:31 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 4:31 Matthew Thode [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-20 9:01 [gentoo-commits] repo/gentoo:master commit in: dev-python/voluptuous/ Michał Górny
2024-07-20 7:42 Arthur Zamarin
2024-07-03 3:44 Michał Górny
2024-06-27 2:53 Michał Górny
2024-06-24 2:41 Michał Górny
2024-05-18 11:11 Michał Górny
2024-02-20 9:09 Michał Górny
2024-02-20 7:55 Sam James
2024-02-04 4:01 Michał Górny
2023-11-29 11:04 Michał Górny
2023-11-17 13:32 Michał Górny
2023-11-12 19:20 Michał Górny
2023-05-27 19:21 Arthur Zamarin
2022-05-28 21:12 Jakov Smolić
2022-05-01 12:56 Michał Górny
2022-05-01 12:20 Jakov Smolić
2022-04-08 7:33 Michał Górny
2022-04-07 16:59 Arthur Zamarin
2022-03-30 18:45 Michał Górny
2021-10-24 5:13 Arthur Zamarin
2021-09-23 8:16 Michał Górny
2021-06-05 18:39 Michał Górny
2021-01-13 20:16 Michał Górny
2021-01-13 19:07 Sam James
2020-12-07 11:39 Michał Górny
2020-10-22 21:06 Michał Górny
2020-10-22 7:18 Sam James
2020-09-22 20:40 Michał Górny
2020-09-22 19:33 Sam James
2020-09-21 15:30 Michał Górny
2020-09-21 15:30 Michał Górny
2020-08-21 19:28 David Seifert
2020-08-02 9:33 Michał Górny
2020-06-10 8:11 Michał Górny
2020-05-31 15:42 Michał Górny
2020-05-02 18:38 Matthew Thode
2020-04-21 19:45 Sergei Trofimovich
2020-04-08 20:53 Sergei Trofimovich
2020-03-29 11:14 Michał Górny
2019-01-28 0:25 Matthew Thode
2018-08-30 17:50 Matt Thode
2018-07-25 7:07 Matt Thode
2018-04-29 3:14 Matt Thode
2018-04-29 3:14 Matt Thode
2018-03-29 15:54 Matt Thode
2017-08-28 21:52 Matt Thode
2017-05-05 12:44 Manuel Rüger
2016-10-11 18:45 Matt Thode
2016-10-11 18:45 Matt Thode
2016-09-14 13:08 Matt Thode
2016-09-12 14:30 Matt Thode
2016-03-25 22:58 Matt Thode
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=1588393853.ae36b4b117dfed9f63a98124533ea0d9edf3948c.prometheanfire@gentoo \
--to=prometheanfire@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