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: app-portage/elogviewer/
Date: Thu,  6 Jun 2024 00:45:42 +0000 (UTC)	[thread overview]
Message-ID: <1717634690.6e187e57150a1c4b9aa057d1e823048589500aa2.sam@gentoo> (raw)

commit:     6e187e57150a1c4b9aa057d1e823048589500aa2
Author:     Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Wed Jun  5 22:59:55 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jun  6 00:44:50 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6e187e57

app-portage/elogviewer: enable py3.12

In fact it doesn't work on either py3.11 or py3.12 but that is because
it doesn't know how to find any logs. The actual package seems to
function equivalently, and passes unittest mocks, and can load logs via
the command line, so I guess the py3.12 migration is not, itself, a
problem.

Closes: https://bugs.gentoo.org/929350
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>

 app-portage/elogviewer/elogviewer-3.2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-portage/elogviewer/elogviewer-3.2.ebuild b/app-portage/elogviewer/elogviewer-3.2.ebuild
index fa50493d3bbc..9c0c03238ea1 100644
--- a/app-portage/elogviewer/elogviewer-3.2.ebuild
+++ b/app-portage/elogviewer/elogviewer-3.2.ebuild
@@ -3,7 +3,7 @@
 
 EAPI=7
 
-PYTHON_COMPAT=( python3_{9..11} )
+PYTHON_COMPAT=( python3_{10..12} )
 
 DISABLE_AUTOFORMATTING=true
 


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

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06  0:45 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-14 13:39 [gentoo-commits] repo/gentoo:master commit in: app-portage/elogviewer/ Arthur Zamarin
2025-02-14 13:35 Arthur Zamarin
2025-02-14 13:34 Arthur Zamarin
2025-02-14 13:34 Arthur Zamarin
2024-06-06  0:45 Sam James
2023-03-05 15:22 Sam James
2022-05-22 16:13 Zac Medico
2021-05-27  6:57 Agostino Sarubbo
2021-05-27  6:55 Agostino Sarubbo
2021-02-28 13:05 Ben Kohler
2021-02-24 13:55 Ben Kohler
2020-08-01 23:20 Andreas Sturmlechner
2020-08-01 23:20 Andreas Sturmlechner
2020-05-10  8:20 Brian Dolbec
2020-02-10 11:54 Michał Górny
2020-01-07 17:02 Ben Kohler
2019-09-14  5:18 Matt Turner
2019-05-18 10:02 Michał Górny
2018-06-24 13:09 Jason Zaman
2018-06-23 10:02 Pacho Ramos
2018-06-08 18:35 Andreas Sturmlechner
2018-06-08 18:35 Andreas Sturmlechner
2018-05-10 15:46 Brian Dolbec
2018-05-10 14:49 Andreas Sturmlechner
2018-03-21 18:12 Michał Górny
2018-03-21 18:12 Michał Górny
2017-09-02 14:50 Michael Palimaka
2017-08-05  8:10 Michael Palimaka
2017-07-15 15:17 Tobias Klausmann
2017-04-20  7:59 David Seifert
2017-03-10 14:26 Michael Weber
2016-12-24 21:54 Brian Dolbec
2016-05-22 10:37 Ian Delaney
2016-05-22 10:37 Ian Delaney
2015-12-03 10:07 Agostino Sarubbo
2015-12-02 18:23 Paul Varner
2015-11-12  9:40 Agostino Sarubbo
2015-11-11  9:12 Agostino Sarubbo
2015-11-09 10:31 Agostino Sarubbo
2015-09-11  5:40 Brian Dolbec
2015-09-11  5:26 Brian Dolbec

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=1717634690.6e187e57150a1c4b9aa057d1e823048589500aa2.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