From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-auth/fprintd/
Date: Mon, 14 Apr 2025 07:14:14 +0000 (UTC) [thread overview]
Message-ID: <1744614851.937a5e90ffca6f5ce7750a309d7d5f684eadb1d0.juippis@gentoo> (raw)
commit: 937a5e90ffca6f5ce7750a309d7d5f684eadb1d0
Author: Joonas Niilola <juippis <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 14 07:12:11 2025 +0000
Commit: Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Mon Apr 14 07:14:11 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=937a5e90
sys-auth/fprintd: Stabilize 1.94.3 amd64, #951057
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>
sys-auth/fprintd/fprintd-1.94.3.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sys-auth/fprintd/fprintd-1.94.3.ebuild b/sys-auth/fprintd/fprintd-1.94.3.ebuild
index dbdb4718095b..05018c43c467 100644
--- a/sys-auth/fprintd/fprintd-1.94.3.ebuild
+++ b/sys-auth/fprintd/fprintd-1.94.3.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2024 Gentoo Authors
+# Copyright 1999-2025 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
@@ -16,7 +16,7 @@ S="${WORKDIR}/${MY_P}"
LICENSE="GPL-2+"
SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~loong ~ppc ~ppc64 ~riscv ~sparc ~x86"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~loong ~ppc ~ppc64 ~riscv ~sparc ~x86"
IUSE="doc pam selinux systemd test"
RESTRICT="!test? ( test )"
next reply other threads:[~2025-04-14 7:14 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 7:14 Joonas Niilola [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-14 7:14 [gentoo-commits] repo/gentoo:master commit in: sys-auth/fprintd/ Joonas Niilola
2024-06-03 5:53 Sam James
2023-07-27 5:11 WANG Xuerui
2023-06-28 7:37 Sam James
2023-02-24 16:29 Arthur Zamarin
2023-02-24 16:29 Arthur Zamarin
2023-02-24 16:29 Arthur Zamarin
2023-02-24 16:29 Arthur Zamarin
2023-02-24 16:29 Arthur Zamarin
2023-02-24 16:29 Arthur Zamarin
2023-02-24 16:29 Arthur Zamarin
2022-12-28 0:56 Sam James
2022-12-27 23:37 Sam James
2022-12-27 23:37 Sam James
2022-11-18 19:42 Arthur Zamarin
2022-11-18 19:24 Arthur Zamarin
2022-09-22 7:46 Michał Górny
2022-07-30 19:57 Arthur Zamarin
2022-04-29 10:21 Sam James
2022-04-17 19:17 Sam James
2022-04-17 18:36 Arthur Zamarin
2022-04-17 18:36 Arthur Zamarin
2022-04-17 18:36 Arthur Zamarin
2022-04-11 21:05 Jakov Smolić
2022-04-06 6:32 Agostino Sarubbo
2022-04-06 6:32 Agostino Sarubbo
2022-01-04 15:33 Marek Szuba
2021-12-10 1:24 Sam James
2021-12-02 8:29 Agostino Sarubbo
2021-12-02 8:24 Agostino Sarubbo
2021-11-19 20:01 Arthur Zamarin
2021-11-04 17:07 Sam James
2021-10-20 9:46 Sam James
2021-10-20 9:46 Sam James
2021-10-20 3:26 Sam James
2021-08-27 15:19 Yixun Lan
2021-07-25 1:10 Sam James
2021-07-24 15:22 Sam James
2021-04-02 9:23 Sergei Trofimovich
2021-03-26 7:45 Agostino Sarubbo
2021-03-25 18:12 Agostino Sarubbo
2021-03-25 13:02 Joonas Niilola
2021-03-25 13:02 Joonas Niilola
2021-03-25 13:02 Joonas Niilola
2021-03-15 18:06 Sergei Trofimovich
2021-03-15 6:32 Sam James
2021-03-14 22:11 Sam James
2021-03-14 22:11 Sam James
2021-03-13 11:37 Sam James
2021-03-13 11:35 Sam James
2021-03-04 0:23 Sam James
2021-02-11 7:36 Sergei Trofimovich
2021-01-05 22:00 Matt Turner
2019-08-04 19:36 Maxim Koltsov
2019-08-04 19:36 Maxim Koltsov
2019-08-03 11:19 Aaron Bauman
2019-07-29 14:53 Mikle Kolyada
2019-07-29 14:53 Mikle Kolyada
2019-06-20 9:23 Mikle Kolyada
2019-06-09 19:25 Sergei Trofimovich
2019-06-06 21:31 Sergei Trofimovich
2019-06-06 21:24 Sergei Trofimovich
2019-06-05 18:14 Sergei Trofimovich
2019-01-18 18:01 Mikle Kolyada
2019-01-08 14:07 Maxim Koltsov
2018-05-21 16:25 Mikle Kolyada
2015-08-09 22:33 Michael Weber
2015-08-09 22:16 Michael Weber
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=1744614851.937a5e90ffca6f5ce7750a309d7d5f684eadb1d0.juippis@gentoo \
--to=juippis@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