public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-vcs/gitg/
Date: Sat,  7 Apr 2018 14:34:09 +0000 (UTC)	[thread overview]
Message-ID: <1523111623.3d0e6f9a888dbd332e82c9cae573fa21bcff3ccd.leio@gentoo> (raw)

commit:     3d0e6f9a888dbd332e82c9cae573fa21bcff3ccd
Author:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Sat Apr  7 14:33:11 2018 +0000
Commit:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Sat Apr  7 14:33:43 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3d0e6f9a

dev-vcs/gitg: add python3.6 compat

Works as well as with python3.4 (read: fails to actually import GitgExt override
with an assert failure). I would outright remove the python override support, as
there are no consumers of it, but that's a too big change for this revision and
we need to do something soon about libgit2-0.27 compat anyways..

Package-Manager: Portage-2.3.28, Repoman-2.3.9

 dev-vcs/gitg/gitg-3.26.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-vcs/gitg/gitg-3.26.0.ebuild b/dev-vcs/gitg/gitg-3.26.0.ebuild
index f438d41513f..c9365256aab 100644
--- a/dev-vcs/gitg/gitg-3.26.0.ebuild
+++ b/dev-vcs/gitg/gitg-3.26.0.ebuild
@@ -3,7 +3,7 @@
 
 EAPI=6
 GNOME2_LA_PUNT="yes"
-PYTHON_COMPAT=( python{3_4,3_5} )
+PYTHON_COMPAT=( python3_{4,5,6} )
 VALA_MIN_API_VERSION="0.32" # Needed when gtk+-3.20 is found
 
 inherit gnome2 pax-utils python-r1 vala


             reply	other threads:[~2018-04-07 14:34 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-07 14:34 Mart Raudsepp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-29 22:23 [gentoo-commits] repo/gentoo:master commit in: dev-vcs/gitg/ Mart Raudsepp
2023-10-29 22:23 Mart Raudsepp
2023-10-06 18:08 Sam James
2023-10-06 18:08 Sam James
2023-09-03 14:01 Matt Turner
2023-01-01 16:20 David Seifert
2022-10-30 15:42 Matt Turner
2022-02-10 12:02 Michał Górny
2022-02-10 11:53 Jakov Smolić
2022-02-10 11:13 Jakov Smolić
2022-01-25  0:51 Sam James
2021-12-30 10:51 Michał Górny
2021-12-30  8:57 Michał Górny
2020-12-23 12:57 Michał Górny
2020-02-27 16:26 Michał Górny
2019-08-22 13:01 Michał Górny
2019-08-19  4:29 Michał Górny
2019-08-18 21:51 Agostino Sarubbo
2019-08-16 22:38 Thomas Deutschmann
2019-07-25 14:27 Michał Górny
2018-12-29 12:41 Gilles Dartiguelongue
2018-10-26  8:38 Michał Górny
2018-10-10 15:48 Mart Raudsepp
2018-02-19 20:03 Mart Raudsepp
2018-02-06 18:36 Thomas Deutschmann
2018-01-26 15:03 Mikle Kolyada
2017-11-26 11:39 David Seifert
2017-08-24  7:09 Michał Górny
2017-08-22 12:59 Mart Raudsepp
2017-05-01 22:35 Mart Raudsepp
2017-05-01 22:35 Mart Raudsepp
2017-05-01 22:35 Mart Raudsepp
2017-04-18 10:56 Mart Raudsepp
2016-10-20  7:42 Gilles Dartiguelongue
2016-10-20  7:42 Gilles Dartiguelongue
2016-09-17 12:39 Gilles Dartiguelongue
2016-09-05 22:37 Gilles Dartiguelongue
2016-08-17 18:38 Pacho Ramos
2016-07-02 10:43 Pacho Ramos
2016-07-02 10:43 Pacho Ramos
2016-03-08  4:37 Alexandre Rostovtsev
2016-03-06 16:43 Mikle Kolyada
2016-02-03  5:33 Ian Delaney
2015-11-17 20:23 Pacho Ramos
2015-08-30 12:47 Mike Auty
2015-08-29 17:19 Mike Auty
2015-08-29 12:31 Mike Auty
2015-08-29 12:28 Mike Auty

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=1523111623.3d0e6f9a888dbd332e82c9cae573fa21bcff3ccd.leio@gentoo \
    --to=leio@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