public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-misc/gsasl/
Date: Tue, 16 Aug 2022 07:45:07 +0000 (UTC)	[thread overview]
Message-ID: <1660635873.1fba2601f68df9d061239ca5db34a82e6a83ed41.ago@gentoo> (raw)

commit:     1fba2601f68df9d061239ca5db34a82e6a83ed41
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Tue Aug 16 07:44:33 2022 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Tue Aug 16 07:44:33 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1fba2601

net-misc/gsasl: arm64 stable wrt bug #853637

Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 net-misc/gsasl/gsasl-2.0.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-misc/gsasl/gsasl-2.0.1.ebuild b/net-misc/gsasl/gsasl-2.0.1.ebuild
index a77897523854..d8b4db232b4c 100644
--- a/net-misc/gsasl/gsasl-2.0.1.ebuild
+++ b/net-misc/gsasl/gsasl-2.0.1.ebuild
@@ -13,7 +13,7 @@ LICENSE="GPL-3"
 SLOT="0"
 # Before giving keywords (or ideally even bumping), please check https://www.gnu.org/software/gsasl/ to see
 # if it's a stable release or not!
-KEYWORDS="amd64 arm ~arm64 ~hppa ~ia64 ~loong ppc ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux ~ppc-macos"
+KEYWORDS="amd64 arm arm64 ~hppa ~ia64 ~loong ppc ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux ~ppc-macos"
 IUSE="+client gcrypt gnutls idn kerberos nls ntlm +server static-libs"
 REQUIRED_USE="|| ( client server )"
 


             reply	other threads:[~2022-08-16  7:45 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16  7:45 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-25 20:42 [gentoo-commits] repo/gentoo:master commit in: net-misc/gsasl/ Sam James
2024-11-23 18:27 Michał Górny
2024-11-23 18:02 Arthur Zamarin
2024-09-12 16:16 Jakov Smolić
2024-03-16 10:23 Arthur Zamarin
2024-03-15 20:22 Sam James
2024-03-15 20:11 Arthur Zamarin
2024-03-15 20:07 Arthur Zamarin
2024-03-15 20:04 Arthur Zamarin
2024-01-03  9:27 Sam James
2023-04-07  1:49 Sam James
2023-04-06  4:42 Sam James
2022-09-19  6:42 Michał Górny
2022-09-03 16:28 Sam James
2022-08-16  7:44 Agostino Sarubbo
2022-07-19  8:59 Agostino Sarubbo
2022-07-19  8:58 Agostino Sarubbo
2022-07-19  8:58 Agostino Sarubbo
2022-07-19  5:53 Joonas Niilola
2022-07-19  5:53 Joonas Niilola
2022-07-18 18:52 Sam James
2022-07-18 18:52 Sam James
2022-07-18 18:45 Sam James
2022-07-18 18:39 Sam James
2022-07-16 14:33 Sam James
2022-06-30 18:16 Arthur Zamarin
2022-06-28 15:44 Arthur Zamarin
2022-06-27 11:17 WANG Xuerui
2022-06-22 16:15 Arthur Zamarin
2022-06-22 12:34 Jakov Smolić
2022-06-22 12:02 Jakov Smolić
2022-06-22 11:45 Jakov Smolić
2022-06-22 11:40 Jakov Smolić
2022-06-22  4:39 Sam James
2022-06-21 22:01 Sam James
2022-06-21 22:01 Sam James
2021-10-28  8:16 Sam James
2021-07-13 11:21 Marek Szuba
2021-02-05 12:29 Sam James
2021-02-03  3:11 Sam James
2021-02-01 13:33 Sam James
2021-02-01  5:49 Sam James
2021-01-01 22:53 Sam James
2020-12-20 16:40 Thomas Deutschmann
2020-12-17 16:41 Agostino Sarubbo
2020-12-17  8:58 Sam James
2016-08-06 16:51 Michał Górny

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=1660635873.1fba2601f68df9d061239ca5db34a82e6a83ed41.ago@gentoo \
    --to=ago@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