public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/DateTime-TimeZone/
Date: Sat,  7 Apr 2018 20:27:48 +0000 (UTC)	[thread overview]
Message-ID: <1523132787.a0943b80622bc1a29583207e44cc2c7bc1ca8b3a.slyfox@gentoo> (raw)

commit:     a0943b80622bc1a29583207e44cc2c7bc1ca8b3a
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Apr  7 20:26:27 2018 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Apr  7 20:26:27 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a0943b80

dev-perl/DateTime-TimeZone: keyworded 2.130.0 for ppc64, bug #652718

Package-Manager: Portage-2.3.28, Repoman-2.3.9
RepoMan-Options: --include-arches="ppc64"

 dev-perl/DateTime-TimeZone/DateTime-TimeZone-2.130.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-perl/DateTime-TimeZone/DateTime-TimeZone-2.130.0.ebuild b/dev-perl/DateTime-TimeZone/DateTime-TimeZone-2.130.0.ebuild
index 2ca9c6c8499..36c6434e9a1 100644
--- a/dev-perl/DateTime-TimeZone/DateTime-TimeZone-2.130.0.ebuild
+++ b/dev-perl/DateTime-TimeZone/DateTime-TimeZone-2.130.0.ebuild
@@ -10,7 +10,7 @@ inherit perl-module
 DESCRIPTION="Time zone object base class and factory"
 
 SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~mips ~x86 ~ppc-aix ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~x86-solaris"
+KEYWORDS="~amd64 ~arm64 ~mips ~ppc64 ~x86 ~ppc-aix ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~x86-solaris"
 IUSE="test"
 
 RDEPEND="


             reply	other threads:[~2018-04-07 20:27 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-07 20:27 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-14  2:00 [gentoo-commits] repo/gentoo:master commit in: dev-perl/DateTime-TimeZone/ Sam James
2024-10-14  3:50 Sam James
2023-06-21  9:12 Arthur Zamarin
2023-06-21  9:12 Arthur Zamarin
2023-06-21  9:12 Arthur Zamarin
2023-06-21  8:19 Arthur Zamarin
2023-06-21  8:18 Sam James
2023-06-21  8:18 Sam James
2023-06-21  8:17 Arthur Zamarin
2023-04-26 14:33 Sam James
2023-04-26 14:29 Sam James
2023-03-24  5:12 Sam James
2022-12-18 19:06 Arthur Zamarin
2022-12-18 11:49 Sam James
2022-12-18 11:41 Sam James
2022-11-18  4:52 Sam James
2021-12-06  8:06 Agostino Sarubbo
2021-12-05  3:15 Sam James
2021-12-05  3:11 Sam James
2021-12-05  3:09 Sam James
2021-12-05  3:08 Sam James
2021-10-20 23:00 Andreas K. Hüttel
2021-10-20 23:00 Andreas K. Hüttel
2021-05-24  0:32 Sam James
2021-05-24  0:32 Sam James
2021-05-24  0:12 Sam James
2021-05-24  0:12 Sam James
2021-05-23 23:05 Agostino Sarubbo
2021-05-23 22:28 Agostino Sarubbo
2021-05-23 12:13 Sergei Trofimovich
2021-05-22 16:20 Andreas K. Hüttel
2021-05-16 11:29 Andreas K. Hüttel
2020-12-27 14:54 Fabian Groffen
2020-12-12  8:40 Kent Fredric
2020-08-31  8:48 Kent Fredric
2020-07-27  9:51 Kent Fredric
2020-04-12 18:27 Sergei Trofimovich
2020-04-12  9:44 Sergei Trofimovich
2018-12-08 12:51 Mikle Kolyada
2018-12-01 15:10 Sergei Trofimovich
2018-11-23 13:06 Agostino Sarubbo
2018-10-18  7:52 Tobias Klausmann
2018-10-16 18:47 Fabian Groffen
2018-10-06 19:34 Matt Turner
2018-09-30 16:08 Sergei Trofimovich
2018-09-07 23:28 Kent Fredric
2018-08-04  0:29 Mikle Kolyada
2018-04-16 19:03 Sergei Trofimovich
2018-04-15 21:10 Sergei Trofimovich
2018-04-11 18:50 Markus Meier
2018-04-07 20:31 Sergei Trofimovich
2018-04-07 15:26 Mart Raudsepp
2017-10-19  8:35 Kent Fredric
2017-03-24 13:07 Kent Fredric
2017-03-24 13:07 Kent Fredric
2017-03-16  3:13 Kent Fredric
2017-03-16  3:13 Kent Fredric
2016-11-12 15:36 Kent Fredric
2016-10-16 15:04 Robin H. Johnson
2016-01-02 19:11 Andreas Hüttel
2016-01-02 17:58 Agostino Sarubbo
2016-01-02 16:15 Andreas Hüttel
2015-09-08 19:43 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=1523132787.a0943b80622bc1a29583207e44cc2c7bc1ca8b3a.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