public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "orbea" <orbea@riseup.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/libressl:master commit in: dev-qt/qtbase/
Date: Fri,  5 Jul 2024 02:04:23 +0000 (UTC)	[thread overview]
Message-ID: <1720144963.cfe00b762e6787556e2bcee942e65b15d8041025.orbea@gentoo> (raw)

commit:     cfe00b762e6787556e2bcee942e65b15d8041025
Author:     orbea <orbea <AT> riseup <DOT> net>
AuthorDate: Fri Jul  5 02:02:43 2024 +0000
Commit:     orbea <orbea <AT> riseup <DOT> net>
CommitDate: Fri Jul  5 02:02:43 2024 +0000
URL:        https://gitweb.gentoo.org/repo/proj/libressl.git/commit/?id=cfe00b76

dev-qt/qtbase: sync ::gentoo

Signed-off-by: orbea <orbea <AT> riseup.net>

 dev-qt/qtbase/qtbase-6.7.1.ebuild | 1 +
 dev-qt/qtbase/qtbase-6.7.2.ebuild | 1 +
 2 files changed, 2 insertions(+)

diff --git a/dev-qt/qtbase/qtbase-6.7.1.ebuild b/dev-qt/qtbase/qtbase-6.7.1.ebuild
index 263fbfc..cf41a45 100644
--- a/dev-qt/qtbase/qtbase-6.7.1.ebuild
+++ b/dev-qt/qtbase/qtbase-6.7.1.ebuild
@@ -283,6 +283,7 @@ src_test() {
 		tst_qlogging # backtrace log test can easily vary
 		tst_q{,raw}font # affected by available fonts / settings (bug #914737)
 		tst_qprinter # checks system's printers (bug #916216)
+		tst_qhighdpi # may detect users' settings and fail (bug #935364)
 		tst_qstorageinfo # checks mounted filesystems
 		# flaky due to using different test framework and fails with USE=-gui
 		tst_selftests

diff --git a/dev-qt/qtbase/qtbase-6.7.2.ebuild b/dev-qt/qtbase/qtbase-6.7.2.ebuild
index f994fc4..c14e136 100644
--- a/dev-qt/qtbase/qtbase-6.7.2.ebuild
+++ b/dev-qt/qtbase/qtbase-6.7.2.ebuild
@@ -281,6 +281,7 @@ src_test() {
 		tst_qlogging # backtrace log test can easily vary
 		tst_q{,raw}font # affected by available fonts / settings (bug #914737)
 		tst_qprinter # checks system's printers (bug #916216)
+		tst_qhighdpi # may detect users' settings and fail (bug #935364)
 		tst_qstorageinfo # checks mounted filesystems
 		# flaky due to using different test framework and fails with USE=-gui
 		tst_selftests


             reply	other threads:[~2024-07-05  2:04 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-05  2:04 orbea [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-22 19:28 [gentoo-commits] repo/proj/libressl:master commit in: dev-qt/qtbase/ orbea
2025-04-21  0:52 orbea
2025-04-21  0:52 orbea
2025-03-26 18:07 orbea
2025-03-26 18:07 orbea
2025-02-24 22:09 orbea
2025-02-24 22:09 orbea
2024-12-29 14:50 orbea
2024-12-02 22:26 orbea
2024-11-03  4:08 orbea
2024-09-27 16:15 orbea
2024-09-25 23:52 orbea
2024-08-01 17:58 orbea
2024-07-22  4:44 orbea
2024-07-22  4:44 orbea
2024-07-10 13:30 orbea
2024-06-28 21:14 orbea
2024-06-11 19:21 orbea
2024-05-31  0:59 orbea
2024-04-22 23:44 orbea
2024-04-02 18:50 orbea
2024-04-02 18:50 orbea
2024-03-24 15:22 orbea
2024-02-20 18:29 orbea
2024-02-16 15:02 orbea
2024-01-25 15:33 orbea
2024-01-20 15:34 orbea
2023-12-29 15:34 orbea
2023-12-06  4:58 orbea
2023-11-07 14:36 orbea
2023-10-22 16:54 orbea
2023-09-28 16:55 orbea
2023-09-17 16:22 orbea
2023-05-23 13:17 orbea
2023-04-13  2:19 orbea

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=1720144963.cfe00b762e6787556e2bcee942e65b15d8041025.orbea@gentoo \
    --to=orbea@riseup.net \
    --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