public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brian Evans" <grknight@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-PEAR/
Date: Wed, 22 Feb 2017 20:42:56 +0000 (UTC)	[thread overview]
Message-ID: <1487796048.c29342029ee3f641c635b22cef245908a30c4f76.grknight@gentoo> (raw)

commit:     c29342029ee3f641c635b22cef245908a30c4f76
Author:     Brian Evans <grknight <AT> gentoo <DOT> org>
AuthorDate: Wed Feb 22 20:40:48 2017 +0000
Commit:     Brian Evans <grknight <AT> gentoo <DOT> org>
CommitDate: Wed Feb 22 20:40:48 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c2934202

dev-php/PEAR-PEAR: Stable all arches under ALLARCHES policy wrt bug 609552

Package-Manager: Portage-2.3.3, Repoman-2.3.1

 dev-php/PEAR-PEAR/PEAR-PEAR-1.10.1-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-php/PEAR-PEAR/PEAR-PEAR-1.10.1-r1.ebuild b/dev-php/PEAR-PEAR/PEAR-PEAR-1.10.1-r1.ebuild
index c7f6d07843..373adebabe 100644
--- a/dev-php/PEAR-PEAR/PEAR-PEAR-1.10.1-r1.ebuild
+++ b/dev-php/PEAR-PEAR/PEAR-PEAR-1.10.1-r1.ebuild
@@ -11,7 +11,7 @@ DESCRIPTION="PEAR Base System"
 HOMEPAGE="http://pear.php.net/package/${MY_PN}"
 SRC_URI="http://pear.php.net/get/${MY_P}.tgz"
 LICENSE="MIT"
-KEYWORDS="alpha amd64 ~arm hppa ~ia64 ~ppc ~ppc64 ~s390 ~sh ~sparc x86 ~amd64-linux ~x86-linux ~x64-macos ~x86-macos"
+KEYWORDS="alpha amd64 arm hppa ia64 ppc ppc64 ~s390 ~sh sparc x86 ~amd64-linux ~x86-linux ~x64-macos ~x86-macos"
 SLOT="0"
 IUSE=""
 


             reply	other threads:[~2017-02-22 20:43 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 20:42 Brian Evans [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-11 19:26 [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-PEAR/ Michael Orlitzky
2024-06-11 19:26 Michael Orlitzky
2021-08-11 12:50 Brian Evans
2021-01-22 13:46 Brian Evans
2021-01-21 22:32 Sam James
2021-01-21 15:28 Brian Evans
2020-06-02 13:57 Brian Evans
2020-04-10  9:48 Sergei Trofimovich
2019-08-11 11:20 David Seifert
2019-03-20 20:27 Aaron Bauman
2019-03-14 20:04 Brian Evans
2018-12-06 15:25 Brian Evans
2018-09-19 12:47 Brian Evans
2018-09-19 12:47 Brian Evans
2018-09-19  8:42 Sergei Trofimovich
2018-08-22 20:20 Brian Evans
2018-01-27  0:14 Michael Orlitzky
2018-01-26 19:32 Michael Orlitzky
2018-01-26 19:32 Michael Orlitzky
2018-01-22  7:45 Sergei Trofimovich
2018-01-21 10:28 Sergei Trofimovich
2018-01-01 20:09 Sergei Trofimovich
2017-11-05 23:54 Michael Orlitzky
2017-11-05 23:54 Michael Orlitzky
2017-11-05 23:30 Michael Orlitzky
2017-08-12 22:40 Sergei Trofimovich
2017-08-10 22:19 Sergei Trofimovich
2017-07-01 10:26 Sergei Trofimovich
2017-06-27 13:13 Brian Evans
2017-04-15 12:24 Jeroen Roovers
2017-04-05 13:23 Michael Weber
2017-03-21  3:42 Michael Orlitzky
2017-03-21  3:15 Michael Orlitzky
2017-03-03  3:28 Brian Evans
2017-02-28 17:05 Brian Evans
2017-02-28 16:28 Brian Evans
2017-02-21 12:05 Tobias Klausmann
2017-02-21  6:11 Jeroen Roovers
2017-02-20 20:53 Brian Evans
2017-02-19 13:33 Agostino Sarubbo
2017-02-19 13:11 Agostino Sarubbo
2017-01-29 16:59 Fabian Groffen
2017-01-07 14:22 Michael Orlitzky
2015-12-07  2:53 Brian Evans

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=1487796048.c29342029ee3f641c635b22cef245908a30c4f76.grknight@gentoo \
    --to=grknight@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