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/Error/
Date: Sun, 30 Sep 2018 16:08:11 +0000 (UTC)	[thread overview]
Message-ID: <1538323683.01b9fcbce6b20e4ace8f127e03ce1d4c4ee61760.slyfox@gentoo> (raw)

commit:     01b9fcbce6b20e4ace8f127e03ce1d4c4ee61760
Author:     Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Sun Sep 30 15:15:00 2018 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sun Sep 30 16:08:03 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=01b9fcbc

dev-perl/Error: stable 0.170.250 for sparc, bug #667266

Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
Package-Manager: Portage-2.3.49, Repoman-2.3.10
RepoMan-Options: --include-arches="sparc"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>

 dev-perl/Error/Error-0.170.250.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-perl/Error/Error-0.170.250.ebuild b/dev-perl/Error/Error-0.170.250.ebuild
index f1f5699f6ef..cca5015f4f8 100644
--- a/dev-perl/Error/Error-0.170.250.ebuild
+++ b/dev-perl/Error/Error-0.170.250.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
@@ -11,7 +11,7 @@ DESCRIPTION="Error/exception handling in an OO-ish way"
 
 LICENSE+=" MIT"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~ppc-aix ~x64-cygwin ~amd64-fbsd ~x86-fbsd ~amd64-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 ~x64-cygwin ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
 IUSE="test"
 
 RDEPEND="


             reply	other threads:[~2018-09-30 16:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-30 16:08 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-26  7:45 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Error/ Sam James
2021-10-24 14:46 Andreas K. Hüttel
2021-05-31 17:43 Sergei Trofimovich
2021-05-29 15:33 Sam James
2021-05-29  8:43 Agostino Sarubbo
2021-05-29  8:41 Agostino Sarubbo
2021-05-29  6:09 Sam James
2021-05-28 19:11 Sam James
2020-08-14  6:58 Kent Fredric
2020-04-14  9:53 Kent Fredric
2019-05-04 18:46 Andreas K. Hüttel
2018-12-08 12:51 Mikle Kolyada
2018-12-01 15:10 Sergei Trofimovich
2018-11-23 13:06 Agostino Sarubbo
2018-10-12 11:16 Tobias Klausmann
2018-10-06 21:10 Mart Raudsepp
2018-10-06 19:34 Matt Turner
2018-07-01 14:01 Mikle Kolyada
2017-10-21  3:32 Kent Fredric
2017-03-17 11:12 Michael Haubenwallner
2016-08-04  8:19 Kent Fredric
2016-03-06 22:52 Stephen Klimaszewski
2016-01-05 13:10 Andreas Hüttel
2016-01-05  9:17 Agostino Sarubbo
2016-01-04 23:04 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=1538323683.01b9fcbce6b20e4ace8f127e03ce1d4c4ee61760.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