public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/firejail/
Date: Tue,  4 Jun 2024 00:51:12 +0000 (UTC)	[thread overview]
Message-ID: <1717462106.e41b25041e343a3d7e45b5c2bbbd09962b19d133.sam@gentoo> (raw)

commit:     e41b25041e343a3d7e45b5c2bbbd09962b19d133
Author:     Alfred Wingate <parona <AT> protonmail <DOT> com>
AuthorDate: Mon Jun  3 22:28:23 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jun  4 00:48:26 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e41b2504

sys-apps/firejail: enable py3.12

Closes: https://bugs.gentoo.org/929812
Signed-off-by: Alfred Wingate <parona <AT> protonmail.com>
Closes: https://github.com/gentoo/gentoo/pull/37014
Signed-off-by: Sam James <sam <AT> gentoo.org>

 sys-apps/firejail/firejail-0.9.72.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sys-apps/firejail/firejail-0.9.72.ebuild b/sys-apps/firejail/firejail-0.9.72.ebuild
index 85c24854379a..a778a5a44e7c 100644
--- a/sys-apps/firejail/firejail-0.9.72.ebuild
+++ b/sys-apps/firejail/firejail-0.9.72.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
 
-PYTHON_COMPAT=( python3_{9..11} )
+PYTHON_COMPAT=( python3_{10..12} )
 
 inherit toolchain-funcs python-single-r1 linux-info
 


             reply	other threads:[~2024-06-04  0:51 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04  0:51 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-02  4:57 [gentoo-commits] repo/gentoo:master commit in: sys-apps/firejail/ Sam James
2023-04-19  9:45 Sam James
2022-08-27 11:38 Sam James
2022-07-15 10:28 Joonas Niilola
2022-03-29  7:20 Joonas Niilola
2022-02-21  1:51 Sam James
2021-07-16  0:38 Sam James
2021-07-16  0:36 Sam James
2021-07-16  0:36 Sam James
2021-02-21  5:19 Sam James
2021-02-18 23:12 Conrad Kostecki
2021-02-18  0:59 Sam James
2021-02-18  0:54 Sam James
2021-02-09  7:34 Sam James
2020-12-02 23:21 Sam James
2020-11-21  7:21 Joonas Niilola
2020-11-20 11:45 Joonas Niilola
2020-11-20 11:45 Joonas Niilola
2020-11-20 10:42 Joonas Niilola
2020-11-20 10:42 Joonas Niilola
2020-11-14 23:39 Sam James
2020-11-13 20:57 Aaron Bauman
2020-11-11  7:50 Joonas Niilola
2020-11-11  7:50 Joonas Niilola
2020-11-11  7:50 Joonas Niilola
2020-10-11 19:42 Dennis Lamm
2020-08-22 10:18 Dennis Lamm
2020-08-22 10:18 Dennis Lamm
2020-07-05 13:36 Agostino Sarubbo
2020-01-02 16:45 Dennis Lamm
2019-11-09 11:52 Dennis Lamm
2019-11-09 11:18 Dennis Lamm
2019-10-28  7:41 Agostino Sarubbo
2019-08-11 20:06 Dennis Lamm
2019-08-04 18:27 Dennis Lamm
2019-07-29 18:36 Mikle Kolyada
2019-07-29 12:16 Mikle Kolyada
2019-07-29  4:21 Dennis Lamm
2019-07-07 21:13 Amadeusz Piotr Żołnowski
2018-12-04 22:16 Amadeusz Piotr Żołnowski
2017-12-16 17:24 Tobias Klausmann
2017-11-30 20:40 Thomas Deutschmann
2017-09-10 21:49 Amadeusz Piotr Żołnowski
2017-05-16 21:41 Amadeusz Piotr Żołnowski
2017-01-30 13:09 Agostino Sarubbo
2017-01-27 22:21 Amadeusz Piotr Żołnowski
2017-01-27 22:21 Amadeusz Piotr Żołnowski
2017-01-13 17:06 Agostino Sarubbo
2016-12-18 13:27 Amadeusz Piotr Żołnowski
2016-12-13 11:05 Agostino Sarubbo
2016-10-30 10:37 Amadeusz Piotr Żołnowski
2016-09-27  8:57 Agostino Sarubbo
2016-09-26 20:35 Amadeusz Piotr Żołnowski
2016-09-26 20:35 Amadeusz Piotr Żołnowski
2016-09-26 12:36 Agostino Sarubbo
2016-09-14  9:19 Amadeusz Piotr Żołnowski
2016-06-06 13:33 Agostino Sarubbo
2016-06-04 20:56 Amadeusz Piotr Żołnowski
2016-06-04 18:24 Amadeusz Piotr Żołnowski
2016-04-20  4:29 Mike Frysinger
2016-02-12 20:09 Amadeusz Piotr Żołnowski
2016-02-12 20:06 Amadeusz Piotr Żołnowski
2016-01-05 21:20 Amadeusz Piotr Żołnowski

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=1717462106.e41b25041e343a3d7e45b5c2bbbd09962b19d133.sam@gentoo \
    --to=sam@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