From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Qt in core-updates (was: KDE in core-updates)
Date: Sun, 26 Feb 2023 13:44:20 +0100 [thread overview]
Message-ID: <Y/tUJH7RbW8LvSxv@jurong> (raw)
In-Reply-To: <878rglwqu4.fsf@gnu.org>
Am Sat, Feb 25, 2023 at 07:19:15PM +0100 schrieb Ludovic Courtès:
> Given the test name, one would hope that it’s the usual time bomb of an
> expired X.509 certificate.
Apparently not, just some strange handling of openssl@3; if I understand
correctly, these tests are expected to fail and should be skipped.
I may have found a solution that entails switching from Qt 6.3.1 to 6.3.2
and applying a patch. Does anyone know whether it is possible to just
increase the version of qtbase, while keeping all others at 6.3.1?
Or do we need to keep in lockstep even with patch level versions?
In any case, I realised that we are still compiling most packages (including
KDE) with Qt 5, which is seriously outdated (not maintained any more in the
free version since May 2021). Qt 6.3 support will end in April 2023,
that of the current version Qt 6.4 in September 2023. So we have the work
carved out for a (yet to be created) Qt/KDE team.
Andreas
next prev parent reply other threads:[~2023-02-26 12:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 13:59 KDE in core-updates Andreas Enge
2023-02-24 10:34 ` Andreas Enge
2023-02-25 18:19 ` Ludovic Courtès
2023-02-26 12:44 ` Andreas Enge [this message]
2023-02-26 23:43 ` Qt in core-updates (was: KDE in core-updates) Philip McGrath
2023-02-27 2:38 ` kiasoc5
2023-02-27 19:02 ` Efraim Flashner
2023-02-28 15:13 ` Andreas Enge
2023-02-28 17:59 ` Qt in core-updates Andreas Enge
2023-02-28 18:09 ` Andreas Enge
2023-02-28 18:20 ` Leo Famulari
2023-02-28 20:51 ` Andreas Enge
2023-02-28 20:55 ` Andreas Enge
2023-02-28 23:54 ` Andreas Enge
2023-03-01 0:05 ` Andreas Enge
2023-03-15 13:53 ` KDE " Andreas Enge
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y/tUJH7RbW8LvSxv@jurong \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).