public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libfido2/
Date: Thu,  2 Jun 2022 02:21:57 +0000 (UTC)	[thread overview]
Message-ID: <1654136468.26a9d5187be7cb5a531b0cfe182173935998798c.sam@gentoo> (raw)

commit:     26a9d5187be7cb5a531b0cfe182173935998798c
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jun  2 02:21:08 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jun  2 02:21:08 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=26a9d518

dev-libs/libfido2: Stabilize 1.11.0 ppc, #849128

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-libs/libfido2/libfido2-1.11.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-libs/libfido2/libfido2-1.11.0.ebuild b/dev-libs/libfido2/libfido2-1.11.0.ebuild
index f3f3238ed10e..97d6c74d3dd2 100644
--- a/dev-libs/libfido2/libfido2-1.11.0.ebuild
+++ b/dev-libs/libfido2/libfido2-1.11.0.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/Yubico/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
 
 LICENSE="BSD-2"
 SLOT="0/1"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc x86"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~mips ppc ~ppc64 ~riscv ~s390 ~sparc x86"
 IUSE="nfc static-libs"
 
 DEPEND="dev-libs/libcbor:=


             reply	other threads:[~2022-06-02  2:22 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  2:21 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-08 19:30 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libfido2/ Andreas Sturmlechner
2023-08-02 15:11 Sam James
2023-07-26  4:08 Sam James
2023-07-26  3:35 Sam James
2023-07-26  3:35 Sam James
2023-07-26  3:35 Sam James
2023-07-26  0:55 Sam James
2023-05-14 19:47 David Seifert
2023-03-04  9:05 Arthur Zamarin
2023-03-04  8:44 Arthur Zamarin
2023-03-04  7:12 Arthur Zamarin
2023-03-04  7:04 Arthur Zamarin
2023-03-04  6:17 Arthur Zamarin
2023-03-04  6:07 Arthur Zamarin
2022-06-02  4:08 Jakov Smolić
2022-06-02  4:08 Jakov Smolić
2022-06-02  3:05 Sam James
2022-06-02  2:21 Sam James
2022-06-02  2:03 Sam James
2022-06-02  2:03 Sam James
2022-06-02  1:46 Matt Turner
2022-05-22  3:13 Sam James
2022-05-05 23:48 WANG Xuerui
2022-04-03  3:41 Sam James
2022-01-17  7:26 Joshua Kinard
2021-11-03 16:08 Lars Wendler
2021-10-03 11:28 David Seifert
2021-10-02 15:43 Sam James
2021-10-02  9:08 James Le Cuirot
2021-09-21 16:35 Sam James
2021-09-20  0:27 Sam James
2021-09-19  6:39 Agostino Sarubbo
2021-09-18 19:51 Sam James
2021-09-18 19:51 Sam James
2021-09-18 17:18 Sam James
2021-09-10 15:16 Mike Gilbert
2021-09-10 14:47 Mike Gilbert
2021-09-09 19:09 Mike Gilbert
2021-08-02 16:42 Marek Szuba
2021-07-23 14:28 Lars Wendler
2021-05-09 21:44 Sam James
2021-05-09 21:42 Sam James
2021-05-09 10:57 Sam James
2021-05-09 10:57 Sam James
2021-05-09 10:57 Sam James
2021-05-09 10:57 Sam James
2021-05-01  7:29 Mikle Kolyada
2021-02-06 13:27 Sam James
2021-01-14 20:09 Sergei Trofimovich
2020-12-27 12:51 Sergei Trofimovich
2020-12-24 22:06 Sergei Trofimovich
2020-12-24 10:03 Agostino Sarubbo
2020-12-23  4:59 Lars Wendler
2020-12-22 21:04 Sam James
2020-12-22 21:03 Sam James
2020-12-21 23:55 Sam James
2020-12-21 17:48 Thomas Deutschmann
2020-10-19  3:30 Georgy Yakovlev
2020-09-29 21:25 Sergei Trofimovich
2020-07-12  1:51 Sam James
2020-06-01  4:16 Matt Turner
2020-05-31 15:17 Sergei Trofimovich
2020-05-28 18:20 Sergei Trofimovich
2020-05-02 13:30 Mart Raudsepp
2020-04-17 22:18 Patrick McLean
2020-04-04 10:52 Sergei Trofimovich
2020-03-15 12:17 Mikle Kolyada
2020-02-21 16:24 Lars Wendler
2020-02-18 23:10 Patrick McLean
2020-02-18 22:25 Patrick McLean
2020-02-16  7:13 Georgy Yakovlev

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=1654136468.26a9d5187be7cb5a531b0cfe182173935998798c.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