From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-Auth_SASL/
Date: Thu, 20 Jun 2024 21:46:33 +0000 (UTC) [thread overview]
Message-ID: <1718919939.62e31be6f1e400841384bb0429b9d9c236b2fb15.sam@gentoo> (raw)
commit: 62e31be6f1e400841384bb0429b9d9c236b2fb15
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jun 20 21:45:39 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jun 20 21:45:39 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=62e31be6
dev-php/PEAR-Auth_SASL: Stabilize 1.2.0 ppc64, #934618
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-php/PEAR-Auth_SASL/PEAR-Auth_SASL-1.2.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-php/PEAR-Auth_SASL/PEAR-Auth_SASL-1.2.0.ebuild b/dev-php/PEAR-Auth_SASL/PEAR-Auth_SASL-1.2.0.ebuild
index d2745d3daeae..f420b47ac98d 100644
--- a/dev-php/PEAR-Auth_SASL/PEAR-Auth_SASL-1.2.0.ebuild
+++ b/dev-php/PEAR-Auth_SASL/PEAR-Auth_SASL-1.2.0.ebuild
@@ -9,5 +9,5 @@ DESCRIPTION="Abstraction of various SASL mechanism responses"
LICENSE="BSD"
SLOT="0"
-KEYWORDS="amd64 arm ~hppa ~ppc64 ~s390 sparc x86"
+KEYWORDS="amd64 arm ~hppa ppc64 ~s390 sparc x86"
RDEPEND="dev-php/PEAR-PEAR"
next reply other threads:[~2024-06-20 21:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 21:46 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-21 5:04 [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-Auth_SASL/ Arthur Zamarin
2024-06-20 20:33 Arthur Zamarin
2024-06-20 18:04 Arthur Zamarin
2024-06-20 17:53 Sam James
2024-06-20 17:43 Arthur Zamarin
2024-06-11 18:56 Michael Orlitzky
2023-12-15 3:26 Ionen Wolkens
2017-07-05 20:26 Brian Evans
2017-07-05 20:26 Brian Evans
2017-03-07 15:49 Brian Evans
2017-03-07 15:49 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=1718919939.62e31be6f1e400841384bb0429b9d9c236b2fb15.sam@gentoo \
--to=sam@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