From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-auth/nss-pam-ldapd/
Date: Sat, 12 Oct 2024 07:52:20 +0000 (UTC) [thread overview]
Message-ID: <1728719531.5692b552961736acfb827b804a88751c63fed03c.mgorny@gentoo> (raw)
commit: 5692b552961736acfb827b804a88751c63fed03c
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 12 07:52:11 2024 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sat Oct 12 07:52:11 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5692b552
sys-auth/nss-pam-ldapd: Stabilize 0.9.12-r4 arm, #941363
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
sys-auth/nss-pam-ldapd/nss-pam-ldapd-0.9.12-r4.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-auth/nss-pam-ldapd/nss-pam-ldapd-0.9.12-r4.ebuild b/sys-auth/nss-pam-ldapd/nss-pam-ldapd-0.9.12-r4.ebuild
index 56f00ec57d0c..815a5f464dc9 100644
--- a/sys-auth/nss-pam-ldapd/nss-pam-ldapd-0.9.12-r4.ebuild
+++ b/sys-auth/nss-pam-ldapd/nss-pam-ldapd-0.9.12-r4.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://arthurdejong.org/${PN}/${P}.tar.gz"
LICENSE="LGPL-2.1"
SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~hppa ~mips ~ppc ~ppc64 ~sparc ~x86"
+KEYWORDS="~alpha ~amd64 arm ~hppa ~mips ~ppc ~ppc64 ~sparc ~x86"
IUSE="debug kerberos +pam pynslcd sasl selinux test +utils"
REQUIRED_USE="
${PYTHON_REQUIRED_USE}
next reply other threads:[~2024-10-12 7:52 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 7:52 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-12 10:08 [gentoo-commits] repo/gentoo:master commit in: sys-auth/nss-pam-ldapd/ Michał Górny
2024-10-12 9:44 Michał Górny
2024-10-12 9:44 Michał Górny
2024-07-04 0:00 Matthew Thode
2024-04-13 15:38 Matthew Thode
2024-01-19 23:08 Ionen Wolkens
2024-01-14 4:19 Sam James
2024-01-14 4:18 Sam James
2024-01-14 4:14 Sam James
2023-12-23 19:59 Arthur Zamarin
2023-12-19 5:19 Sam James
2023-12-16 7:09 Arthur Zamarin
2023-11-30 2:08 Sam James
2023-11-28 5:27 Arthur Zamarin
2023-11-28 5:27 Arthur Zamarin
2023-06-28 7:50 Sam James
2023-03-03 6:28 Viorel Munteanu
2023-02-28 1:30 Sam James
2023-02-26 18:22 Arthur Zamarin
2023-02-26 18:16 Arthur Zamarin
2023-01-13 12:39 Arthur Zamarin
2023-01-13 12:39 Arthur Zamarin
2023-01-01 18:24 David Seifert
2022-03-23 0:14 Sam James
2022-01-22 3:13 Matthew Thode
2022-01-05 10:01 David Seifert
2021-12-21 18:52 Matthew Thode
2021-11-21 23:05 Matthew Thode
2021-11-06 19:59 Arthur Zamarin
2021-07-30 23:31 Sam James
2021-03-07 11:58 David Seifert
2020-12-02 17:04 Mikle Kolyada
2020-05-26 16:16 Matthew Thode
2020-03-17 9:56 Michał Górny
2020-03-16 17:58 Matthew Thode
2019-12-18 21:06 Matthew Thode
2019-11-06 19:49 Matthew Thode
2019-10-12 19:36 Mikle Kolyada
2019-10-07 15:35 Matthew Thode
2018-09-28 20:35 Matt Thode
2018-09-01 17:46 Matt Thode
2018-04-12 4:25 Matt Thode
2018-03-18 19:15 Matt Thode
2018-02-18 23:36 Matt Thode
2017-08-01 17:44 Patrick McLean
2017-07-23 2:33 Matt Thode
2017-06-26 15:19 Matt Thode
2016-12-29 10:45 Agostino Sarubbo
2016-12-17 1:10 Aaron Bauman
2016-10-17 1:19 Matt Thode
2016-09-14 13:25 Matt Thode
2016-09-14 13:25 Matt Thode
2016-08-15 14:40 Matt Thode
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=1728719531.5692b552961736acfb827b804a88751c63fed03c.mgorny@gentoo \
--to=mgorny@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