public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-qt/qthelp/
Date: Tue, 25 Apr 2023 09:42:53 +0000 (UTC)	[thread overview]
Message-ID: <1682415706.c2ef03cb184c970fa24f4f4842f502dc0f102a74.arthurzam@gentoo> (raw)

commit:     c2ef03cb184c970fa24f4f4842f502dc0f102a74
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Tue Apr 25 09:41:00 2023 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Tue Apr 25 09:41:46 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c2ef03cb

dev-qt/qthelp: Stabilize 5.15.9 arm, #904373

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 dev-qt/qthelp/qthelp-5.15.9.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-qt/qthelp/qthelp-5.15.9.ebuild b/dev-qt/qthelp/qthelp-5.15.9.ebuild
index b5c6c1fc0ac1..bdea155f72da 100644
--- a/dev-qt/qthelp/qthelp-5.15.9.ebuild
+++ b/dev-qt/qthelp/qthelp-5.15.9.ebuild
@@ -5,7 +5,7 @@ EAPI=8
 
 if [[ ${PV} != *9999* ]]; then
 	QT5_KDEPATCHSET_REV=1
-	KEYWORDS="amd64 ~arm arm64 ~hppa ~loong ~ppc ~ppc64 ~riscv ~sparc x86"
+	KEYWORDS="amd64 arm arm64 ~hppa ~loong ~ppc ~ppc64 ~riscv ~sparc x86"
 fi
 
 QT5_MODULE="qttools"


             reply	other threads:[~2023-04-25  9:42 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25  9:42 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-01 14:53 [gentoo-commits] repo/gentoo:master commit in: dev-qt/qthelp/ Arthur Zamarin
2024-04-03 19:06 Arthur Zamarin
2024-04-03 18:48 Arthur Zamarin
2024-01-31 22:47 Ionen Wolkens
2024-01-30  4:05 Ionen Wolkens
2023-11-06  7:14 Arthur Zamarin
2023-07-12 23:39 Sam James
2023-07-12  1:13 Sam James
2023-01-21 19:37 Arthur Zamarin
2023-01-21 19:33 Arthur Zamarin
2022-12-05 19:45 Arthur Zamarin
2022-12-02 10:20 WANG Xuerui
2022-07-04 17:58 Arthur Zamarin
2022-07-02 12:54 Arthur Zamarin
2022-06-13 21:18 Sam James
2022-04-17 19:32 Sam James
2022-04-12 18:45 Arthur Zamarin
2021-10-17  0:29 Sam James
2021-10-17  0:27 Sam James
2021-09-30 18:21 Sam James
2021-09-30 18:15 Sam James
2021-09-08 16:55 Andreas Sturmlechner
2021-01-09 21:18 Sam James
2021-01-09 21:17 Sam James
2021-01-09 13:42 Sam James
2020-10-13  9:58 Agostino Sarubbo
2020-10-13  9:51 Agostino Sarubbo
2020-10-12 11:55 Sam James
2020-05-30 19:33 Sergei Trofimovich
2020-05-09  7:46 Agostino Sarubbo
2020-05-09  7:43 Agostino Sarubbo
2020-03-19 10:14 Agostino Sarubbo
2020-03-19 10:12 Agostino Sarubbo
2020-01-27 10:48 Mikle Kolyada
2020-01-13 19:50 Sergei Trofimovich
2019-12-21 10:54 Mikle Kolyada
2019-10-20 16:15 Mikle Kolyada
2019-05-23 13:20 Mikle Kolyada
2019-05-23 12:26 Mikle Kolyada
2019-04-26 17:51 Anthony G. Basile
2019-02-11 23:36 Sergei Trofimovich
2019-01-09 13:30 Mikle Kolyada
2018-11-24 13:32 Sergei Trofimovich
2018-09-07 23:46 Sergei Trofimovich
2018-08-19 10:46 Sergei Trofimovich
2018-08-17 21:12 Sergei Trofimovich
2018-03-26  7:04 Sergei Trofimovich
2018-03-21  7:25 Sergei Trofimovich
2018-03-14 17:27 Michał Górny
2018-01-28 18:05 Sergei Trofimovich
2017-11-11 23:34 Sergei Trofimovich
2017-11-11 19:37 Sergei Trofimovich
2017-07-15  5:16 Markus Meier
2017-06-26  7:54 Alexis Ballier
2017-06-23  5:20 Alexis Ballier
2017-06-06 16:12 Markus Meier
2017-06-03 20:09 Sergei Trofimovich
2017-05-22 11:40 Agostino Sarubbo
2017-05-21 16:41 Michael Weber
2017-05-20 10:37 Michael Weber
2017-05-18 12:39 Agostino Sarubbo
2017-01-02 18:48 Markus Meier
2016-08-23 19:20 Markus Meier
2016-06-04 11:40 Davide Pesavento
2016-03-24  5:53 Markus Meier
2016-03-09  4:12 Jeroen Roovers
2016-03-05 22:20 Mikle Kolyada
2016-01-15  6:47 Michael Palimaka
2016-01-14 18:10 Michael Palimaka
2015-10-18  9:40 Mikle Kolyada
2015-09-21  4:58 Jeroen Roovers
2015-08-26 14:56 Mikle Kolyada

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=1682415706.c2ef03cb184c970fa24f4f4842f502dc0f102a74.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