public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Pacho Ramos" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: games-board/gnome-mines/
Date: Tue, 30 Jul 2024 08:49:59 +0000 (UTC)	[thread overview]
Message-ID: <1722329283.32175d5658fe135ce21d3fdd21269be798b3156f.pacho@gentoo> (raw)

commit:     32175d5658fe135ce21d3fdd21269be798b3156f
Author:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 30 08:30:40 2024 +0000
Commit:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Tue Jul 30 08:48:03 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=32175d56

games-board/gnome-mines: Support python 3.12

Closes: https://bugs.gentoo.org/929573
Signed-off-by: Pacho Ramos <pacho <AT> gentoo.org>

 games-board/gnome-mines/gnome-mines-40.1.ebuild | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/games-board/gnome-mines/gnome-mines-40.1.ebuild b/games-board/gnome-mines/gnome-mines-40.1.ebuild
index b0ef7a340d18..d591d53e4cf9 100644
--- a/games-board/gnome-mines/gnome-mines-40.1.ebuild
+++ b/games-board/gnome-mines/gnome-mines-40.1.ebuild
@@ -1,12 +1,12 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
-EAPI=7
-PYTHON_COMPAT=( python3_{9..11} )
+EAPI=8
+PYTHON_COMPAT=( python3_{10..12} )
 inherit gnome.org gnome2-utils meson python-any-r1 vala xdg
 
 DESCRIPTION="Clear hidden mines from a minefield"
-HOMEPAGE="https://wiki.gnome.org/Apps/Mines"
+HOMEPAGE="https://gitlab.gnome.org/GNOME/gnome-mines"
 
 LICENSE="GPL-3+ CC-BY-SA-3.0"
 SLOT="0"
@@ -32,8 +32,8 @@ BDEPEND="
 "
 
 src_prepare() {
-	xdg_src_prepare
-	vala_src_prepare
+	default
+	vala_setup
 }
 
 pkg_postinst() {


             reply	other threads:[~2024-07-30  8:50 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30  8:49 Pacho Ramos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-30 15:42 [gentoo-commits] repo/gentoo:master commit in: games-board/gnome-mines/ Matt Turner
2022-02-18 22:49 Matt Turner
2022-02-08  4:45 Sam James
2022-01-16 12:33 Mart Raudsepp
2021-04-20  2:49 Matt Turner
2021-03-27 20:41 Matt Turner
2020-08-06 21:38 Mart Raudsepp
2020-03-29 16:41 Mart Raudsepp
2020-03-15 12:23 Mikle Kolyada
2019-12-22 20:47 Mart Raudsepp
2019-10-20 17:38 Mart Raudsepp
2019-05-18 20:46 Mart Raudsepp
2019-04-14 15:30 Aaron Bauman
2019-03-14 18:38 Mart Raudsepp
2019-02-17 12:35 Mart Raudsepp
2019-02-17 12:35 Mart Raudsepp
2019-02-17 11:34 Mart Raudsepp
2019-02-17 11:34 Mart Raudsepp
2018-12-19  8:45 Gilles Dartiguelongue
2018-09-14  8:17 Mart Raudsepp
2018-09-14  8:17 Mart Raudsepp
2018-08-31 23:43 Mart Raudsepp
2018-02-03 19:40 Mart Raudsepp
2018-01-18  2:27 Mikle Kolyada
2017-08-08 22:10 Gilles Dartiguelongue
2017-05-01 21:49 Mart Raudsepp
2017-04-02 13:03 Mart Raudsepp
2016-11-09 23:27 Gilles Dartiguelongue
2016-10-31 11:06 Gilles Dartiguelongue
2016-10-31 11:06 Gilles Dartiguelongue
2016-07-02 10:43 Pacho Ramos
2016-07-02 10:43 Pacho Ramos
2016-06-02  7:37 Patrice Clement
2016-03-06 16:43 Mikle Kolyada
2015-11-09 21:51 Pacho Ramos
2015-11-09 21:51 Pacho Ramos

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=1722329283.32175d5658fe135ce21d3fdd21269be798b3156f.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