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-perl/Net-DNS-SEC/
Date: Mon, 20 Aug 2018 03:54:19 +0000 (UTC)	[thread overview]
Message-ID: <1534737233.8cc37be4fe25febdcb1ea10be7dbdbc90bd9d193.zlogene@gentoo> (raw)

commit:     8cc37be4fe25febdcb1ea10be7dbdbc90bd9d193
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 20 03:53:53 2018 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Mon Aug 20 03:53:53 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8cc37be4

dev-perl/Net-DNS-SEC: Add ~s390 keyword wrt bug #639714

Package-Manager: Portage-2.3.40, Repoman-2.3.9

 dev-perl/Net-DNS-SEC/Net-DNS-SEC-1.30.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-perl/Net-DNS-SEC/Net-DNS-SEC-1.30.0.ebuild b/dev-perl/Net-DNS-SEC/Net-DNS-SEC-1.30.0.ebuild
index 347a6d49d63..b234e40acc1 100644
--- a/dev-perl/Net-DNS-SEC/Net-DNS-SEC-1.30.0.ebuild
+++ b/dev-perl/Net-DNS-SEC/Net-DNS-SEC-1.30.0.ebuild
@@ -10,7 +10,7 @@ inherit perl-module
 DESCRIPTION="DNSSEC extensions to Net::DNS"
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm hppa ~ia64 ~mips ppc ppc64 sparc x86"
+KEYWORDS="~alpha ~amd64 ~arm hppa ~ia64 ~mips ppc ppc64 ~s390 sparc x86"
 IUSE="test"
 
 RDEPEND="


             reply	other threads:[~2018-08-20  3:54 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20  3:54 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-04 16:13 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Net-DNS-SEC/ Arthur Zamarin
2023-11-04 10:50 Sam James
2023-09-16  9:27 Sam James
2023-07-27 10:22 WANG Xuerui
2023-06-21  9:12 Arthur Zamarin
2023-06-21  9:12 Arthur Zamarin
2023-06-21  8:18 Arthur Zamarin
2023-06-21  8:18 Sam James
2023-06-21  8:18 Sam James
2023-06-21  8:17 Arthur Zamarin
2023-06-21  8:17 Arthur Zamarin
2023-06-02 22:35 Sam James
2022-12-18 12:45 Sam James
2022-12-18 12:45 Sam James
2022-12-18 12:26 Sam James
2022-12-18 11:44 Sam James
2022-12-18 11:41 Sam James
2022-12-18 11:41 Sam James
2022-11-15  8:46 Sam James
2022-05-15  8:09 Michał Górny
2022-02-19 12:02 Arthur Zamarin
2022-02-19 12:02 Arthur Zamarin
2022-02-19  9:05 Arthur Zamarin
2022-02-19  8:04 Arthur Zamarin
2022-02-19  7:19 Arthur Zamarin
2022-02-19  3:41 Sam James
2022-02-19  3:02 Sam James
2021-11-21 11:24 Andreas K. Hüttel
2021-11-21 11:24 Andreas K. Hüttel
2021-08-26 14:55 Sam James
2021-08-26 14:52 Sam James
2021-08-25 16:26 Sam James
2021-08-25  5:40 Agostino Sarubbo
2021-08-25  5:25 Agostino Sarubbo
2021-07-15 22:18 Sergei Trofimovich
2021-07-13 20:05 Sam James
2021-07-12  6:41 Sam James
2021-07-12  1:18 Sam James
2021-07-12  1:16 Sam James
2021-07-12  1:06 Sam James
2021-07-11 21:59 Andreas K. Hüttel
2020-07-18  5:07 Kent Fredric
2020-05-22 19:22 Robin H. Johnson
2020-04-15 12:29 Kent Fredric
2019-07-29 20:02 Aaron Bauman
2019-04-01 19:33 Andreas Sturmlechner
2018-10-27 12:31 Fabian Groffen
2018-10-14 13:29 Mikle Kolyada
2018-09-08  5:30 Mikle Kolyada
2018-08-24 19:37 Markus Meier
2018-07-27  7:12 Sergei Trofimovich
2018-07-23  6:19 Sergei Trofimovich
2018-07-22  9:01 Sergei Trofimovich
2017-12-05 15:10 Kent Fredric
2017-11-24 22:40 Sergei Trofimovich
2017-11-24 22:25 Sergei Trofimovich
2017-11-24  6:15 Markus Meier
2017-11-09  0:07 Matt Turner
2017-11-07 22:52 Sergei Trofimovich
2017-10-29 10:45 Sergei Trofimovich
2017-09-19 19:29 Sergei Trofimovich
2017-06-29  8:06 Agostino Sarubbo
2017-05-25 20:04 Michael Weber
2017-04-05 10:50 Michael Weber
2017-03-15 18:54 Matt Turner
2017-02-20 17:51 Markus Meier
2017-02-05  1:45 Jeroen Roovers
2017-01-26 16:08 Tobias Klausmann
2016-03-30 23:19 Andreas Hüttel
2015-12-26 12:53 Andreas Hüttel

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=1534737233.8cc37be4fe25febdcb1ea10be7dbdbc90bd9d193.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