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

commit:     f9260e0d0c6e91003eae031115e739c375343069
Author:     Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Sun Sep 30 15:16:12 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=f9260e0d

dev-perl/Expect: stable 1.350.0 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/Expect/Expect-1.350.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-perl/Expect/Expect-1.350.0.ebuild b/dev-perl/Expect/Expect-1.350.0.ebuild
index 930484b50b0..86743e4ed91 100644
--- a/dev-perl/Expect/Expect-1.350.0.ebuild
+++ b/dev-perl/Expect/Expect-1.350.0.ebuild
@@ -11,7 +11,7 @@ inherit perl-module
 DESCRIPTION="Expect for Perl"
 
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sparc ~x86 ~amd64-fbsd"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 sparc ~x86 ~amd64-fbsd"
 IUSE="test minimal"
 
 RDEPEND="


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

Thread overview: 43+ 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 --
2024-07-10  4:21 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Expect/ Ionen Wolkens
2024-06-14  1:50 Sam James
2024-06-09 21:21 Sam James
2024-06-09 21:21 Sam James
2024-05-02  1:36 Sam James
2021-10-24 14:46 Andreas K. Hüttel
2020-08-17  8:41 Fabian Groffen
2019-05-05 19:39 Mikle Kolyada
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-09-07 23:28 Kent Fredric
2018-06-09 19:42 Mikle Kolyada
2018-06-08  2:11 Kent Fredric
2018-04-20  9:23 Mart Raudsepp
2018-03-28  4:09 Matt Turner
2018-02-22 19:41 Michał Górny
2018-01-20 18:04 Tobias Klausmann
2018-01-10  6:19 Markus Meier
2017-12-21  5:45 Markus Meier
2017-11-24 20:26 Sergei Trofimovich
2017-11-23 23:52 Matt Turner
2017-11-23 23:06 Sergei Trofimovich
2017-11-20 22:03 Sergei Trofimovich
2017-11-20 10:16 Jeroen Roovers
2017-11-10 17:00 Matt Turner
2017-11-07 22:44 Sergei Trofimovich
2017-11-07 22:44 Sergei Trofimovich
2017-11-07 22:44 Sergei Trofimovich
2017-05-22  3:11 Kent Fredric
2016-12-08 19:09 Kent Fredric
2016-01-14 19:33 Andreas Hüttel
2016-01-14 17:06 Agostino Sarubbo
2015-10-10 14:46 Mikle Kolyada
2015-10-10 14:45 Mikle Kolyada
2015-10-10 14:43 Mikle Kolyada
2015-10-05  9:28 Patrice Clement
2015-10-04  8:03 Jeroen Roovers
2015-09-27 13:09 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.f9260e0d0c6e91003eae031115e739c375343069.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