public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/perl-Time-Piece/
Date: Fri,  6 Dec 2019 09:34:50 +0000 (UTC)	[thread overview]
Message-ID: <1575624780.9d693e43d3e4089709f0713af06adf5bb7e53ff8.zlogene@gentoo> (raw)

commit:     9d693e43d3e4089709f0713af06adf5bb7e53ff8
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Fri Dec  6 09:33:00 2019 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Fri Dec  6 09:33:00 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9d693e43

virtual/perl-Time-Piece: amd64 stable wrt bug #698542

Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>

 virtual/perl-Time-Piece/perl-Time-Piece-1.330.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/virtual/perl-Time-Piece/perl-Time-Piece-1.330.0.ebuild b/virtual/perl-Time-Piece/perl-Time-Piece-1.330.0.ebuild
index f277f5930e9..cedec64c873 100644
--- a/virtual/perl-Time-Piece/perl-Time-Piece-1.330.0.ebuild
+++ b/virtual/perl-Time-Piece/perl-Time-Piece-1.330.0.ebuild
@@ -5,7 +5,7 @@ EAPI=6
 
 DESCRIPTION="Virtual for ${PN#perl-}"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~x64-cygwin ~x86-solaris"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~x64-cygwin ~x86-solaris"
 
 RDEPEND="
 	|| ( =dev-lang/perl-5.30* ~perl-core/${PN#perl-}-${PV} )


             reply	other threads:[~2019-12-06  9:34 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06  9:34 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-26 20:02 [gentoo-commits] repo/gentoo:master commit in: virtual/perl-Time-Piece/ Andreas K. Hüttel
2024-03-15 14:58 Matt Turner
2023-09-02 15:34 Sam James
2023-09-02  8:53 Sam James
2023-09-01 19:56 Arthur Zamarin
2023-09-01 19:33 Arthur Zamarin
2023-09-01 17:24 Arthur Zamarin
2023-09-01 14:23 Sam James
2023-06-03 16:31 Andreas K. Hüttel
2023-04-22 13:01 Sam James
2022-05-25 21:16 Andreas K. Hüttel
2022-04-29  2:14 WANG Xuerui
2021-08-06 20:25 Andreas K. Hüttel
2021-05-26  8:13 Sam James
2021-05-24  5:47 Sam James
2021-05-24  5:07 Sam James
2021-05-24  4:42 Sam James
2021-05-24  3:27 Sam James
2021-05-24  2:04 Sam James
2021-05-20  3:21 Sam James
2021-01-06 12:42 Fabian Groffen
2020-12-27 19:00 Fabian Groffen
2020-08-07 16:01 Andreas K. Hüttel
2020-07-23 13:28 Kent Fredric
2020-06-29 15:32 Kent Fredric
2019-12-07 16:56 Aaron Bauman
2019-12-06 10:00 Mikle Kolyada
2019-12-06  9:56 Mikle Kolyada
2019-12-06  9:53 Mikle Kolyada
2019-12-06  9:51 Mikle Kolyada
2019-12-06  9:49 Mikle Kolyada
2019-12-06  9:46 Mikle Kolyada
2019-12-06  9:43 Mikle Kolyada
2019-12-06  9:41 Mikle Kolyada
2019-12-06  9:37 Mikle Kolyada
2019-09-10  0:40 Matt Turner
2019-07-18  0:16 Kent Fredric
2019-05-26  0:28 Aaron Bauman
2019-05-24 14:37 Mikle Kolyada
2019-05-24  8:12 Mikle Kolyada
2019-05-24  7:39 Mikle Kolyada
2019-05-24  6:54 Mikle Kolyada
2019-05-24  6:42 Mikle Kolyada
2019-05-24  6:39 Mikle Kolyada
2019-05-24  6:35 Mikle Kolyada
2019-05-17 20:08 Andreas K. Hüttel
2017-05-30 22:21 Sergei Trofimovich
2017-04-28 13:14 Agostino Sarubbo
2017-04-24 12:44 Tobias Klausmann
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-01-21 14:08 Jeroen Roovers
2016-12-17  7:03 Markus Meier
2016-09-29 13:46 Agostino Sarubbo
2016-09-29 11:01 Agostino Sarubbo
2016-09-29 10:34 Agostino Sarubbo
2016-09-29  9:22 Agostino Sarubbo
2016-09-29  9:06 Agostino Sarubbo
2016-09-14  7:28 Agostino Sarubbo
2016-05-24 15:47 Tobias Klausmann

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=1575624780.9d693e43d3e4089709f0713af06adf5bb7e53ff8.zlogene@gentoo \
    --to=zlogene@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