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/itstool/
Date: Mon, 30 Dec 2019 15:30:32 +0000 (UTC)	[thread overview]
Message-ID: <1577719812.ff1b784fb3d01073aecd0cbc6e6b9acbeeab5500.ago@gentoo> (raw)

commit:     ff1b784fb3d01073aecd0cbc6e6b9acbeeab5500
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Mon Dec 30 15:30:12 2019 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Mon Dec 30 15:30:12 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ff1b784f

dev-util/itstool: s390 stable wrt bug #683226

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

 dev-util/itstool/itstool-2.0.6.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-util/itstool/itstool-2.0.6.ebuild b/dev-util/itstool/itstool-2.0.6.ebuild
index 7d0233962c8..13079e49833 100644
--- a/dev-util/itstool/itstool-2.0.6.ebuild
+++ b/dev-util/itstool/itstool-2.0.6.ebuild
@@ -15,7 +15,7 @@ SRC_URI="http://files.itstool.org/itstool/${P}.tar.bz2"
 # files in /usr/share/itstool/its are under a special exception || GPL-3+
 LICENSE="GPL-3+"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh sparc ~x86 ~x86-linux"
+KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ia64 ~m68k ~mips ~ppc ~ppc64 s390 ~sh sparc ~x86 ~x86-linux"
 IUSE=""
 
 REQUIRED_USE="${PYTHON_REQUIRED_USE}"


             reply	other threads:[~2019-12-30 15:30 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-30 15:30 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-05  1:43 [gentoo-commits] repo/gentoo:master commit in: dev-util/itstool/ Sam James
2024-05-06  7:09 Mart Raudsepp
2024-05-01  5:28 Joonas Niilola
2024-04-09 22:46 Sam James
2024-04-07  9:14 Arthur Zamarin
2024-04-07  6:21 Arthur Zamarin
2024-04-06 21:07 Arthur Zamarin
2024-01-23 20:15 Arthur Zamarin
2024-01-23  5:32 Sam James
2024-01-20  9:07 Sam James
2024-01-20  9:07 Sam James
2024-01-20  9:07 Sam James
2024-01-20  9:07 Sam James
2024-01-20  9:07 Sam James
2024-01-20  9:07 Sam James
2022-09-07  7:52 Michał Górny
2022-05-26  3:52 WANG Xuerui
2022-03-18 14:43 Arthur Zamarin
2022-03-15 20:54 Matt Turner
2022-03-08 12:32 Sam James
2021-12-18 23:39 Matt Turner
2021-10-27 17:54 Arthur Zamarin
2021-10-27 17:54 Arthur Zamarin
2020-12-19  8:19 Fabian Groffen
2020-12-14 23:04 Mike Gilbert
2020-08-31 14:26 Yixun Lan
2020-07-02 12:56 Fabian Groffen
2020-05-30 11:00 Fabian Groffen
2020-05-12  6:53 Fabian Groffen
2020-03-29 11:03 Mart Raudsepp
2020-03-29 10:06 Sergei Trofimovich
2020-02-09 16:25 Michał Górny
2020-01-02  8:40 Sergei Trofimovich
2020-01-01 12:53 Agostino Sarubbo
2019-12-30 16:12 Agostino Sarubbo
2019-12-30 15:53 Agostino Sarubbo
2019-12-30 15:33 Agostino Sarubbo
2019-12-30 14:51 Agostino Sarubbo
2019-12-30 12:57 Agostino Sarubbo
2019-12-29 21:02 Aaron Bauman
2019-12-29 20:03 Sergei Trofimovich
2019-12-04 16:37 Aaron Bauman
2019-11-17 14:17 Mart Raudsepp
2015-11-26 10:51 Gilles Dartiguelongue

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=1577719812.ff1b784fb3d01073aecd0cbc6e6b9acbeeab5500.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