From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Net-LibIDN2/
Date: Tue, 14 Apr 2020 15:45:52 +0000 (UTC) [thread overview]
Message-ID: <1586879094.0028adb235f88445970fb29275cae809cc75d054.ago@gentoo> (raw)
commit: 0028adb235f88445970fb29275cae809cc75d054
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Tue Apr 14 15:44:54 2020 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Tue Apr 14 15:44:54 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0028adb2
dev-perl/Net-LibIDN2: ppc64 stable wrt bug #717060
Package-Manager: Portage-2.3.89, Repoman-2.3.20
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
dev-perl/Net-LibIDN2/Net-LibIDN2-1.0.0-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-perl/Net-LibIDN2/Net-LibIDN2-1.0.0-r1.ebuild b/dev-perl/Net-LibIDN2/Net-LibIDN2-1.0.0-r1.ebuild
index a2a922a4fc8..62490e701bb 100644
--- a/dev-perl/Net-LibIDN2/Net-LibIDN2-1.0.0-r1.ebuild
+++ b/dev-perl/Net-LibIDN2/Net-LibIDN2-1.0.0-r1.ebuild
@@ -9,7 +9,7 @@ inherit perl-module
DESCRIPTION="Perl bindings for GNU Libidn2"
SLOT="0"
-KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 sparc x86 ~ppc-aix ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~mips ~ppc ppc64 ~s390 sparc x86 ~ppc-aix ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
IUSE="test"
RESTRICT="!test? ( test )"
next reply other threads:[~2020-04-14 15:45 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 15:45 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-25 4:10 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Net-LibIDN2/ Sam James
2024-06-25 4:07 Sam James
2024-06-25 3:56 Sam James
2024-06-25 3:56 Sam James
2024-05-25 7:35 Sam James
2024-05-22 1:44 Sam James
2023-06-21 9:12 Arthur Zamarin
2023-06-21 8:28 Arthur Zamarin
2023-06-21 8:21 Arthur Zamarin
2023-06-21 8:19 Arthur Zamarin
2023-06-21 8:19 Arthur Zamarin
2023-06-21 8:18 Sam James
2023-06-21 8:18 Sam James
2023-03-14 2:09 Sam James
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:37 Agostino Sarubbo
2021-08-25 5:26 Agostino Sarubbo
2021-07-15 18:14 Andreas K. Hüttel
2021-07-15 18:14 Andreas K. Hüttel
2021-07-15 18:14 Andreas K. Hüttel
2020-07-06 2:51 Matt Turner
2020-07-05 21:21 Kent Fredric
2020-04-15 7:08 Agostino Sarubbo
2020-04-14 14:06 Agostino Sarubbo
2020-04-14 14:03 Agostino Sarubbo
2020-04-14 12:59 Agostino Sarubbo
2020-04-12 11:39 Mart Raudsepp
2019-04-01 19:33 Andreas Sturmlechner
2019-01-07 0:33 Thomas Deutschmann
2018-10-27 12:31 Fabian Groffen
2018-08-20 3:54 Mikle Kolyada
2018-04-28 6:02 Matt Turner
2018-03-26 5:28 Matt Turner
2017-12-25 11:42 Markus Meier
2017-12-21 13:40 Sergei Trofimovich
2017-12-09 11:31 Sergei Trofimovich
2017-12-08 23:31 Sergei Trofimovich
2017-12-05 8:45 Sergei Trofimovich
2017-12-04 22:07 Sergei Trofimovich
2017-12-04 1:46 Kent Fredric
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=1586879094.0028adb235f88445970fb29275cae809cc75d054.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