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/
Date: Sun, 26 Aug 2018 16:47:07 +0000 (UTC)	[thread overview]
Message-ID: <1535302018.6a2c1de70a2f0015f066f075f070f207fbd1b04d.slyfox@gentoo> (raw)

commit:     6a2c1de70a2f0015f066f075f070f207fbd1b04d
Author:     Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Sun Aug 26 16:01:40 2018 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sun Aug 26 16:46:58 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6a2c1de7

dev-perl/DateTime: keyworded 1.440.0 for sparc, bug #652718

Package-Manager: Portage-2.3.40, Repoman-2.3.9
RepoMan-Options: --include-arches="sparc"

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

diff --git a/dev-perl/DateTime/DateTime-1.440.0.ebuild b/dev-perl/DateTime/DateTime-1.440.0.ebuild
index 05a1fbef728..3edd663eb88 100644
--- a/dev-perl/DateTime/DateTime-1.440.0.ebuild
+++ b/dev-perl/DateTime/DateTime-1.440.0.ebuild
@@ -11,7 +11,7 @@ DESCRIPTION="A date and time object"
 
 LICENSE="Artistic-2"
 SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~ia64 ~mips ~ppc ~ppc64 ~s390 ~x86 ~ppc-aix ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~x86-solaris"
+KEYWORDS="~amd64 ~arm ~arm64 ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sparc ~x86 ~ppc-aix ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~x86-solaris"
 IUSE="test"
 
 CONFLICTS="


             reply	other threads:[~2018-08-26 16:47 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-26 16:47 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-14  0:43 [gentoo-commits] repo/gentoo:master commit in: dev-perl/DateTime/ Sam James
2024-05-02  1:36 Sam James
2024-01-23  5:43 Sam James
2024-01-10 15:03 Sam James
2023-12-31  3:49 Sam James
2023-11-13  4:35 Sam James
2023-08-02 21:06 Sam James
2023-06-21  7:35 Sam James
2021-08-13  1:05 Sam James
2021-08-06 12:16 Sam James
2021-08-03 11:05 Sam James
2021-08-02  3:22 Sam James
2021-08-01 10:42 Sam James
2021-05-17  7:49 Agostino Sarubbo
2021-05-16 23:44 Sam James
2021-05-16 19:57 Sam James
2021-05-16 14:55 Sam James
2021-05-16 14:44 Sam James
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-18  9:29 Kent Fredric
2020-07-25  9:07 Kent Fredric
2020-04-12 18:27 Sergei Trofimovich
2020-04-12  9:44 Sergei Trofimovich
2019-03-20 19:37 Sergei Trofimovich
2018-12-08 12:51 Mikle Kolyada
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-08-04  0:29 Mikle Kolyada
2018-04-15 21:10 Sergei Trofimovich
2018-04-11 18:50 Markus Meier
2018-04-07 20:31 Sergei Trofimovich
2018-04-07 20:27 Sergei Trofimovich
2018-04-07 15:26 Mart Raudsepp
2017-10-19  4:27 Kent Fredric
2017-10-10  6:04 Kent Fredric
2017-03-15 18:54 Matt Turner
2017-03-10 21:04 Matt Turner
2017-02-22 21:45 Markus Meier
2017-02-20 18:02 Markus Meier
2017-01-12 14:21 Jeroen Roovers
2017-01-05  3:41 Kent Fredric
2017-01-05  3:41 Kent Fredric
2016-12-04 16:43 Michael Palimaka
2016-11-24 17:45 Tobias Klausmann
2016-11-17  6:01 Kent Fredric
2016-11-17  6:01 Kent Fredric
2016-11-11 20:22 Kent Fredric
2016-11-11  3:46 Kent Fredric
2016-01-24 12:11 Andreas Hüttel
2016-01-24  7:39 Jeroen Roovers
2016-01-17 19:04 Mikle Kolyada
2016-01-17 17:02 Agostino Sarubbo
2016-01-12 20:14 Markus Meier
2016-01-10 10:34 Agostino Sarubbo
2016-01-06 13:34 Agostino Sarubbo
2016-01-02 18:53 Agostino Sarubbo
2016-01-01 13:45 Andreas Hüttel
2016-01-01 13:45 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=1535302018.6a2c1de70a2f0015f066f075f070f207fbd1b04d.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