public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-Exception/
Date: Sun,  5 Nov 2017 23:54:36 +0000 (UTC)	[thread overview]
Message-ID: <1509925978.09ee36520670ea1058ef012fc5aeb137bd8aa2fc.mjo@gentoo> (raw)

commit:     09ee36520670ea1058ef012fc5aeb137bd8aa2fc
Author:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Sun Nov  5 23:35:24 2017 +0000
Commit:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Sun Nov  5 23:52:58 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=09ee3652

dev-php/PEAR-Exception: add ~alpha and ~x86 keywords.

This is pure PHP code, what could possibly go wrong? We need this for
half of the packages in dev-php, and it's been 8 months, so... bam.

Bug: https://bugs.gentoo.org/613380
Package-Manager: Portage-2.3.8, Repoman-2.3.3

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

diff --git a/dev-php/PEAR-Exception/PEAR-Exception-1.0.0.ebuild b/dev-php/PEAR-Exception/PEAR-Exception-1.0.0.ebuild
index ed45b38d93f..42a77744cb2 100644
--- a/dev-php/PEAR-Exception/PEAR-Exception-1.0.0.ebuild
+++ b/dev-php/PEAR-Exception/PEAR-Exception-1.0.0.ebuild
@@ -11,7 +11,7 @@ HOMEPAGE="http://pear.php.net/package/${MY_PN}"
 SRC_URI="http://download.pear.php.net/package/${MY_P}.tgz"
 LICENSE="BSD-2"
 SLOT="0"
-KEYWORDS="~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64"
+KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~x86"
 IUSE="test"
 RDEPEND="dev-lang/php:*
 	!<=dev-php/PEAR-PEAR-1.10.3-r1"


             reply	other threads:[~2017-11-05 23:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-05 23:54 Michael Orlitzky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-26 15:09 [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-Exception/ Andreas Sturmlechner
2023-07-04 10:13 Sam James
2021-03-22 12:58 Brian Evans
2021-03-22 12:58 Brian Evans
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-08-12 22:40 Sergei Trofimovich
2017-08-10 22:19 Sergei Trofimovich
2017-07-01 10:26 Sergei Trofimovich
2017-04-15 12:24 Jeroen Roovers
2017-04-05 13:23 Michael Weber
2017-03-21  3:42 Michael Orlitzky

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=1509925978.09ee36520670ea1058ef012fc5aeb137bd8aa2fc.mjo@gentoo \
    --to=mjo@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