From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/recaptcha/
Date: Fri, 1 Mar 2019 03:48:50 +0000 (UTC) [thread overview]
Message-ID: <1551410880.04c03080d70a094d2bbb674f9b011b8da1df8a3b.mjo@gentoo> (raw)
commit: 04c03080d70a094d2bbb674f9b011b8da1df8a3b
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 1 03:28:00 2019 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Fri Mar 1 03:28:00 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=04c03080
dev-php/recaptcha: stabilize v1.2.1 on amd64.
I'm not sure what happened on bug 678720... this was supposed to be
stabilized on amd64 already. But in any case, it was stabilized on x86
and marked ALLARCHES. Moreover, I actually use it on amd64. All is well.
Bug: https://bugs.gentoo.org/678720
Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>
Package-Manager: Portage-2.3.51, Repoman-2.3.11
dev-php/recaptcha/recaptcha-1.2.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-php/recaptcha/recaptcha-1.2.1.ebuild b/dev-php/recaptcha/recaptcha-1.2.1.ebuild
index b7ba445b7d3..bcba673ab3c 100644
--- a/dev-php/recaptcha/recaptcha-1.2.1.ebuild
+++ b/dev-php/recaptcha/recaptcha-1.2.1.ebuild
@@ -9,7 +9,7 @@ SRC_URI="https://github.com/google/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="BSD"
SLOT="0"
-KEYWORDS="~amd64 x86"
+KEYWORDS="amd64 x86"
IUSE="examples test"
RDEPEND="dev-lang/php"
next reply other threads:[~2019-03-01 3:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 3:48 Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-09 23:48 [gentoo-commits] repo/gentoo:master commit in: dev-php/recaptcha/ Michael Orlitzky
2023-07-09 18:28 Arthur Zamarin
2022-08-07 17:02 Michael Orlitzky
2020-08-18 23:06 Thomas Deutschmann
2019-03-01 3:48 Michael Orlitzky
2019-03-01 1:14 Thomas Deutschmann
2018-10-12 21:47 Michael Orlitzky
2017-07-23 13:45 Michael Orlitzky
2017-05-14 16:22 Michael Orlitzky
2017-01-09 0:17 Michael Orlitzky
2015-11-12 20:04 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=1551410880.04c03080d70a094d2bbb674f9b011b8da1df8a3b.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