public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/jitterentropy/
Date: Sun,  3 Nov 2019 13:40:58 +0000 (UTC)	[thread overview]
Message-ID: <1572788436.606b54d12c988cc6e9e1de7e413be8bc9ae001e7.zlogene@gentoo> (raw)

commit:     606b54d12c988cc6e9e1de7e413be8bc9ae001e7
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun Nov  3 13:40:36 2019 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun Nov  3 13:40:36 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=606b54d1

app-crypt/jitterentropy: arm stable wrt bug #699172

Package-Manager: Portage-2.3.76, Repoman-2.3.16
RepoMan-Options: --include-arches="arm"
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>

 app-crypt/jitterentropy/jitterentropy-2.1.2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-crypt/jitterentropy/jitterentropy-2.1.2.ebuild b/app-crypt/jitterentropy/jitterentropy-2.1.2.ebuild
index 412940d2dfa..0048f74e832 100644
--- a/app-crypt/jitterentropy/jitterentropy-2.1.2.ebuild
+++ b/app-crypt/jitterentropy/jitterentropy-2.1.2.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/smuellerDD/jitterentropy-library/archive/v${PV}.tar.
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~ia64 ~mips ~ppc ~ppc64 ~riscv ~x86"
+KEYWORDS="~alpha amd64 arm ~arm64 ~ia64 ~mips ~ppc ~ppc64 ~riscv ~x86"
 IUSE="static-libs"
 
 S="${WORKDIR}/${PN}-library-${PV}"


             reply	other threads:[~2019-11-03 13:41 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-03 13:40 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-07  7:41 [gentoo-commits] repo/gentoo:master commit in: app-crypt/jitterentropy/ Göktürk Yüksek
2023-12-14  4:15 Sam James
2023-09-09 13:17 David Seifert
2023-09-09 13:17 David Seifert
2023-01-05  0:19 Sam James
2023-01-05  0:19 Sam James
2023-01-05  0:19 Sam James
2023-01-05  0:19 Sam James
2023-01-05  0:19 Sam James
2023-01-05  0:19 Sam James
2022-09-19  3:05 Sam James
2022-06-28  6:41 Agostino Sarubbo
2022-06-27  7:37 Agostino Sarubbo
2022-06-27  7:36 Agostino Sarubbo
2022-06-27  7:36 Agostino Sarubbo
2022-06-27  7:35 Agostino Sarubbo
2022-06-27  7:35 Agostino Sarubbo
2022-02-15 20:17 Göktürk Yüksek
2022-02-12  9:29 Göktürk Yüksek
2021-03-06  6:04 Göktürk Yüksek
2021-03-06  6:04 Göktürk Yüksek
2020-10-06 13:43 Sam James
2020-10-04 16:59 Sam James
2020-09-30  1:49 Sam James
2020-09-26 10:06 Sergei Trofimovich
2020-09-26  9:18 Sergei Trofimovich
2020-09-25  8:46 Agostino Sarubbo
2020-04-05 20:06 Mart Raudsepp
2020-03-30 12:20 Göktürk Yüksek
2019-11-13  7:39 Agostino Sarubbo
2019-11-12 15:08 Agostino Sarubbo
2019-11-04  9:22 Agostino Sarubbo
2019-11-03  9:13 Piotr Karbowski
2019-08-11 21:38 Matt Turner
2019-08-08 23:57 Matt Turner
2019-08-08 16:01 Matt Turner
2019-08-06 17:50 Matt Turner
2019-08-05 23:55 Göktürk Yüksek
2019-08-05 23:34 Aaron Bauman
2019-08-05  5:08 Matt Turner
2019-08-05  5:08 Matt Turner
2019-06-12 22:59 Göktürk Yüksek
2019-06-12 22:59 Göktürk Yüksek

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=1572788436.606b54d12c988cc6e9e1de7e413be8bc9ae001e7.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