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/qtquick3d/
Date: Mon,  1 Apr 2024 18:29:24 +0000 (UTC)	[thread overview]
Message-ID: <1711996081.6ee015843f26ee5613b787f19b44e41d3f57120d.arthurzam@gentoo> (raw)

commit:     6ee015843f26ee5613b787f19b44e41d3f57120d
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Mon Apr  1 18:28:01 2024 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Mon Apr  1 18:28:01 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6ee01584

dev-qt/qtquick3d: Stabilize 6.6.3 amd64, #928382

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

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

diff --git a/dev-qt/qtquick3d/qtquick3d-6.6.3.ebuild b/dev-qt/qtquick3d/qtquick3d-6.6.3.ebuild
index 3ce3b4f8b69d..cb98cbb2bda2 100644
--- a/dev-qt/qtquick3d/qtquick3d-6.6.3.ebuild
+++ b/dev-qt/qtquick3d/qtquick3d-6.6.3.ebuild
@@ -8,7 +8,7 @@ inherit qt6-build
 DESCRIPTION="Qt module and API for defining 3D content in Qt QuickTools"
 
 if [[ ${QT6_BUILD_TYPE} == release ]]; then
-	KEYWORDS="~amd64 ~arm ~arm64 ~loong ~ppc ~ppc64 ~riscv ~x86"
+	KEYWORDS="amd64 ~arm ~arm64 ~loong ~ppc ~ppc64 ~riscv ~x86"
 elif [[ ${QT6_BUILD_TYPE} == live ]]; then
 	EGIT_SUBMODULES=() # skip qtquick3d-assimp
 fi


             reply	other threads:[~2024-04-01 18:29 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 18:29 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-13 10:04 [gentoo-commits] repo/gentoo:master commit in: dev-qt/qtquick3d/ Ionen Wolkens
2024-11-02 14:10 Arthur Zamarin
2024-11-01  6:35 Arthur Zamarin
2024-10-09  6:22 Ionen Wolkens
2024-10-08  5:03 Ionen Wolkens
2024-09-27  7:26 Ionen Wolkens
2024-09-24  9:57 Ionen Wolkens
2024-07-24  2:20 Ionen Wolkens
2024-07-16  1:29 Ionen Wolkens
2024-07-08 11:16 Arthur Zamarin
2024-07-08 10:09 Sam James
2024-07-02  2:37 Ionen Wolkens
2024-06-18 18:14 Ionen Wolkens
2024-06-08 13:41 Ionen Wolkens
2024-06-08  5:27 Arthur Zamarin
2024-06-04 19:36 Ionen Wolkens
2024-06-02  4:04 Sam James
2024-05-28 18:56 Arthur Zamarin
2024-05-20  8:48 Ionen Wolkens
2024-04-19  7:55 Ionen Wolkens
2024-04-13 17:50 Arthur Zamarin
2024-04-02 13:06 Ionen Wolkens
2024-04-02  6:09 Arthur Zamarin
2024-03-30  0:29 Ionen Wolkens
2024-03-26  7:10 Ionen Wolkens
2024-03-24 18:39 Ionen Wolkens
2024-03-22 10:29 Ionen Wolkens
2024-03-22  6:16 Arthur Zamarin
2024-03-21 14:41 Ionen Wolkens
2024-03-12 12:01 Ionen Wolkens
2024-02-20 14:30 Arthur Zamarin
2024-02-14 12:24 Ionen Wolkens
2024-01-02 16:26 WANG Xuerui
2023-12-19 20:33 Ionen Wolkens
2023-12-17 18:29 Arthur Zamarin
2023-12-12 21:25 Ionen Wolkens
2023-12-05  7:25 Joonas Niilola
2023-12-03 20:48 Jakov Smolić
2023-12-02 10:57 Arthur Zamarin
2023-12-02 10:57 Arthur Zamarin
2023-12-01 10:58 Arthur Zamarin
2023-12-01 10:58 Arthur Zamarin
2023-11-27  8:47 Ionen Wolkens
2023-11-20  2:07 Ionen Wolkens
2023-11-20  2:07 Ionen Wolkens
2023-11-15 19:28 Ionen Wolkens
2023-11-15 17:20 Arthur Zamarin
2023-10-10 14:51 Ionen Wolkens
2023-09-28 13:07 Ionen Wolkens
2023-09-26 19:48 Ionen Wolkens
2023-09-15  4:49 Sam James
2023-09-09 16:22 Ionen Wolkens
2023-09-05 13:05 Ionen Wolkens
2023-07-26 13:31 Jimi Huotari
2023-07-20 19:41 Jimi Huotari
2023-06-10 13:33 Jimi Huotari
2023-05-06 11:26 Jimi Huotari
2023-04-15 18:39 Jimi Huotari
2023-03-26 16:59 Jimi Huotari
2023-03-19 13:09 Jimi Huotari
2023-02-09 10:02 Andreas Sturmlechner
2023-01-05 22:39 Jimi Huotari
2022-12-01 19:19 Andreas Sturmlechner
2022-09-24 14:32 Andreas Sturmlechner
2022-09-24 14:32 Andreas Sturmlechner
2022-08-02 22:00 Sam James
2022-08-02 21:51 Sam James

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=1711996081.6ee015843f26ee5613b787f19b44e41d3f57120d.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