From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-qt/qtwaylandscanner/
Date: Wed, 3 Apr 2024 18:48:40 +0000 (UTC) [thread overview]
Message-ID: <1712170036.2a88e128960a1afb0c985caf2c528a95252f0d43.arthurzam@gentoo> (raw)
commit: 2a88e128960a1afb0c985caf2c528a95252f0d43
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Wed Apr 3 18:47:16 2024 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Wed Apr 3 18:47:16 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2a88e128
dev-qt/qtwaylandscanner: Stabilize 5.15.13 arm, #927748
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
dev-qt/qtwaylandscanner/qtwaylandscanner-5.15.13.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-qt/qtwaylandscanner/qtwaylandscanner-5.15.13.ebuild b/dev-qt/qtwaylandscanner/qtwaylandscanner-5.15.13.ebuild
index a420cabf7111..70455ccd4802 100644
--- a/dev-qt/qtwaylandscanner/qtwaylandscanner-5.15.13.ebuild
+++ b/dev-qt/qtwaylandscanner/qtwaylandscanner-5.15.13.ebuild
@@ -9,7 +9,7 @@ inherit qt5-build
DESCRIPTION="Tool that generates certain boilerplate C++ code from Wayland protocol xml spec"
if [[ ${QT5_BUILD_TYPE} == release ]]; then
- KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~loong ~ppc ~ppc64 ~riscv ~sparc ~x86"
+ KEYWORDS="~amd64 arm ~arm64 ~hppa ~loong ~ppc ~ppc64 ~riscv ~sparc ~x86"
fi
DEPEND="=dev-qt/qtcore-${QT5_PV}*:5="
next reply other threads:[~2024-04-03 18:48 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 18:48 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-06 16:43 [gentoo-commits] repo/gentoo:master commit in: dev-qt/qtwaylandscanner/ Andreas Sturmlechner
2024-06-04 16:16 Arthur Zamarin
2024-06-01 15:59 Arthur Zamarin
2024-06-01 14:53 Arthur Zamarin
2024-06-01 10:25 Arthur Zamarin
2024-05-30 12:52 Andreas Sturmlechner
2024-04-05 15:01 Andreas Sturmlechner
2024-04-04 4:23 Arthur Zamarin
2024-04-03 20:45 Arthur Zamarin
2024-04-03 20:43 Arthur Zamarin
2024-04-03 19:06 Arthur Zamarin
2024-03-23 17:01 Andreas Sturmlechner
2024-02-01 23:06 Andreas Sturmlechner
2024-01-31 22:47 Ionen Wolkens
2024-01-31 7:18 Joonas Niilola
2024-01-30 4:05 Ionen Wolkens
2024-01-29 4:22 Ionen Wolkens
2024-01-01 21:14 Andreas Sturmlechner
2023-11-06 18:11 Andreas Sturmlechner
2023-11-06 8:15 Arthur Zamarin
2023-11-06 7:14 Arthur Zamarin
2023-10-08 15:58 Andreas Sturmlechner
2023-07-13 8:42 Andreas Sturmlechner
2023-07-12 23:39 Sam James
2023-07-12 1:13 Sam James
2023-07-09 17:00 Arthur Zamarin
2023-06-13 11:42 Andreas Sturmlechner
2023-05-01 12:54 Andreas Sturmlechner
2023-05-01 7:26 Arthur Zamarin
2023-04-25 9:42 Arthur Zamarin
2023-04-23 16:00 Arthur Zamarin
2023-04-13 21:45 Andreas Sturmlechner
2023-01-24 9:45 Andreas Sturmlechner
2023-01-21 19:37 Arthur Zamarin
2023-01-21 19:33 Arthur Zamarin
2023-01-21 19:30 Arthur Zamarin
2023-01-21 9:15 Arthur Zamarin
2023-01-17 20:56 Arthur Zamarin
2023-01-17 20:04 Sam James
2023-01-08 21:45 Andreas Sturmlechner
2022-12-06 17:07 Andreas Sturmlechner
2022-12-05 19:45 Arthur Zamarin
2022-12-04 19:30 Arthur Zamarin
2022-12-04 19:22 Arthur Zamarin
2022-12-03 20:37 Arthur Zamarin
2022-12-03 11:02 Sam James
2022-11-29 20:51 Andreas Sturmlechner
2022-07-06 10:27 Andreas Sturmlechner
2022-07-04 18:00 Arthur Zamarin
2022-07-02 18:26 Sam James
2022-07-02 12:54 Arthur Zamarin
2022-07-02 11:02 Arthur Zamarin
2022-06-30 22:19 Sam James
2022-06-19 12:26 Andreas Sturmlechner
2022-06-18 17:25 Andreas Sturmlechner
2022-06-18 15:39 Sam James
2022-06-14 13:27 Sam James
2022-06-14 7:21 Agostino Sarubbo
2022-06-13 21:18 Sam James
2022-06-10 3:16 Sam James
2022-05-20 19:43 Andreas Sturmlechner
2022-04-17 18:18 Sam James
2022-04-14 0:19 Sam James
2022-04-12 22:49 Sam James
2022-04-12 19:35 Arthur Zamarin
2022-04-12 18:45 Arthur Zamarin
2022-03-21 11:04 Andreas Sturmlechner
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=1712170036.2a88e128960a1afb0c985caf2c528a95252f0d43.arthurzam@gentoo \
--to=arthurzam@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