From: fvalasiad <fvalasiad@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qt6-base: Update to 6.6.3
Date: Tue, 26 Mar 2024 17:44:59 +0100 [thread overview]
Message-ID: <20240326164459.A44B121EB7@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49549@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
New comment by fvalasiad on void-packages repository
https://github.com/void-linux/void-packages/pull/49549#issuecomment-2020960387
Comment:
Ah the build failed for x86, was it cause of the failed tests? We have to patch all those?
@Johnnynator Honestly I am trying to setup plasma 6 to work and I am still trying to figure out the layout of qt in the repositories in an attempt to upgrade to qt6.
Now there is a `qt5` package creating all the subpackages but there ain't no `qt6` yet, rather there is just `qt6-base` which is a minimal version. Then there is no `qt5-base`, while additionally some subpackages originally created from `qt5` are now separate packages for `qt6`.
I wonder have you got any reason to hold back plasma 6 or is it just an issue of time? Since you mention that all qt components need to be updated in parallel, should I bother trying in my spare time?
next prev parent reply other threads:[~2024-03-26 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 14:05 [PR PATCH] qt6-base: Update to 6.6.2 fvalasiad
2024-03-26 14:10 ` fvalasiad
2024-03-26 14:13 ` fvalasiad
2024-03-26 14:14 ` fvalasiad
2024-03-26 14:25 ` [PR PATCH] [Updated] " fvalasiad
2024-03-26 14:26 ` fvalasiad
2024-03-26 15:54 ` qt6-base: Update to 6.6.3 Johnnynator
2024-03-26 16:44 ` fvalasiad [this message]
2024-03-26 19:23 ` fvalasiad
2024-06-25 1:49 ` github-actions
2024-06-25 10:14 ` [PR PATCH] [Closed]: " fvalasiad
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=20240326164459.A44B121EB7@inbox.vuxu.org \
--to=fvalasiad@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).