From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-admin/system-config-printer/
Date: Sat, 2 Mar 2024 20:41:26 +0000 (UTC) [thread overview]
Message-ID: <1709412052.f670aeafbfda5e9c8ad2da83a9f13cb4375ea7b8.sam@gentoo> (raw)
commit: f670aeafbfda5e9c8ad2da83a9f13cb4375ea7b8
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 2 20:40:52 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Mar 2 20:40:52 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f670aeaf
app-admin/system-config-printer: Stabilize 1.5.18-r2 ppc, #924716
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-admin/system-config-printer/system-config-printer-1.5.18-r2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-admin/system-config-printer/system-config-printer-1.5.18-r2.ebuild b/app-admin/system-config-printer/system-config-printer-1.5.18-r2.ebuild
index c7baacfcef66..96a93369f31b 100644
--- a/app-admin/system-config-printer/system-config-printer-1.5.18-r2.ebuild
+++ b/app-admin/system-config-printer/system-config-printer-1.5.18-r2.ebuild
@@ -18,7 +18,7 @@ SRC_URI="
LICENSE="GPL-2+"
SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~ia64 ~loong ~ppc ppc64 ~riscv ~sparc ~x86"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~ia64 ~loong ppc ppc64 ~riscv ~sparc ~x86"
IUSE="keyring policykit"
# Needs cups running, bug 284005
RESTRICT="test"
next reply other threads:[~2024-03-02 20:41 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 20:41 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-06 20:32 [gentoo-commits] repo/gentoo:master commit in: app-admin/system-config-printer/ Andreas Sturmlechner
2024-03-05 17:22 Arthur Zamarin
2024-02-23 4:46 Sam James
2024-01-10 19:02 Mike Gilbert
2024-01-07 17:06 Michał Górny
2022-11-01 6:19 WANG Xuerui
2022-10-29 22:33 Matt Turner
2022-10-25 18:36 Andreas Sturmlechner
2022-09-01 1:20 Matt Turner
2022-08-26 2:06 Matt Turner
2022-08-14 9:27 Pacho Ramos
2022-03-25 2:29 Sam James
2022-03-16 15:26 Andreas Sturmlechner
2022-03-16 15:15 Maciej Barć
2022-02-21 5:48 Matt Turner
2021-11-22 9:44 Sam James
2021-08-27 15:19 Yixun Lan
2021-02-01 8:40 Andreas Sturmlechner
2021-02-01 8:25 Sam James
2021-01-24 21:52 Sam James
2021-01-24 13:35 Sam James
2021-01-24 13:31 Sam James
2021-01-24 12:10 Agostino Sarubbo
2021-01-14 1:32 Andreas Sturmlechner
2021-01-14 1:32 Andreas Sturmlechner
2021-01-08 10:45 Andreas Sturmlechner
2020-11-26 23:04 Sergei Trofimovich
2020-11-26 14:36 Sam James
2020-11-25 16:37 Mikle Kolyada
2020-11-25 16:23 Mikle Kolyada
2020-11-25 16:19 Mikle Kolyada
2020-11-08 8:45 Andreas Sturmlechner
2020-04-17 18:55 Andreas Sturmlechner
2020-03-01 22:02 Andreas Sturmlechner
2019-12-28 12:53 Johannes Huber
2019-12-27 17:04 Aaron Bauman
2019-12-25 20:50 Sergei Trofimovich
2019-12-25 20:39 Sergei Trofimovich
2019-12-24 10:56 Agostino Sarubbo
2019-12-24 8:08 Agostino Sarubbo
2019-11-20 13:52 Andreas Sturmlechner
2019-11-20 13:52 Andreas Sturmlechner
2019-06-02 14:05 Alexey Shvetsov
2018-12-05 14:07 Mart Raudsepp
2018-12-05 7:34 Mikle Kolyada
2018-12-05 7:07 Mikle Kolyada
2018-11-02 13:25 Andreas Sturmlechner
2018-10-14 9:04 Andreas Sturmlechner
2017-07-25 12:27 Alexis Ballier
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=1709412052.f670aeafbfda5e9c8ad2da83a9f13cb4375ea7b8.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