From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: kde-frameworks/solid/
Date: Tue, 28 May 2024 02:10:28 +0000 (UTC) [thread overview]
Message-ID: <1716862050.d630b36a64b08ffe7e639be668a4a1d867999972.sam@gentoo> (raw)
commit: d630b36a64b08ffe7e639be668a4a1d867999972
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue May 28 02:07:30 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue May 28 02:07:30 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d630b36a
kde-frameworks/solid: Stabilize 5.116.0 arm64, #932369
Signed-off-by: Sam James <sam <AT> gentoo.org>
kde-frameworks/solid/solid-5.116.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kde-frameworks/solid/solid-5.116.0.ebuild b/kde-frameworks/solid/solid-5.116.0.ebuild
index 78a6e2eba194..f3d77112cc05 100644
--- a/kde-frameworks/solid/solid-5.116.0.ebuild
+++ b/kde-frameworks/solid/solid-5.116.0.ebuild
@@ -9,7 +9,7 @@ inherit ecm frameworks.kde.org optfeature
DESCRIPTION="Provider for platform independent hardware discovery, abstraction and management"
LICENSE="LGPL-2.1+"
-KEYWORDS="amd64 ~arm ~arm64 ~loong ppc64 ~riscv x86"
+KEYWORDS="amd64 ~arm arm64 ~loong ppc64 ~riscv x86"
IUSE="ios"
RDEPEND="
next reply other threads:[~2024-05-28 2:10 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 2:10 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-20 19:25 [gentoo-commits] repo/gentoo:master commit in: kde-frameworks/solid/ Arthur Zamarin
2024-11-20 19:25 Arthur Zamarin
2024-11-20 19:25 Arthur Zamarin
2024-11-20 3:51 Sam James
2024-11-05 22:50 Andreas Sturmlechner
2024-10-04 16:37 Arthur Zamarin
2024-09-12 17:21 Arthur Zamarin
2024-05-27 23:47 Sam James
2024-05-27 18:13 Arthur Zamarin
2024-05-13 20:26 Andreas Sturmlechner
2024-03-01 14:00 Arthur Zamarin
2024-02-19 16:28 Sam James
2024-02-02 12:44 Arthur Zamarin
2023-08-02 17:48 Sam James
2023-06-22 19:59 Arthur Zamarin
2022-11-16 21:33 Andreas Sturmlechner
2022-02-08 14:46 Agostino Sarubbo
2022-01-20 13:26 Andreas Sturmlechner
2021-12-08 15:08 Andreas Sturmlechner
2021-09-13 8:18 Agostino Sarubbo
2021-08-01 19:32 Andreas Sturmlechner
2021-04-11 12:25 Mikle Kolyada
2021-04-11 12:20 Mikle Kolyada
2021-04-10 23:41 Thomas Deutschmann
2020-07-11 15:37 Andreas Sturmlechner
2020-06-28 17:56 Andreas Sturmlechner
2020-05-31 15:54 Mikle Kolyada
2020-05-30 13:38 Mikle Kolyada
2020-05-30 13:33 Mikle Kolyada
2020-03-01 7:28 Mikle Kolyada
2020-03-01 7:23 Mikle Kolyada
2020-03-01 7:18 Mikle Kolyada
2019-12-02 15:51 Andreas Sturmlechner
2019-09-08 16:18 Andreas Sturmlechner
2019-07-28 19:16 Aaron Bauman
2019-07-28 0:36 Mikle Kolyada
2019-07-28 0:15 Mikle Kolyada
2019-06-10 10:37 Michael Palimaka
2019-05-27 21:04 Aaron Bauman
2019-05-16 12:28 Mikle Kolyada
2019-05-16 12:23 Mikle Kolyada
2019-04-21 19:06 Andreas Sturmlechner
2019-04-21 19:06 Andreas Sturmlechner
2019-02-06 11:37 Mikle Kolyada
2019-02-06 10:59 Mikle Kolyada
2018-10-10 11:48 Mikle Kolyada
2018-10-10 3:01 Thomas Deutschmann
2018-05-22 4:44 Andreas Sturmlechner
2017-07-13 18:32 Alexis Ballier
2017-06-09 10:19 Agostino Sarubbo
2017-06-04 16:00 Agostino Sarubbo
2017-01-20 9:47 Agostino Sarubbo
2017-01-17 19:54 Aaron Bauman
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=1716862050.d630b36a64b08ffe7e639be668a4a1d867999972.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