From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Net-DNS-SEC/
Date: Fri, 27 Jul 2018 07:12:20 +0000 (UTC) [thread overview]
Message-ID: <1532675386.b44f1877a64b11b3e5b07d8234f49e8764cda982.slyfox@gentoo> (raw)
commit: b44f1877a64b11b3e5b07d8234f49e8764cda982
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 27 07:09:46 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Fri Jul 27 07:09:46 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b44f1877
dev-perl/Net-DNS-SEC: stable 1.30.0 for ppc64, bug #661724
Bug: https://bugs.gentoo.org/661724
Package-Manager: Portage-2.3.43, Repoman-2.3.10
RepoMan-Options: --include-arches="ppc64"
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 cd218a3a8c3..347a6d49d63 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 sparc x86"
IUSE="test"
RDEPEND="
next reply other threads:[~2018-07-27 7:12 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 7:12 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-14 2:01 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Net-DNS-SEC/ Sam James
2024-11-14 2:01 Sam James
2024-11-14 2:01 Sam James
2024-10-11 3:39 Sam James
2023-11-04 16:13 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-08-20 3:54 Mikle Kolyada
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=1532675386.b44f1877a64b11b3e5b07d8234f49e8764cda982.slyfox@gentoo \
--to=slyfox@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