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: dev-python/elasticsearch-curator/
Date: Mon, 25 May 2020 12:18:57 +0000 (UTC)	[thread overview]
Message-ID: <1590409134.23acea3a395ffe7d8c01dca478110bc8ac5e7a9c.zlogene@gentoo> (raw)

commit:     23acea3a395ffe7d8c01dca478110bc8ac5e7a9c
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Mon May 25 12:18:41 2020 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Mon May 25 12:18:54 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=23acea3a

dev-python/elasticsearch-curator: amd64 stable wrt bug #713342

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

 dev-python/elasticsearch-curator/elasticsearch-curator-5.8.1-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/elasticsearch-curator/elasticsearch-curator-5.8.1-r1.ebuild b/dev-python/elasticsearch-curator/elasticsearch-curator-5.8.1-r1.ebuild
index 168a9f59d02..3807417be73 100644
--- a/dev-python/elasticsearch-curator/elasticsearch-curator-5.8.1-r1.ebuild
+++ b/dev-python/elasticsearch-curator/elasticsearch-curator-5.8.1-r1.ebuild
@@ -17,7 +17,7 @@ SRC_URI="https://github.com/elasticsearch/${MY_PN}/archive/v${PV}.tar.gz -> ${P}
 
 LICENSE="Apache-2.0"
 SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
 # tests fail in chroot
 # https://github.com/elastic/elasticsearch/issues/12018
 RESTRICT="test"


             reply	other threads:[~2020-05-25 12:19 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25 12:18 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-09  9:44 [gentoo-commits] repo/gentoo:master commit in: dev-python/elasticsearch-curator/ Sam James
2021-03-09  9:44 Sam James
2020-12-23  1:17 Thomas Deutschmann
2020-12-11 14:51 Michał Górny
2020-12-10 19:31 Thomas Deutschmann
2020-06-30  6:34 Agostino Sarubbo
2020-04-23 13:06 Michał Górny
2020-03-27  8:58 Michał Górny
2019-10-28 14:43 Joonas Niilola
2019-08-16 13:50 Michał Górny
2018-12-17  1:03 Thomas Deutschmann
2018-11-17 14:27 Mikle Kolyada
2018-11-15 15:48 Thomas Deutschmann
2018-10-12  0:57 Thomas Deutschmann
2018-10-12  0:57 Thomas Deutschmann
2018-07-11  8:13 Tony Vroon
2018-05-11  8:35 Michał Górny
2018-05-11  8:35 Michał Górny
2018-04-23 14:32 Aaron Bauman
2018-01-31 22:10 Michał Górny
2018-01-31 22:10 Michał Górny
2017-11-30 14:47 Patrice Clement
2017-11-30 14:47 Patrice Clement
2017-11-13 15:41 Manuel Rüger
2017-11-07 22:59 Patrice Clement
2017-10-29 21:08 Thomas Deutschmann
2017-09-10 21:24 Patrice Clement
2017-09-10 21:24 Patrice Clement
2017-09-10 21:24 Patrice Clement
2017-08-14 21:41 Patrice Clement
2017-08-14 21:41 Patrice Clement
2017-07-08 21:35 Patrice Clement
2017-06-20  5:17 Agostino Sarubbo
2017-06-19 17:03 Agostino Sarubbo
2017-05-24 13:27 Michał Górny
2017-05-19 10:52 Michał Górny
2017-05-18 22:25 Michał Górny
2017-05-17 16:37 Patrick Lauer
2017-02-06 21:14 Göktürk Yüksek
2017-01-26  8:31 Göktürk Yüksek
2017-01-26  8:31 Göktürk Yüksek
2016-12-27 18:44 Göktürk Yüksek
2016-10-28 19:45 Patrick Lauer
2016-10-02 12:59 Göktürk Yüksek
2016-09-29 20:42 Patrice Clement
2016-09-02  5:26 Patrick Lauer
2016-08-16 17:59 Patrice Clement
2016-08-09  9:44 Patrick Lauer
2016-07-08 19:05 Patrice Clement
2016-07-08 19:05 Patrice Clement
2016-03-23 14:59 Patrick Lauer
2016-03-18 13:43 Patrice Clement
2016-03-18 12:23 Ian Delaney
2016-03-17 14:27 Patrick Lauer
2016-02-15 13:16 Patrice Clement
2016-02-15 13:16 Patrice Clement
2016-02-15 13:16 Patrice Clement
2015-11-23 11:32 Ian Delaney
2015-11-12  8:18 Ian Delaney
2015-11-11 14:15 Ian Delaney
2015-09-11  7:53 Justin Lecher
2015-09-10  6:26 Ian Delaney

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=1590409134.23acea3a395ffe7d8c01dca478110bc8ac5e7a9c.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