From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pyscard/
Date: Thu, 3 Nov 2022 20:17:58 +0000 (UTC) [thread overview]
Message-ID: <1667506667.b123d225c64ec34c45d6b6f50ee1baa9437f11ec.sam@gentoo> (raw)
commit: b123d225c64ec34c45d6b6f50ee1baa9437f11ec
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Nov 3 20:17:47 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Nov 3 20:17:47 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b123d225
dev-python/pyscard: Stabilize 2.0.5 amd64, #879417
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/pyscard/pyscard-2.0.5.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/pyscard/pyscard-2.0.5.ebuild b/dev-python/pyscard/pyscard-2.0.5.ebuild
index acbc37af89b9..e37af30c2471 100644
--- a/dev-python/pyscard/pyscard-2.0.5.ebuild
+++ b/dev-python/pyscard/pyscard-2.0.5.ebuild
@@ -18,7 +18,7 @@ SRC_URI="mirror://sourceforge/${PN}/${P}.tar.gz"
LICENSE="LGPL-2.1"
SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~ppc64 ~riscv ~x86"
+KEYWORDS="amd64 ~arm ~arm64 ~ppc64 ~riscv ~x86"
DEPEND="
sys-apps/pcsc-lite
next reply other threads:[~2022-11-03 20:18 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 20:17 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-10 3:24 [gentoo-commits] repo/gentoo:master commit in: dev-python/pyscard/ Michał Górny
2024-11-10 0:42 Jakov Smolić
2024-11-10 0:42 Jakov Smolić
2024-11-09 10:21 Arthur Zamarin
2024-10-21 4:35 Michał Górny
2024-09-28 15:25 Michał Górny
2024-09-28 13:32 Arthur Zamarin
2024-09-28 11:41 Arthur Zamarin
2024-09-28 11:41 Arthur Zamarin
2024-09-10 7:06 Michał Górny
2024-09-09 2:24 Michał Górny
2024-06-29 16:58 Michał Górny
2024-06-29 8:53 Sam James
2024-06-29 8:25 Sam James
2024-06-29 8:25 Sam James
2024-06-15 15:43 Petr Vaněk
2024-06-02 2:35 Michał Górny
2024-04-25 3:39 Michał Górny
2024-04-24 17:16 Sam James
2024-04-24 15:31 Sam James
2024-04-24 15:31 Sam James
2024-04-06 15:01 Michał Górny
2024-03-30 16:21 Michał Górny
2024-03-30 15:28 Michał Górny
2024-03-30 14:59 Michał Górny
2024-03-30 14:59 Michał Górny
2024-03-10 3:35 Michał Górny
2023-11-24 15:12 Arthur Zamarin
2023-08-23 23:37 Marek Szuba
2023-05-04 16:30 Michał Górny
2023-05-03 7:57 Michał Górny
2023-05-03 6:33 Arthur Zamarin
2023-05-02 19:31 Sam James
2023-04-01 6:13 Michał Górny
2022-11-04 8:38 Michał Górny
2022-11-04 8:16 Agostino Sarubbo
2022-10-03 6:53 Michał Górny
2022-10-03 0:44 Sam James
2022-09-28 18:34 Michał Górny
2022-08-28 20:15 Arthur Zamarin
2022-06-20 15:40 Marek Szuba
2022-04-19 16:03 Michał Górny
2022-04-19 13:46 Jakov Smolić
2022-04-19 13:46 Jakov Smolić
2022-03-18 22:28 Michał Górny
2022-01-11 2:23 Georgy Yakovlev
2021-12-31 1:15 Georgy Yakovlev
2021-10-24 5:23 Arthur Zamarin
2021-10-24 4:51 Sam James
2021-10-24 1:15 Sam James
2021-09-23 8:16 Michał Górny
2021-08-01 22:07 Marek Szuba
2021-07-25 8:41 Michał Górny
2021-07-25 1:29 Sam James
2021-07-24 17:10 Sam James
2021-06-17 19:47 Michał Górny
2021-05-27 15:37 Marek Szuba
2021-03-02 9:06 Michał Górny
2021-03-02 7:39 Sam James
2021-03-02 7:38 Sam James
2020-12-31 6:07 Sam James
2020-12-03 16:53 Marek Szuba
2020-05-04 11:44 Michał Górny
2020-05-03 19:02 Agostino Sarubbo
2020-03-19 2:11 Rick Farina
2020-03-19 2:11 Rick Farina
2020-02-05 19:53 Michał Górny
2019-03-20 22:00 Alon Bar-Lev
2019-03-19 15:38 Rick Farina
2019-03-11 8:40 Mikle Kolyada
2018-12-30 17:33 Alon Bar-Lev
2018-09-27 23:55 Alon Bar-Lev
2018-03-20 21:11 Michał Górny
2018-01-08 23:57 Thomas Deutschmann
2017-08-18 17:34 Alon Bar-Lev
2017-05-14 10:45 Manuel Rüger
2017-05-11 13:02 Manuel Rüger
2016-06-12 13:41 Alon Bar-Lev
2016-03-02 19:25 Markus Meier
2016-02-19 13:02 Patrick Lauer
2016-02-07 9:48 Justin Lecher
2016-02-06 8:51 Justin Lecher
2015-12-23 13:50 Alon Bar-Lev
2015-08-17 2:31 Ian Delaney
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=1667506667.b123d225c64ec34c45d6b6f50ee1baa9437f11ec.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