public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/cucumber-wire/
Date: Wed,  5 Jun 2019 07:28:02 +0000 (UTC)	[thread overview]
Message-ID: <1559719608.350b7fe4335654c2bb2edfb72e195e20dad90574.ago@gentoo> (raw)

commit:     350b7fe4335654c2bb2edfb72e195e20dad90574
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Wed Jun  5 07:26:48 2019 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Wed Jun  5 07:26:48 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=350b7fe4

dev-util/cucumber-wire: ia64 stable wrt bug #684076

Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
Package-Manager: Portage-2.3.66, Repoman-2.3.11
RepoMan-Options: --include-arches="ia64"

 dev-util/cucumber-wire/cucumber-wire-0.0.1-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-util/cucumber-wire/cucumber-wire-0.0.1-r1.ebuild b/dev-util/cucumber-wire/cucumber-wire-0.0.1-r1.ebuild
index beb6ecc0bf3..8da48ce7023 100644
--- a/dev-util/cucumber-wire/cucumber-wire-0.0.1-r1.ebuild
+++ b/dev-util/cucumber-wire/cucumber-wire-0.0.1-r1.ebuild
@@ -14,7 +14,7 @@ DESCRIPTION="Executable feature scenarios"
 HOMEPAGE="https://github.com/aslakhellesoy/cucumber/wikis"
 LICENSE="Ruby"
 
-KEYWORDS="alpha amd64 arm ~arm64 hppa ~ia64 ppc ppc64 s390 sparc x86"
+KEYWORDS="alpha amd64 arm ~arm64 hppa ia64 ppc ppc64 s390 sparc x86"
 SLOT="0"
 IUSE="test"
 


             reply	other threads:[~2019-06-05  7:28 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05  7:28 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-11  7:07 [gentoo-commits] repo/gentoo:master commit in: dev-util/cucumber-wire/ Hans de Graaff
2023-04-13  3:03 Sam James
2022-07-03  9:51 Hans de Graaff
2022-05-22  6:23 Agostino Sarubbo
2022-05-22  6:15 Agostino Sarubbo
2022-05-21  8:27 Agostino Sarubbo
2022-05-21  8:26 Agostino Sarubbo
2022-05-21  8:25 Agostino Sarubbo
2022-05-20  9:02 Agostino Sarubbo
2022-05-20  9:00 Agostino Sarubbo
2022-03-19 12:00 Hans de Graaff
2022-01-16  7:34 Hans de Graaff
2021-11-24  7:29 Hans de Graaff
2021-11-23 16:09 Sam James
2021-10-16  7:46 Hans de Graaff
2021-10-16  7:46 Hans de Graaff
2021-10-11  0:45 Sam James
2021-10-10 21:48 Sam James
2021-10-10 20:53 Sam James
2021-10-10 20:48 Sam James
2021-08-28  6:46 Hans de Graaff
2021-08-15  7:41 Hans de Graaff
2021-08-10  5:24 Hans de Graaff
2021-08-02 21:48 Marek Szuba
2021-07-30  8:30 Hans de Graaff
2021-07-26  5:22 Sam James
2021-07-26  5:22 Sam James
2021-07-25  3:23 Sam James
2021-07-23  6:24 Hans de Graaff
2021-07-14  9:20 Hans de Graaff
2020-12-15  2:37 Matt Turner
2020-11-06  3:21 Sam James
2020-07-11  9:28 Hans de Graaff
2019-06-05 17:56 Hans de Graaff
2019-05-04  7:49 Hans de Graaff
2019-05-02 21:38 Mikle Kolyada
2019-04-28 20:12 Mikle Kolyada
2019-04-27 19:20 Sergei Trofimovich
2019-04-27 16:25 Sergei Trofimovich
2019-04-27 16:03 Sergei Trofimovich
2019-04-26 20:54 Mikle Kolyada
2019-04-24 17:02 Sergei Trofimovich
2019-04-23 19:33 Mikle Kolyada
2018-12-27  2:57 Matt Turner
2018-12-27  2:57 Matt Turner
2018-06-18 18:07 Tobias Klausmann
2018-05-22 16:33 Hans de Graaff
2018-04-08 23:44 Matt Turner
2018-03-22 20:23 Jeroen Roovers
2018-03-18 22:38 Sergei Trofimovich
2018-03-18 19:59 Markus Meier
2018-03-06 22:28 Sergei Trofimovich
2017-12-29 17:41 Sergei Trofimovich
2017-12-28 18:45 Thomas Deutschmann
2017-12-27 20:06 Sergei Trofimovich
2017-10-01  0:56 Thomas Deutschmann
2017-09-02  6:53 Hans de Graaff
2017-08-22  9:19 Sergei Trofimovich
2017-02-27 17:01 Michael Weber
2017-02-14  0:36 Michael Weber
2016-09-01 19:49 Hans de Graaff
2016-07-26  5:28 Hans de Graaff
2016-07-26  5:28 Hans de Graaff

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=1559719608.350b7fe4335654c2bb2edfb72e195e20dad90574.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