From: "Markus Meier" <maekke@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/perl-Parse-CPAN-Meta/
Date: Sat, 17 Dec 2016 06:54:45 +0000 (UTC) [thread overview]
Message-ID: <1481957671.6368d3926deec0c224e05f49894f1ec40443b74d.maekke@gentoo> (raw)
commit: 6368d3926deec0c224e05f49894f1ec40443b74d
Author: Markus Meier <maekke <AT> gentoo <DOT> org>
AuthorDate: Sat Dec 17 06:54:31 2016 +0000
Commit: Markus Meier <maekke <AT> gentoo <DOT> org>
CommitDate: Sat Dec 17 06:54:31 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6368d392
virtual/perl-Parse-CPAN-Meta: arm stable, bug #589680
Package-Manager: portage-2.3.3
RepoMan-Options: --include-arches="arm"
.../perl-Parse-CPAN-Meta/perl-Parse-CPAN-Meta-1.441.400.100_rc.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/virtual/perl-Parse-CPAN-Meta/perl-Parse-CPAN-Meta-1.441.400.100_rc.ebuild b/virtual/perl-Parse-CPAN-Meta/perl-Parse-CPAN-Meta-1.441.400.100_rc.ebuild
index 2a5d70e..19dd27d 100644
--- a/virtual/perl-Parse-CPAN-Meta/perl-Parse-CPAN-Meta-1.441.400.100_rc.ebuild
+++ b/virtual/perl-Parse-CPAN-Meta/perl-Parse-CPAN-Meta-1.441.400.100_rc.ebuild
@@ -10,7 +10,7 @@ SRC_URI=""
LICENSE=""
SLOT="0"
-KEYWORDS="alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~ppc-aix ~amd64-fbsd ~x86-fbsd ~x64-freebsd ~x86-freebsd ~x86-interix ~amd64-linux ~arm-linux ~ia64-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 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~ppc-aix ~amd64-fbsd ~x86-fbsd ~x64-freebsd ~x86-freebsd ~x86-interix ~amd64-linux ~arm-linux ~ia64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
IUSE=""
RDEPEND="
next reply other threads:[~2016-12-17 6:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-17 6:54 Markus Meier [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-26 19:21 [gentoo-commits] repo/gentoo:master commit in: virtual/perl-Parse-CPAN-Meta/ Andreas K. Hüttel
2023-04-22 12:08 Sam James
2022-05-25 19:26 Andreas K. Hüttel
2020-08-06 20:22 Andreas K. Hüttel
2019-05-17 18:44 Andreas K. Hüttel
2019-05-04 20:12 Andreas K. Hüttel
2019-02-16 8:46 Mikle Kolyada
2019-01-08 22:01 Mart Raudsepp
2019-01-06 11:34 Mikle Kolyada
2019-01-06 10:33 Mikle Kolyada
2019-01-06 10:23 Mikle Kolyada
2019-01-06 10:14 Mikle Kolyada
2019-01-06 8:32 Sergei Trofimovich
2019-01-05 20:46 Matt Turner
2019-01-05 19:45 Sergei Trofimovich
2019-01-05 12:30 Mikle Kolyada
2019-01-05 7:59 Mikle Kolyada
2019-01-04 13:47 Mikle Kolyada
2017-05-30 22:21 Sergei Trofimovich
2017-04-28 13:14 Agostino Sarubbo
2017-04-16 8:07 Jeroen Roovers
2017-04-15 11:25 Agostino Sarubbo
2017-04-15 11:20 Agostino Sarubbo
2017-04-05 21:29 Michael Weber
2017-02-24 5:45 Mike Frysinger
2017-01-29 20:46 Fabian Groffen
2017-01-18 10:02 Agostino Sarubbo
2017-01-18 9:50 Agostino Sarubbo
2016-12-23 0:22 Thomas Deutschmann
2016-12-17 8:32 Aaron Bauman
2016-12-12 13:34 Tobias Klausmann
2016-11-23 10:54 Kent Fredric
2016-11-23 10:54 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=1481957671.6368d3926deec0c224e05f49894f1ec40443b74d.maekke@gentoo \
--to=maekke@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