public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/python-ldap/
Date: Thu, 30 Nov 2023 15:40:25 +0000 (UTC)	[thread overview]
Message-ID: <1701358822.f464f2d7da79eaf7e2e17879203f1aed51e3f10f.mgorny@gentoo> (raw)

commit:     f464f2d7da79eaf7e2e17879203f1aed51e3f10f
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Thu Nov 30 15:40:12 2023 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Thu Nov 30 15:40:22 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f464f2d7

dev-python/python-ldap: Stabilize 3.4.3 arm64, #918904

Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>

 dev-python/python-ldap/python-ldap-3.4.3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/python-ldap/python-ldap-3.4.3.ebuild b/dev-python/python-ldap/python-ldap-3.4.3.ebuild
index dca4223250f3..ff3693c2dce0 100644
--- a/dev-python/python-ldap/python-ldap-3.4.3.ebuild
+++ b/dev-python/python-ldap/python-ldap-3.4.3.ebuild
@@ -23,7 +23,7 @@ S=${WORKDIR}/${PN}-${P}
 
 LICENSE="MIT PSF-2"
 SLOT="0"
-KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~ppc ppc64 ~riscv sparc x86"
+KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~ppc ppc64 ~riscv sparc x86"
 IUSE="examples sasl ssl"
 
 RDEPEND="


             reply	other threads:[~2023-11-30 15:40 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 15:40 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-09 15:47 [gentoo-commits] repo/gentoo:master commit in: dev-python/python-ldap/ Michał Górny
2023-12-09 15:30 Michał Górny
2023-12-09 14:30 Michał Górny
2023-12-09 14:04 Michał Górny
2023-12-09 13:56 Michał Górny
2023-12-09 13:56 Michał Górny
2023-12-09 13:52 Michał Górny
2023-11-30  2:08 Sam James
2023-11-18 15:47 Michał Górny
2023-11-05 17:15 Michał Górny
2023-05-20  8:28 Michał Górny
2023-05-04 16:30 Michał Górny
2022-10-25 14:06 Michał Górny
2022-10-25 12:50 Sam James
2022-10-25  9:49 Sam James
2022-10-23  7:53 Agostino Sarubbo
2022-10-22 16:27 Arthur Zamarin
2022-09-22 12:15 Michał Górny
2022-08-12 14:09 Michał Górny
2022-08-12 10:49 Agostino Sarubbo
2022-08-10  8:04 Arthur Zamarin
2022-08-09  7:43 Agostino Sarubbo
2022-08-09  4:00 Arthur Zamarin
2022-07-07  8:26 Michał Górny
2022-06-17  6:58 Agostino Sarubbo
2022-06-16 15:46 Sam James
2022-06-16  9:41 Jakov Smolić
2022-06-16  9:37 Jakov Smolić
2022-05-14  2:52 Sam James
2022-03-26 21:47 Marek Szuba
2022-03-22 23:32 Sam James
2021-11-29 14:45 Michał Górny
2021-11-29  8:49 Agostino Sarubbo
2021-11-29  7:36 Arthur Zamarin
2021-11-29  7:36 Arthur Zamarin
2021-11-29  7:36 Arthur Zamarin
2021-11-28 23:36 Jakov Smolić
2021-11-26 21:56 Michał Górny
2021-08-08 22:20 Louis Sautier
2021-08-08 22:20 Louis Sautier
2020-11-18  9:12 Michał Górny
2020-11-17 19:17 Agostino Sarubbo
2020-11-17 19:10 Agostino Sarubbo
2020-11-17 18:55 Agostino Sarubbo
2020-11-17 18:49 Agostino Sarubbo
2020-11-16  1:15 Sam James
2020-10-31  1:36 Patrick McLean
2020-10-09 23:08 Patrick McLean
2020-08-02  9:15 Michał Górny
2020-03-28 21:11 Michał Górny
2020-03-25 15:27 Agostino Sarubbo
2020-03-25 12:36 Agostino Sarubbo
2020-03-19 22:12 David Seifert
2020-02-10 18:52 Patrick McLean
2020-02-10 18:52 Patrick McLean
2020-02-10 18:48 Patrick McLean
2019-04-13 22:41 Matthew Thode
2019-03-13 17:29 Matthew Thode
2018-11-18  9:38 Mikle Kolyada
2018-06-20 21:45 Louis Sautier
2018-06-20 21:45 Louis Sautier
2018-06-20 21:45 Louis Sautier
2018-04-29 10:30 Michał Górny
2018-03-20 21:11 Michał Górny
2017-05-10 20:47 Manuel Rüger
2017-04-07  1:02 Manuel Rüger
2015-10-10 15:40 Justin Lecher
2015-10-09 10:04 Mike Gilbert
2015-09-28 12:12 Justin Lecher
2015-09-21 12:10 Justin Lecher
2015-08-25  4:35 Jeroen Roovers
2015-08-25  4:35 Jeroen Roovers

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=1701358822.f464f2d7da79eaf7e2e17879203f1aed51e3f10f.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