From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/haveged/
Date: Wed, 8 Apr 2020 10:17:51 +0000 (UTC) [thread overview]
Message-ID: <1586341062.7b87bbe15b4968be5f7e5d6cc44d9713e0269415.ago@gentoo> (raw)
commit: 7b87bbe15b4968be5f7e5d6cc44d9713e0269415
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Wed Apr 8 10:17:42 2020 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Wed Apr 8 10:17:42 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7b87bbe1
sys-apps/haveged: arm stable wrt bug #713006
Package-Manager: Portage-2.3.89, Repoman-2.3.20
RepoMan-Options: --include-arches="arm"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
sys-apps/haveged/haveged-1.9.8c.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-apps/haveged/haveged-1.9.8c.ebuild b/sys-apps/haveged/haveged-1.9.8c.ebuild
index 12c4f0ab2d6..9054d5f0026 100644
--- a/sys-apps/haveged/haveged-1.9.8c.ebuild
+++ b/sys-apps/haveged/haveged-1.9.8c.ebuild
@@ -10,7 +10,7 @@ SRC_URI="https://github.com/jirka-h/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="GPL-3+"
SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ~ppc ~ppc64 ~x86"
+KEYWORDS="amd64 arm ~arm64 ~ppc ~ppc64 ~x86"
IUSE="selinux static-libs threads"
RDEPEND="
next reply other threads:[~2020-04-08 10:17 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 10:17 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-02 10:20 [gentoo-commits] repo/gentoo:master commit in: sys-apps/haveged/ WANG Xuerui
2022-07-25 7:09 Agostino Sarubbo
2022-07-22 17:57 Sam James
2022-07-22 14:33 Anthony G. Basile
2022-05-05 15:06 Anthony G. Basile
2022-02-19 14:12 Arthur Zamarin
2022-02-19 13:22 Jakov Smolić
2022-02-19 13:15 Jakov Smolić
2022-02-19 12:45 Arthur Zamarin
2022-01-10 15:58 Anthony G. Basile
2022-01-09 1:42 Sam James
2021-12-24 18:18 Arthur Zamarin
2021-12-24 18:18 Arthur Zamarin
2021-12-24 13:51 Jakov Smolić
2021-12-24 13:51 Jakov Smolić
2021-12-24 8:08 Sam James
2021-12-24 8:08 Sam James
2021-10-04 14:51 Anthony G. Basile
2021-07-22 0:41 Georgy Yakovlev
2021-07-06 19:00 Georgy Yakovlev
2021-06-19 22:54 Joshua Kinard
2021-03-11 13:30 Sam James
2021-03-11 2:36 Sam James
2021-03-09 10:30 Sam James
2021-01-20 21:16 Lars Wendler
2021-01-20 21:16 Lars Wendler
2021-01-08 1:58 Anthony G. Basile
2020-07-14 11:10 Jeroen Roovers
2020-06-29 18:41 Anthony G. Basile
2020-06-22 13:33 Anthony G. Basile
2020-06-22 13:30 Anthony G. Basile
2020-06-17 15:59 Anthony G. Basile
2020-06-10 19:46 Anthony G. Basile
2020-04-14 12:32 Agostino Sarubbo
2020-04-08 9:47 Agostino Sarubbo
2020-04-07 20:43 Anthony G. Basile
2019-12-26 12:56 Georgy Yakovlev
2018-09-05 10:14 Jeroen Roovers
2018-09-05 10:14 Jeroen Roovers
2018-04-21 11:40 Mikle Kolyada
2018-04-05 23:19 Thomas Deutschmann
2018-04-01 17:41 Aaron Bauman
2018-03-31 14:56 Anthony G. Basile
2018-03-31 14:43 Anthony G. Basile
2018-03-31 14:28 Anthony G. Basile
2018-03-31 14:12 Anthony G. Basile
2017-11-18 22:21 Anthony G. Basile
2017-11-17 16:20 Anthony G. Basile
2017-08-26 11:29 Anthony G. Basile
2017-05-11 3:19 Robin H. Johnson
2015-10-24 17:16 Anthony G. Basile
2015-10-24 17:09 Mikle Kolyada
2015-10-17 11:18 Markus Meier
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=1586341062.7b87bbe15b4968be5f7e5d6cc44d9713e0269415.ago@gentoo \
--to=ago@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