public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: kde-frameworks/kquickcharts/
Date: Tue, 25 Jul 2023 11:40:07 +0000 (UTC)	[thread overview]
Message-ID: <1690284701.8ea9937dee92731fb26b877b4e040f7fba5ad326.asturm@gentoo> (raw)

commit:     8ea9937dee92731fb26b877b4e040f7fba5ad326
Author:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 25 11:31:41 2023 +0000
Commit:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Tue Jul 25 11:31:41 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8ea9937d

kde-frameworks/kquickcharts: Add back VIRTUALX_REQUIRED, otherwise fails

with Failed to create OpenGL context for format QSurfaceFormat(version 2.0, ...)

Bug: https://bugs.gentoo.org/910062
Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>

 kde-frameworks/kquickcharts/kquickcharts-5.108.0.ebuild | 1 +
 1 file changed, 1 insertion(+)

diff --git a/kde-frameworks/kquickcharts/kquickcharts-5.108.0.ebuild b/kde-frameworks/kquickcharts/kquickcharts-5.108.0.ebuild
index e309ddc6983c..3bf3c015e625 100644
--- a/kde-frameworks/kquickcharts/kquickcharts-5.108.0.ebuild
+++ b/kde-frameworks/kquickcharts/kquickcharts-5.108.0.ebuild
@@ -8,6 +8,7 @@ ECM_QTHELP="false"
 ECM_TEST="true"
 PVCUT=$(ver_cut 1-2)
 QTMIN=5.15.9
+VIRTUALX_REQUIRED="test" # bug 910062 (tests fail)
 inherit ecm frameworks.kde.org
 
 DESCRIPTION="QtQuick plugin providing high-performance charts"


             reply	other threads:[~2023-07-25 11:40 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 11:40 Andreas Sturmlechner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-06  1:20 [gentoo-commits] repo/gentoo:master commit in: kde-frameworks/kquickcharts/ Andreas Sturmlechner
2024-10-15 20:13 Andreas Sturmlechner
2024-10-09  7:03 Arthur Zamarin
2024-10-04 20:27 Arthur Zamarin
2024-09-01 13:27 Andreas Sturmlechner
2024-09-01 13:27 Andreas Sturmlechner
2024-09-01 13:27 Andreas Sturmlechner
2024-09-01 10:28 Sam James
2024-03-01 16:24 Arthur Zamarin
2024-02-28 18:51 Arthur Zamarin
2024-01-14 22:28 Andreas Sturmlechner
2024-01-04 10:11 Sam James
2023-12-28 18:55 Arthur Zamarin
2023-08-26  4:50 Sam James
2023-07-25 18:14 Arthur Zamarin
2023-06-22 19:59 Arthur Zamarin
2023-05-27 13:44 Arthur Zamarin
2023-02-18 16:06 Arthur Zamarin
2023-02-18 13:27 Arthur Zamarin
2022-11-25  1:06 Jakov Smolić
2022-11-23 17:49 Jakov Smolić
2022-11-12 14:53 Arthur Zamarin
2022-08-06  4:08 Sam James
2022-04-29  3:30 Sam James
2022-04-22  1:59 Sam James
2022-04-22  1:57 Sam James
2022-02-10  0:40 Sam James
2022-02-08 14:46 Agostino Sarubbo
2022-02-08 11:02 Jakov Smolić
2021-12-10 18:37 Jakov Smolić
2021-12-10 11:15 Jakov Smolić
2021-09-14  5:19 Sam James
2021-09-13  8:18 Agostino Sarubbo
2021-09-12 23:34 Sam James
2021-04-11 12:25 Mikle Kolyada
2021-04-11 12:20 Mikle Kolyada
2021-04-10 23:41 Thomas Deutschmann
2020-03-01  7:28 Mikle Kolyada
2020-03-01  7:23 Mikle Kolyada
2020-03-01  7:18 Mikle Kolyada
2019-12-22 10:54 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=1690284701.8ea9937dee92731fb26b877b4e040f7fba5ad326.asturm@gentoo \
    --to=asturm@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