From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Params-Validate/
Date: Tue, 2 Oct 2018 07:33:35 +0000 (UTC) [thread overview]
Message-ID: <1538465596.b43fd5dd1487e425e6b8940fa595ee69879e1a53.slyfox@gentoo> (raw)
commit: b43fd5dd1487e425e6b8940fa595ee69879e1a53
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Mon Oct 1 23:23:00 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Tue Oct 2 07:33:16 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b43fd5dd
dev-perl/Params-Validate: stable 1.290.0 for ia64, bug #667266
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
Package-Manager: Portage-2.3.50, Repoman-2.3.11
RepoMan-Options: --include-arches="ia64"
dev-perl/Params-Validate/Params-Validate-1.290.0.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-perl/Params-Validate/Params-Validate-1.290.0.ebuild b/dev-perl/Params-Validate/Params-Validate-1.290.0.ebuild
index 44ec02f6051..7b2de905583 100644
--- a/dev-perl/Params-Validate/Params-Validate-1.290.0.ebuild
+++ b/dev-perl/Params-Validate/Params-Validate-1.290.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -12,7 +12,7 @@ DESCRIPTION="Flexible system for validation of method/function call parameters"
LICENSE="Artistic-2"
SLOT="0"
-KEYWORDS="alpha amd64 arm ~arm64 hppa ~ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh sparc x86 ~ppc-aix ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~x86-solaris"
+KEYWORDS="alpha amd64 arm ~arm64 hppa ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh sparc x86 ~ppc-aix ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~x86-solaris"
IUSE="test"
RDEPEND="
next reply other threads:[~2018-10-02 7:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 7:33 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-20 15:07 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Params-Validate/ Ionen Wolkens
2023-08-02 16:54 Sam James
2023-07-24 4:12 Sam James
2023-07-24 4:12 Sam James
2023-07-24 3:59 Sam James
2023-06-19 23:41 Sam James
2021-11-24 16:18 Andreas K. Hüttel
2021-11-17 17:31 Arthur Zamarin
2021-11-17 17:31 Arthur Zamarin
2021-11-04 21:44 Sam James
2021-11-04 21:44 Sam James
2021-11-02 10:20 Sam James
2021-11-02 10:20 Sam James
2021-11-01 2:07 Sam James
2021-07-24 22:00 Andreas K. Hüttel
2020-07-20 20:45 Kent Fredric
2018-10-17 19:03 Fabian Groffen
2018-09-01 19:01 Thomas Deutschmann
2018-08-30 4:44 Markus Meier
2018-08-20 4:40 Matt Turner
2018-07-27 7:12 Sergei Trofimovich
2018-07-27 7:08 Sergei Trofimovich
2018-07-24 0:12 Mikle Kolyada
2017-12-26 8:48 Kent Fredric
2017-05-30 0:19 Kent Fredric
2017-02-14 21:27 Michael Weber
2017-02-03 22:00 Jeroen Roovers
2017-01-29 16:45 Fabian Groffen
2016-08-18 3:01 Kent Fredric
2016-05-26 0:31 Matt Turner
2016-05-19 19:21 Markus Meier
2016-04-13 23:15 Andreas Hüttel
2016-04-13 23:15 Andreas Hüttel
2016-03-16 22:50 Andreas Hüttel
2016-01-01 21:32 Andreas Hüttel
2016-01-01 21:32 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=1538465596.b43fd5dd1487e425e6b8940fa595ee69879e1a53.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