public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jack Sangdahl" <0x6A73@pm.me>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: app-misc/anki-bin/
Date: Mon, 28 Nov 2022 10:10:16 +0000 (UTC)	[thread overview]
Message-ID: <1669630071.35ec680388ea396c7cfb15f7168d9a74e905c2f8.0x6A73@gentoo> (raw)

commit:     35ec680388ea396c7cfb15f7168d9a74e905c2f8
Author:     Jack Sangdahl <0x6A73 <AT> pm <DOT> me>
AuthorDate: Mon Nov 28 10:07:51 2022 +0000
Commit:     Jack Sangdahl <0x6A73 <AT> pm <DOT> me>
CommitDate: Mon Nov 28 10:07:51 2022 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=35ec6803

app-misc/anki-bin: python 3.10

Signed-off-by: Jack Sangdahl <0x6A73 <AT> pm.me>

 app-misc/anki-bin/anki-bin-2.1.54-r1.ebuild | 2 +-
 app-misc/anki-bin/anki-bin-2.1.54.ebuild    | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/app-misc/anki-bin/anki-bin-2.1.54-r1.ebuild b/app-misc/anki-bin/anki-bin-2.1.54-r1.ebuild
index bc3edd17e..37b482975 100644
--- a/app-misc/anki-bin/anki-bin-2.1.54-r1.ebuild
+++ b/app-misc/anki-bin/anki-bin-2.1.54-r1.ebuild
@@ -3,7 +3,7 @@
 
 EAPI=8
 
-PYTHON_COMPAT=( python3_9 )
+PYTHON_COMPAT=( python3_{9..10} )
 inherit python-single-r1 desktop xdg
 
 MY_PN=${PN%-bin}

diff --git a/app-misc/anki-bin/anki-bin-2.1.54.ebuild b/app-misc/anki-bin/anki-bin-2.1.54.ebuild
index ec35b0130..ec2fa578e 100644
--- a/app-misc/anki-bin/anki-bin-2.1.54.ebuild
+++ b/app-misc/anki-bin/anki-bin-2.1.54.ebuild
@@ -3,7 +3,7 @@
 
 EAPI=7
 
-PYTHON_COMPAT=( python3_{8,9} )
+PYTHON_COMPAT=( python3_{9..10} )
 inherit python-single-r1 desktop xdg
 
 MY_PN=${PN%-bin}


             reply	other threads:[~2022-11-28 10:10 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28 10:10 Jack Sangdahl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-03 22:48 [gentoo-commits] repo/proj/guru:dev commit in: app-misc/anki-bin/ Lucio Sauer
2025-03-03 22:48 Lucio Sauer
2024-12-24 15:30 Lucio Sauer
2024-12-15 23:05 Lucio Sauer
2024-12-15 23:05 Lucio Sauer
2024-11-24 21:06 Anna Vyalkova
2024-11-24 21:06 Anna Vyalkova
2024-11-14  3:45 Anna Vyalkova
2024-09-01 20:58 Lucio Sauer
2024-09-01 20:58 Lucio Sauer
2024-07-03 16:11 Lucio Sauer
2024-07-03 16:07 Lucio Sauer
2024-06-20  2:41 Lucio Sauer
2024-04-29 14:14 Lucio Sauer
2024-04-28 18:00 Lucio Sauer
2024-04-28 17:55 Lucio Sauer
2024-04-28 17:55 Lucio Sauer
2024-04-01 20:38 Lucio Sauer
2024-02-25  1:21 Lucio Sauer
2023-12-28 13:46 Lucio Sauer
2023-12-28 13:46 Lucio Sauer
2023-12-26 18:24 Lucio Sauer
2023-12-26 18:24 Lucio Sauer
2023-12-11 13:28 Lucio Sauer
2023-11-27  0:32 Lucio Sauer
2023-11-24 12:17 Lucio Sauer
2023-11-24 12:17 Lucio Sauer
2023-11-09  5:49 Amano Kenji
2023-11-02  0:58 Shaoyu Tseng
2023-08-27 19:51 Lucio Sauer
2023-08-24 20:02 Lucio Sauer
2023-08-24 20:02 Lucio Sauer
2023-06-12  7:39 Lucio Sauer
2023-06-07 19:58 Lucio Sauer
2023-06-07 19:53 Lucio Sauer
2023-06-05 22:32 Lucio Sauer
2023-05-24 22:38 Lucio Sauer
2023-05-24 22:38 Lucio Sauer
2023-05-15 19:17 Lucio Sauer
2023-05-15 19:17 Lucio Sauer
2023-05-06 22:52 Lucio Sauer
2023-05-06 22:52 Lucio Sauer
2023-03-31 22:08 Lucio Sauer
2023-03-31 22:08 Lucio Sauer
2023-02-22 16:51 Lucio Sauer
2023-02-22 16:51 Lucio Sauer
2023-02-21  0:56 Lucio Sauer
2023-01-29 19:41 Lucio Sauer
2023-01-29 19:41 Lucio Sauer
2023-01-14 19:22 Ran Rutenberg
2023-01-14 16:35 Ran Rutenberg
2023-01-10  2:40 Shaoyu Tseng
2022-12-30  2:45 Lucio Sauer
2022-12-30  2:45 Lucio Sauer
2022-11-28 18:59 Jack Sangdahl
2022-09-18  4:37 Lucio Sauer
2022-09-18  4:37 Lucio Sauer
2022-09-16  0:50 Lucio Sauer
2022-03-28 19:52 Shaoyu Tseng
2021-10-17 16:23 Shaoyu Tseng
2021-08-08  3:51 Shaoyu Tseng
2021-07-31  8:17 Shaoyu Tseng
2021-07-30  9:27 Shaoyu Tseng
2021-07-30  9:11 Andrew Ammerlaan
2021-07-29 12:20 Shaoyu Tseng
2021-07-29 11:41 Shaoyu Tseng

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=1669630071.35ec680388ea396c7cfb15f7168d9a74e905c2f8.0x6A73@gentoo \
    --to=0x6a73@pm.me \
    --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