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: sys-cluster/sanlock/
Date: Wed, 17 Apr 2019 11:57:02 +0000 (UTC)	[thread overview]
Message-ID: <1555502203.b4dc3c074834eabb7b79c5622f653ec97374a2f6.zlogene@gentoo> (raw)

commit:     b4dc3c074834eabb7b79c5622f653ec97374a2f6
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Wed Apr 17 11:56:43 2019 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Wed Apr 17 11:56:43 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b4dc3c07

sys-cluster/sanlock: arm stable wrt bug #680850

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

 sys-cluster/sanlock/sanlock-3.6.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-cluster/sanlock/sanlock-3.6.0.ebuild b/sys-cluster/sanlock/sanlock-3.6.0.ebuild
index 91a011b688f..4a32bb16ec0 100644
--- a/sys-cluster/sanlock/sanlock-3.6.0.ebuild
+++ b/sys-cluster/sanlock/sanlock-3.6.0.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://releases.pagure.org/${PN}/${P}.tar.gz"
 
 LICENSE="LGPL-2+ GPL-2 GPL-2+"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~ia64 ~mips ppc ppc64 ~s390 ~sh ~sparc x86"
+KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~mips ppc ppc64 ~s390 ~sh ~sparc x86"
 IUSE="python"
 
 REQUIRED_USE="python? ( ${PYTHON_REQUIRED_USE} )"


             reply	other threads:[~2019-04-17 11:57 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17 11:57 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-31  9:24 [gentoo-commits] repo/gentoo:master commit in: sys-cluster/sanlock/ Pacho Ramos
2024-03-29 18:47 Sam James
2024-03-29 18:47 Sam James
2023-05-29 20:39 Sam James
2023-05-28 19:17 Arthur Zamarin
2023-05-27 10:47 Sam James
2023-05-26 20:06 Arthur Zamarin
2023-05-26 20:06 Arthur Zamarin
2023-05-26 15:16 Sam James
2023-05-26 15:16 Sam James
2023-05-03 11:11 Marc Schiffbauer
2022-09-17 17:34 Andreas Sturmlechner
2022-08-11 10:55 Sam James
2022-06-20 17:46 Arthur Zamarin
2022-06-18 16:57 Agostino Sarubbo
2022-06-18 16:56 Agostino Sarubbo
2022-06-18 16:56 Agostino Sarubbo
2022-06-18 16:55 Agostino Sarubbo
2022-06-18 16:54 Agostino Sarubbo
2022-06-18 16:54 Agostino Sarubbo
2022-05-14  6:21 WANG Xuerui
2022-01-15 23:31 James Le Cuirot
2021-10-19  5:42 Arthur Zamarin
2021-06-11  0:29 Sam James
2021-01-01  2:03 Michał Górny
2020-12-21  9:36 Sergei Trofimovich
2020-12-16 11:12 Sam James
2020-12-05 11:43 Sergei Trofimovich
2020-12-04 18:37 Sergei Trofimovich
2020-12-03  4:26 Sam James
2020-12-03  4:26 Sam James
2020-12-02 23:31 Thomas Deutschmann
2020-08-21 18:06 Marc Schiffbauer
2020-04-08 20:40 Göktürk Yüksek
2020-02-10 21:25 Michał Górny
2019-07-28 10:55 Mikle Kolyada
2019-07-08 13:08 Marc Schiffbauer
2019-07-08 13:08 Marc Schiffbauer
2019-06-11 22:15 Sergei Trofimovich
2019-06-06  6:54 Agostino Sarubbo
2019-06-05 18:14 Sergei Trofimovich
2019-05-02 21:12 Mikle Kolyada
2019-04-28 20:39 Mikle Kolyada
2019-04-16  3:41 Aaron Bauman
2019-04-02  9:11 Mikle Kolyada
2019-04-01 17:21 Thomas Deutschmann
2019-02-12 12:42 Mikle Kolyada
2019-02-12 12:42 Mikle Kolyada
2019-02-12 12:42 Mikle Kolyada
2019-02-12 12:42 Mikle Kolyada
2018-10-26 20:48 Marc Schiffbauer
2018-06-26 20:51 Pacho Ramos
2018-06-06  5:59 Jeroen Roovers
2018-03-26  3:55 Matt Turner
2018-03-17 19:44 Matt Turner
2018-01-02 19:54 Sergei Trofimovich
2017-12-05  8:22 Marc Schiffbauer
2017-07-12  8:13 Sergei Trofimovich
2017-04-20 18:25 Marc Schiffbauer
2017-04-19 11:39 Michael Weber
2017-01-03 15:50 Marc Schiffbauer
2017-01-03  0:42 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=1555502203.b4dc3c074834eabb7b79c5622f653ec97374a2f6.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