From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/pcsc-tools/
Date: Mon, 16 Mar 2020 07:21:57 +0000 (UTC) [thread overview]
Message-ID: <1584343273.b6014c134662c3dc16ea7b7585744e42b40c3ae8.zlogene@gentoo> (raw)
commit: b6014c134662c3dc16ea7b7585744e42b40c3ae8
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Mon Mar 16 07:21:13 2020 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Mon Mar 16 07:21:13 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b6014c13
sys-apps/pcsc-tools: mark stable
Package-Manager: Portage-2.3.89, Repoman-2.3.20
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
sys-apps/pcsc-tools/pcsc-tools-1.5.5.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-apps/pcsc-tools/pcsc-tools-1.5.5.ebuild b/sys-apps/pcsc-tools/pcsc-tools-1.5.5.ebuild
index aae8a0221d7..add6360afa5 100644
--- a/sys-apps/pcsc-tools/pcsc-tools-1.5.5.ebuild
+++ b/sys-apps/pcsc-tools/pcsc-tools-1.5.5.ebuild
@@ -11,7 +11,7 @@ SRC_URI="http://ludovic.rousseau.free.fr/softwares/${PN}/${P}.tar.bz2"
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="~amd64 ~arm ~hppa ~ppc ~ppc64 ~x86"
+KEYWORDS="amd64 ~arm ~hppa ppc ppc64 x86"
IUSE="gtk network-cron"
DEPEND=">=sys-apps/pcsc-lite-1.4.14"
next reply other threads:[~2020-03-16 7:22 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 7:21 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-09 6:23 [gentoo-commits] repo/gentoo:master commit in: sys-apps/pcsc-tools/ Sam James
2024-02-02 16:27 Arthur Zamarin
2024-02-02 14:58 Arthur Zamarin
2024-02-02 6:40 Sam James
2024-02-02 3:58 Sam James
2024-01-23 15:08 Sam James
2024-01-18 0:28 Sam James
2024-01-17 8:53 Arthur Zamarin
2024-01-17 5:55 Sam James
2024-01-02 7:01 Sam James
2023-11-30 3:49 Sam James
2023-10-08 18:38 David Seifert
2023-04-23 20:48 Sam James
2023-04-23 20:22 Sam James
2023-04-23 20:22 Sam James
2023-04-23 20:22 Sam James
2023-03-23 9:08 Sam James
2023-03-23 9:08 Sam James
2023-03-23 9:08 Sam James
2023-03-04 11:48 Arthur Zamarin
2023-03-04 11:03 Arthur Zamarin
2023-03-04 8:57 Arthur Zamarin
2023-03-04 6:17 Arthur Zamarin
2023-01-01 0:04 Sam James
2022-12-26 8:35 Sam James
2022-11-25 5:44 Sam James
2022-11-25 5:39 Sam James
2022-11-25 5:21 Sam James
2022-11-25 5:04 Sam James
2022-10-29 21:32 Sam James
2022-10-04 6:30 Arthur Zamarin
2022-09-05 1:14 Sam James
2022-09-03 21:59 David Seifert
2022-09-03 10:59 David Seifert
2022-09-01 13:28 Jakov Smolić
2022-09-01 13:28 Jakov Smolić
2022-09-01 13:27 Jakov Smolić
2022-09-01 13:27 Jakov Smolić
2022-06-22 11:57 Jakov Smolić
2022-06-19 1:55 Sam James
2022-03-26 0:01 Sam James
2020-07-12 16:33 Mikle Kolyada
2020-07-12 16:32 Mikle Kolyada
2020-07-12 16:28 Mikle Kolyada
2020-03-16 7:21 Mikle Kolyada
2020-03-16 7:21 Mikle Kolyada
2020-01-27 19:09 Mikle Kolyada
2020-01-08 20:46 Mikle Kolyada
2020-01-08 16:57 Mikle Kolyada
2020-01-08 16:57 Mikle Kolyada
2019-11-18 22:17 Aaron Bauman
2018-09-27 23:55 Alon Bar-Lev
2018-09-01 7:21 Alon Bar-Lev
2017-03-19 4:12 Kent Fredric
2016-07-16 22:34 Manuel Rüger
2016-03-25 15:00 Manuel Rüger
2016-03-25 15:00 Manuel Rüger
2015-11-12 22:10 Manuel Rüger
2015-08-26 1:12 Manuel Rüger
2015-08-11 20:09 Alon Bar-Lev
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=1584343273.b6014c134662c3dc16ea7b7585744e42b40c3ae8.zlogene@gentoo \
--to=zlogene@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