From: "Pacho Ramos" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/anjuta/
Date: Sat, 19 Sep 2020 19:57:17 +0000 (UTC) [thread overview]
Message-ID: <1600545432.7e09dcf5dec29469a3a02b3bc2a30244a19d2733.pacho@gentoo> (raw)
commit: 7e09dcf5dec29469a3a02b3bc2a30244a19d2733
Author: Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Sat Sep 19 19:56:54 2020 +0000
Commit: Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Sat Sep 19 19:57:12 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7e09dcf5
dev-util/anjuta: Port to python3
It looks to work ok for me with python3, also Debian and Fedora are using it
with python3 for a long time without issues. If it still fails, a bug should
be opened and it should be tracked with upstream if needed.
Closes: https://bugs.gentoo.org/735318
Package-Manager: Portage-3.0.7, Repoman-3.0.1
Signed-off-by: Pacho Ramos <pacho <AT> gentoo.org>
dev-util/anjuta/anjuta-3.34.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-util/anjuta/anjuta-3.34.0.ebuild b/dev-util/anjuta/anjuta-3.34.0.ebuild
index 97bb17cc382..4e3d1619f0d 100644
--- a/dev-util/anjuta/anjuta-3.34.0.ebuild
+++ b/dev-util/anjuta/anjuta-3.34.0.ebuild
@@ -3,7 +3,7 @@
EAPI=6
GNOME2_LA_PUNT="yes"
-PYTHON_COMPAT=( python2_7 ) # python loader crashes on load with py3 in 3.34.0
+PYTHON_COMPAT=( python3_{7..9} )
# libanjuta-language-vala.so links to a specific slot of libvala; we want to
# avoid automagic behavior.
VALA_MIN_API_VERSION="0.46" # 3.34.0 upstream release supports up to 0.44, but 0.46 vala LTS support was added without any other adjustments post-release; 0.48 will need patches
next reply other threads:[~2020-09-19 19:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 19:57 Pacho Ramos [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-13 19:53 [gentoo-commits] repo/gentoo:master commit in: dev-util/anjuta/ Sam James
2022-04-26 21:29 James Le Cuirot
2020-07-04 15:07 Mart Raudsepp
2020-06-12 22:16 Mart Raudsepp
2019-04-13 9:47 Mart Raudsepp
2019-04-02 9:13 Mikle Kolyada
2019-04-02 1:37 Thomas Deutschmann
2019-03-30 21:56 Mart Raudsepp
2019-03-22 21:37 Mart Raudsepp
2018-08-03 10:30 Mart Raudsepp
2017-04-02 13:03 Mart Raudsepp
2016-11-02 8:34 Gilles Dartiguelongue
2016-10-08 9:51 Pacho Ramos
2016-03-06 16:43 Mikle Kolyada
2016-02-01 20:45 Pacho Ramos
2016-02-01 20:45 Pacho Ramos
2015-11-14 18:40 Pacho Ramos
2015-11-14 18:40 Pacho Ramos
2015-11-12 8:56 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=1600545432.7e09dcf5dec29469a3a02b3bc2a30244a19d2733.pacho@gentoo \
--to=pacho@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