From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/softhsm/
Date: Sun, 18 Oct 2020 15:29:47 +0000 (UTC) [thread overview]
Message-ID: <1603034969.a247748dc6cf012585729862b92f615211d92479.zlogene@gentoo> (raw)
commit: a247748dc6cf012585729862b92f615211d92479
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 18 15:29:29 2020 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun Oct 18 15:29:29 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a247748d
dev-libs/softhsm: Stabilize 2.6.1 x86, #743142
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
dev-libs/softhsm/softhsm-2.6.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/softhsm/softhsm-2.6.1.ebuild b/dev-libs/softhsm/softhsm-2.6.1.ebuild
index de7ea2819c9..0d7093bbaa8 100644
--- a/dev-libs/softhsm/softhsm-2.6.1.ebuild
+++ b/dev-libs/softhsm/softhsm-2.6.1.ebuild
@@ -7,7 +7,7 @@ DESCRIPTION="A software PKCS#11 implementation"
HOMEPAGE="https://www.opendnssec.org/"
SRC_URI="https://www.opendnssec.org/files/source/${P}.tar.gz"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sparc ~x86"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sparc x86"
IUSE="bindist gost libressl migration-tool test"
RESTRICT="!test? ( test )"
SLOT="2"
next reply other threads:[~2020-10-18 15:29 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 15:29 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-10 21:18 [gentoo-commits] repo/gentoo:master commit in: dev-libs/softhsm/ Petr Vaněk
2024-04-15 9:00 Arthur Zamarin
2024-04-15 9:00 Arthur Zamarin
2024-04-15 9:00 Arthur Zamarin
2024-04-15 8:45 Arthur Zamarin
2024-04-15 8:43 Arthur Zamarin
2024-04-15 8:29 Arthur Zamarin
2024-04-15 8:29 Arthur Zamarin
2024-04-15 8:17 Sam James
2024-04-15 8:02 Sam James
2023-08-05 11:36 Arthur Zamarin
2022-05-19 10:35 WANG Xuerui
2021-12-16 0:09 Sam James
2021-12-03 4:50 Sam James
2021-07-28 18:41 Marek Szuba
2021-05-02 15:38 Mikle Kolyada
2021-03-10 1:24 Sam James
2020-10-18 15:29 Mikle Kolyada
2020-09-28 20:43 Sam James
2020-08-14 20:42 Matt Turner
2019-03-20 22:00 Alon Bar-Lev
2019-01-07 19:15 Lars Wendler
2019-01-04 20:12 Alon Bar-Lev
2018-10-19 16:12 Alon Bar-Lev
2018-09-27 23:55 Alon Bar-Lev
2018-08-14 16:02 Alon Bar-Lev
2018-05-10 18:31 Alon Bar-Lev
2018-04-10 19:24 Alon Bar-Lev
2018-03-28 20:55 Matt Turner
2017-07-28 8:33 Alon Bar-Lev
2017-06-26 7:54 Alexis Ballier
2017-03-25 18:11 Alon Bar-Lev
2017-03-21 18:11 Matt Turner
2017-03-21 18:11 Matt Turner
2017-03-21 18:11 Matt Turner
2017-03-21 18:11 Matt Turner
2017-03-21 18:11 Matt Turner
2017-03-02 18:59 Alon Bar-Lev
2017-02-11 11:12 Alon Bar-Lev
2017-02-11 0:09 Alon Bar-Lev
2017-02-04 21:40 Alon Bar-Lev
2017-01-28 11:18 Alon Bar-Lev
2017-01-28 11:05 Alon Bar-Lev
2017-01-27 18:42 Alon Bar-Lev
2017-01-05 12:56 Jeroen Roovers
2016-12-18 2:54 Marc Schiffbauer
2016-12-18 2:54 Marc Schiffbauer
2016-12-18 2:19 Marc Schiffbauer
2016-02-24 14:39 Marc Schiffbauer
2015-10-04 14:02 Marc Schiffbauer
2015-10-04 13:31 Marc Schiffbauer
2015-10-04 13:31 Marc Schiffbauer
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=1603034969.a247748dc6cf012585729862b92f615211d92479.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