GNU bug report logs - #76044
Request for merging "qt-team" branch

Previous Next

To reply to this bug, email your comments to 76044 AT debbugs.gnu.org.
There is no need to reopen the bug first.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: 宋文武 <iyzsong <at> envs.net>
To: guix-patches <at> gnu.org
Cc: Maxim Cournoyer <maxim.cournoyer <at> gmail>
Subject: Request for merging "qt-team" branch
Date: Tue, 04 Feb 2025 15:26:13 +0800

Hello, this marks the beginning of work on the next iteration of the
qt-team branch.

Now include:
- Update freetype to 2.13.3, Qt requires at least 2.13.1 now for FT_LOAD_NO_SVG.
- Update Qt6 libraries to 6.8.2.
- Update qtcreator to 15.0.1.
- qtwebengine: Set default path for QtWebEngineProcess.
  https://issues.guix.gnu.org/75966
- Update python-pyqt to 6.8.0, planed, not commited yet.

Thanks.

Message #8 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: John Kehayias <john.kehayias <at> protonmail.com>
To: 宋文武 <iyzsong <at> envs.net>
Cc: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>, 76044 <at> debbugs.gnu.org
Subject: Re: bug#76044: Request for merging "qt-team" branch
Date: Sun, 09 Feb 2025 21:16:21 +0000

Hi,

On Tue, Feb 04, 2025 at 03:26 PM, 宋文武 wrote:

> Hello, this marks the beginning of work on the next iteration of the
> qt-team branch.
>
> Now include:
> - Update freetype to 2.13.3, Qt requires at least 2.13.1 now for
> FT_LOAD_NO_SVG.

Regarding the freetype upgrade, could you include adding brotli as in
input and doing away with freetype-with-brotli? This is the original
discussion on this: <https://issues.guix.gnu.org/64519#4> and the
commit:
<https://git.savannah.gnu.org/cgit/guix.git/commit/?id=49b0a5ee5f908d8efa8e792f8635f723fd1d26ed>

It has been a while, but I don't know of any reason why we wouldn't have
brotli (like other distros I had checked at the time) in freetype. I
think there are only a few users of freetype-with-brotli so it is an
easy enough change.

If you agree, feel free to make that change or I can push it directly on
qt-team branch as well.

Thanks!
John

> - Update Qt6 libraries to 6.8.2.
> - Update qtcreator to 15.0.1.
> - qtwebengine: Set default path for QtWebEngineProcess.
>   https://issues.guix.gnu.org/75966
> - Update python-pyqt to 6.8.0, planed, not commited yet.
>
> Thanks.

Message #11 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: 宋文武 <iyzsong <at> envs.net>
To: John Kehayias <john.kehayias <at> protonmail.com>
Cc: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>, 76044 <at> debbugs.gnu.org
Subject: Re: bug#76044: Request for merging "qt-team" branch
Date: Mon, 10 Feb 2025 09:48:22 +0800

John Kehayias <john.kehayias <at> protonmail.com> writes:

> [...]
> Regarding the freetype upgrade, could you include adding brotli as in
> input and doing away with freetype-with-brotli? This is the original
> discussion on this: <https://issues.guix.gnu.org/64519#4> and the
> commit:
> <https://git.savannah.gnu.org/cgit/guix.git/commit/?id=49b0a5ee5f908d8efa8e792f8635f723fd1d26ed>
>
> It has been a while, but I don't know of any reason why we wouldn't have
> brotli (like other distros I had checked at the time) in freetype.

It turn out to it would have dependency cycle due to python -> tk ->
freetype and brotli -> cmake-minimal -> jsoncpp -> meson -> python ->
freetype..

So I think better do it in another branch, thanks.

Message #14 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: 宋文武 <iyzsong <at> envs.net>
To: 76044 <at> debbugs.gnu.org
Cc: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Subject: Re: [bug#76044] Request for merging "qt-team" branch
Date: Mon, 10 Feb 2025 10:33:12 +0800

宋文武 <iyzsong <at> envs.net> writes:

> Hello, this marks the beginning of work on the next iteration of the
> qt-team branch.
>
> Now include:
> - Update freetype to 2.13.3, Qt requires at least 2.13.1 now for FT_LOAD_NO_SVG.
> - Update Qt6 libraries to 6.8.2.
> - Update qtcreator to 15.0.1.
> - qtwebengine: Set default path for QtWebEngineProcess.
>   https://issues.guix.gnu.org/75966
> - Update python-pyqt to 6.8.0, planed, not commited yet.

Qt updates all seems fine, also update Qt5 to 5.15.16, following
commits are available on the qt-team branch:

f6ba1f8e25 gnu: python-pyqt: Update to 5.15.11.
dc84d8ba52 gnu: qtdatavis3d: Rename to qtdatavis3d-5.
8c2f03799b gnu: qtpurchasing: Rename to qtpurchasing-5.
14560ce7be gnu: qtgamepad: Rename to qtgamepad-5.
856627b28e gnu: qtwebglplugin: Rename to qtwebglplugin-5.
8607a2e20e gnu: qtxmlpatterns: Rename to qtxmlpatterns-5.
742efa807f gnu: qtwebview: Rename to qtwebview-5.
91820a40ab gnu: qtscript: Rename to qtscript-5.
c8fc3dade7 gnu: qtserialbus: Rename to qtserialbus-5.
8d10484b1e gnu: python-shiboken-2: Update to 5.15.16.
992432d76f gnu: qtsensors-5: Update to 5.15.16.
fbc1bea287 gnu: qtsensors-5: Change 'name' to 'qtsensors'.
d4f2b575f8 gnu: qtwebengine-5: Update to 5.15.16.
b4a827dd6e gnu: qtvirtualkeyboard-5: Update to 5.15.16.
1f6169106d gnu: qtspeech-5: Update to 5.15.16.
c7c1b8dbe0 gnu: qtnetworkauth-5: Update to 5.15.16.
34194f706d gnu: qtdatavis3d: Update to 5.15.16.
ec88e60251 gnu: qtcharts-5: Update to 5.15.16.
4bad3afd50 gnu: qtpurchasing: Update to 5.15.16.
0d3462b839 gnu: qtscxml-5: Update to 5.15.16.
ab58b7277e gnu: qtgamepad: Update to 5.15.16.
3e0c351ad1 gnu: qtgraphicaleffects: Update to 5.15.16.
eafb227e56 gnu: qtquickcontrols2-5: Update to 5.15.16.
daae008e59 gnu: qtquickcontrols-5: Update to 5.15.16.
7e69d0e5f3 gnu: qtscript: Update to 5.15.16.
3f9844c826 gnu: qttools-5: Update to 5.15.16.
f6507df7a2 gnu: qtlocation-5: Update to 5.15.16.
56414bd5ea gnu: qtwebview: Update to 5.15.16.
6b6cd7154d gnu: qtwebglplugin: Update to 5.15.16.
62a61367d2 gnu: qtwebchannel-5: Update to 5.15.16.
46619e3896 gnu: qtserialbus: Update to 5.15.16.
e74d3b8dad gnu: qtserialport-5: Update to 5.15.16.
c90fc85c81 gnu: qtwayland-5: Update to 5.15.16.
4cb9d921a2 gnu: qtmultimedia-5: Update to 5.15.16.
2bb2968ce4 gnu: qtwebsockets-5: Update to 5.15.16.
6a297d054d gnu: qtconnectivity-5: Update to 5.15.16.
0c852d166b gnu: qtdeclarative-5: Update to 5.15.16.
5ef080b342 gnu: qtxmlpatterns: Update to 5.15.16.
56128e6729 gnu: qtx11extras: Update to 5.15.16.
8537b312f9 gnu: qtimageformats-5: Update to 5.15.16.
2baca64f12 gnu: qtsvg-5: Update to 5.15.16.
487a801352 gnu: qt3d-5: Update to 5.15.16.
f6b01e7136 gnu: qtbase-5: Update to 5.15.16.
5472af810e gnu: python-pyqtwebengine-6: Update to 6.8.0.
a81fdb6149 gnu: python-pyqt-6: Update to 6.8.1.
964970dbfc gnu: python-pyqt6-sip: Update to 13.10.0.
8ac70f6d19 gnu: python-pyqt5-sip: Update to 12.17.0.
102e5fe499 gnu: python-pyqt-builder: Update to 1.18.0.
b24823b06e gnu: qt-creator: Update to 15.0.1.
c205062579 gnu: qthttpserver: Update to 6.8.2.
73ad0621b0 gnu: python-shiboken-6: Update to 6.8.2.
1913e5e7ce gnu: qtwebengine: Update to 6.8.2.
dc2983f99c gnu: Add lld-as-ld-wrapper-18.
9c7c4d3024 gnu: ffmpeg: Add 'av_stream_get_first_dts' patch for QtWebEngine.
3d0f9a4b44 gnu: qtspeech: Update to 6.8.2.
937ff9cb87 gnu: qtremoteobjects: Update to 6.8.2.
d2895dd391 gnu: qtnetworkauth: Update to 6.8.2.
ead622a543 gnu: qtcharts: Update to 6.8.2.
9f956735e7 gnu: qtpositioning: Update to 6.8.2.
e6b4d9a458 gnu: qtscxml: Update to 6.8.2.
62d0a3984e gnu: qttranslations: Update to 6.8.2.
52e06487d1 gnu: qttools: Update to 6.8.2.
c7b4167ce1 gnu: qtlottie: Update to 6.8.2.
111036aad4 gnu: qtlocation: Update to 6.8.2.
6d9cd61f66 gnu: qtlanguageserver: Update to 6.8.2.
d0a121054e gnu: qtwebchannel: Update to 6.8.2.
5aeb8ba01a gnu: qtserialport: Update to 6.8.2.
f08878de0a gnu: qtwayland: Update to 6.8.2.
19c3af2b42 gnu: qtmultimedia: Update to 6.8.2.
ab8e0f4997 gnu: qtshadertools: Update to 6.8.2.
314aaa3f99 gnu: qtsensors: Update to 6.8.2.
384d0ad282 gnu: qtwebsockets: Update to 6.8.2.
9218df5f9f gnu: qtconnectivity: Update to 6.8.2.
83c915b784 gnu: qtdeclarative: Update to 6.8.2.
06f9d58412 gnu: qtimageformats: Update to 6.8.2.
4cfcdff2da gnu: qtsvg: Update to 6.8.2.
c85dcc7d96 gnu: qt5compat: Update to 6.8.2.
4c1756e701 gnu: qtbase: Update to 6.8.2.
38fd7bb123 gnu: agg: Fix build with newer freetype.
a24e54d274 gnu: ftgl: Fix build with newer freetype.
d84c89a185 gnu: freetype: Update to 2.13.3.


For x86_64, following packages are broken only on qt-team, will checking them later:
converseen.x86_64-linux
distrho-ports.x86_64-linux
fcitx5-qt.x86_64-linux
helm.x86_64-linux
jami.x86_64-linux
java-testng.x86_64-linux
karchive.x86_64-linux
kconfig.x86_64-linux
kdsoap-qt6.x86_64-linux
kmime.x86_64-linux
kwayland.x86_64-linux
kwidgetsaddons.x86_64-linux
mixxx.x86_64-linux
mkvtoolnix.x86_64-linux
neko.x86_64-linux
obs.x86_64-linux
opencascade-occt.x86_64-linux
python-ndindex.x86_64-linux
r-sanssouci.x86_64-linux
rust-ci-info.x86_64-linux
rust-nix.x86_64-linux
valeronoi.x86_64-linux

Message #17 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: 宋文武 <iyzsong <at> envs.net>
Cc: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>, 76044 <at> debbugs.gnu.org
Subject: Re: [bug#76044] Request for merging "qt-team" branch
Date: Mon, 7 Apr 2025 16:17:32 +0200

Hello,

as qt-team is moving towards the front of the queue (it will depend a
bit on whether python-team and core-packages-team will get ready soon
and jump back to the front of the queue, and how fast elogin-updates and
node-team will be handled), I have rebased the branch on a recent master
commit known to data.qa.guix.gnu.org and pushed. The previous branch is
still around as qt-team-old, just in case.

Andreas

Message #20 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: 宋文武 <iyzsong <at> envs.net>
Cc: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>, 76044 <at> debbugs.gnu.org
Subject: Re: [bug#76044] Request for merging "qt-team" branch
Date: Fri, 11 Apr 2025 18:21:03 +0200

Hello,

after the merge of the elogind-updates branch, I have rebased again on
master, without any problems.

Andreas

Message #23 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: 宋文武 <iyzsong <at> envs.net>
Cc: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>, 76044 <at> debbugs.gnu.org
Subject: Re: [bug#76044] Request for merging "qt-team" branch
Date: Sun, 13 Apr 2025 14:34:58 +0200

And now I have pushed node-team to master and rebased qt-team on it.
python-team is next in line, but already built out by QA. So QA should
normally pick up and start building qt-team in the next few hours.

Andreas

Message #26 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Andreas Enge <andreas <at> enge.fr>
Cc: 76044 <at> debbugs.gnu.org, 宋文武 <iyzsong <at> envs.net>
Subject: Re: [bug#76044] Request for merging "qt-team" branch
Date: Mon, 14 Apr 2025 15:50:10 +0900

Hi Andreas,

Andreas Enge <andreas <at> enge.fr> writes:

> And now I have pushed node-team to master and rebased qt-team on it.
> python-team is next in line, but already built out by QA. So QA should
> normally pick up and start building qt-team in the next few hours.

Thanks, you are a good chef d'orchestre :-).

-- 
Thanks,
Maxim

Message #29 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: 宋文武 <iyzsong <at> envs.net>
Cc: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>, 76044 <at> debbugs.gnu.org
Subject: Re: [bug#76044] Request for merging "qt-team" branch
Date: Wed, 16 Apr 2025 12:16:27 +0200

Hello all,

after the merge of r-team branch, I have rebased (without problems) and
pushed. The branch has been building, do you see any problems?

I will be away for about 10 days, so will let you orchestrate the music
yourself :)  Maybe coordinate avec python-team to see who is ready
to merge first.

Andreas

Message #32 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Sharlatan Hellseher <sharlatanus <at> gmail.com>
To: 76044 <at> debbugs.gnu.org
Cc: andreas <at> enge.fr, maxim.cournoyer <at> gmail.com, iyzsong <at> envs.net
Subject: Request for merging "qt-team" branch
Date: Sat, 19 Apr 2025 17:12:01 +0100

[Message part 1 (text/plain, inline)]

Hello all,

This branch is the next train to park to the master depot.

Affter the merge of python-team branch, I have rebased (with no issues)
and pushed.

--
Oleg

[signature.asc (application/pgp-signature, inline)]

Message #35 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Sharlatan Hellseher <sharlatanus <at> gmail.com>
Cc: iyzsong <at> envs.net, maxim.cournoyer <at> gmail.com, 76044 <at> debbugs.gnu.org
Subject: Re: Request for merging "qt-team" branch
Date: Mon, 28 Apr 2025 16:19:09 +0200

Hello Oleg,

thanks for handling the python-team merge!

I have also just rebased qt-team on a branch known to the data service:
   https://data.qa.guix.gnu.org/revision/56999614a45449c4b93c8614540210b609c2b356
see also
   https://data.qa.guix.gnu.org/repository/1/branch/master

again without problems, and pushed.

Andreas

Message #38 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Sharlatan Hellseher <sharlatanus <at> gmail.com>
Cc: iyzsong <at> envs.net, maxim.cournoyer <at> gmail.com, 76044 <at> debbugs.gnu.org
Subject: Re: Request for merging "qt-team" branch
Date: Sat, 3 May 2025 18:12:11 +0200

Hello all,

qt-team is almost built by QA:
   https://qa.guix.gnu.org/branch/qt-team
So far I see no newly failed builds, just a few blocked ones;
if you think that the branch is ready, please feel free to push
to master soon.

Andreas

Message #41 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: 宋文武 <iyzsong <at> envs.net>
To: Andreas Enge <andreas <at> enge.fr>
Cc: 76185 <at> debbugs.gnu.org, Sharlatan Hellseher <sharlatanus <at> gmail.com>,
 maxim.cournoyer <at> gmail.com, 76044 <at> debbugs.gnu.org,
 Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
Subject: Re: Request for merging "qt-team" branch
Date: Sun, 04 May 2025 13:11:45 +0800

Andreas Enge <andreas <at> enge.fr> writes:

> Hello all,
>
> qt-team is almost built by QA:
>    https://qa.guix.gnu.org/branch/qt-team
> So far I see no newly failed builds, just a few blocked ones;
> if you think that the branch is ready, please feel free to push
> to master soon.

Hi, compared with master 15 packages are failed according to the data
service:

https://data.qa.guix.gnu.org/compare/package-derivations?base_commit=56999614a45449c4b93c8614540210b609c2b356&target_commit=49958a6a2ae31259d35bfb9ed5912db96643ce9a&system=x86_64-linux&target=none&build_change=broken&after_name=&limit_results=&all_results=on

florence                     0.6.3
gnuradio                     3.10.11.0
jami                         20240524.0
kconfig                      6.5.0
kdsoap-qt6                   2.2.0
kmime                        24.05.2
kwidgetsaddons               6.5.0
libnode                      22.14.0
obs-source-copy              0.2.4
obs-vkcapture                1.5.0
optizelle                    1.3.0-0.ed4160b
python-pytz-deprecation-shim 0.1.0.post0
python-tensorly              0.9.0
rust-jemalloc-ctl            0.5.4
savane                       3.10

Particularly kmime and kconfig, which block all other KDE packages, I
took a quick look but haven't figure them out.

I think we should fix those, while other branches (next is tex-team) can
go first.

Thanks.

Message #44 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: 宋文武 <iyzsong <at> envs.net>
To: Andreas Enge <andreas <at> enge.fr>
Cc: Sharlatan Hellseher <sharlatanus <at> gmail.com>, maxim.cournoyer <at> gmail.com,
 76044 <at> debbugs.gnu.org
Subject: Re: Request for merging "qt-team" branch
Date: Sun, 04 May 2025 15:16:49 +0800

宋文武 <iyzsong <at> envs.net> writes:

> Particularly kmime and kconfig, which block all other KDE packages, I
> took a quick look but haven't figure them out.

I have fixed kmime (by set LC_ALL=en_US.utf8) and kconfig (by upgrade to
6.13.0) locally.

Will update the qt-team branch some minutes later, with KDE frameworks
6.13.0.

Message #47 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: 宋文武 <iyzsong <at> envs.net>
Cc: Sharlatan Hellseher <sharlatanus <at> gmail.com>, maxim.cournoyer <at> gmail.com,
 76044 <at> debbugs.gnu.org
Subject: Re: Request for merging "qt-team" branch
Date: Mon, 5 May 2025 12:19:02 +0200

Hello,

Am Sun, May 04, 2025 at 03:16:49PM +0800 schrieb 宋文武:
> I have fixed kmime (by set LC_ALL=en_US.utf8) and kconfig (by upgrade to
> 6.13.0) locally.
> Will update the qt-team branch some minutes later, with KDE frameworks
> 6.13.0.

thanks for the updates!

I am still learning how QA works. At
   https://qa.guix.gnu.org/branch/qt-team
things look good, on x86_64 there are fewer packages failing on qt-team
than on master.
But when clicking through on the 471 failing packages in qt-team, I see at
   https://qa.guix.gnu.org/branch/qt-team/package-changes?x86_64-linux-change=broken&x86_64-linux-change=still-failing&x86_64-linux-change=unknown-to-failing&x86_64-linux-change=new-failing
that some packages are newly failing, which look important, such as
akonadi and kwin.

The build log for kwin shows a few failing tests:
   https://bordeaux.guix.gnu.org/build/6d95a42b-ce81-4e4a-a013-def0abd6a7c1/log

92% tests passed, 10 tests failed out of 130

Total Test time (real) = 445.23 sec

The following tests FAILED:
	 20 - kwin-testLockScreen (Failed)
	 33 - kwin-testTabBox (Failed)
	 36 - kwin-testKeyboardLayout (Failed)
	 60 - kwin-testQuickTiling (Failed)
	 62 - kwin-testDbusInterface (Failed)
	 73 - kwin-testVirtualKeyboardDBus (Failed)
	 74 - kwin-testGlobalShortcuts (Failed)
	 75 - kwin-testKWinBindings (Failed)
	 78 - kwin-testMinimizeAllScript (Failed)
	 87 - kwin-testLibinputDevice (Failed)
Errors while running CTest

Andreas

Message #50 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: 宋文武 <iyzsong <at> envs.net>
To: Andreas Enge <andreas <at> enge.fr>
Cc: Sughosha <sughosha <at> disroot.org>, Zheng Junjie <z572 <at> z572.online>,
 Sharlatan Hellseher <sharlatanus <at> gmail.com>, maxim.cournoyer <at> gmail.com,
 76044 <at> debbugs.gnu.org
Subject: Re: Request for merging "qt-team" branch
Date: Mon, 05 May 2025 21:52:55 +0800

Andreas Enge <andreas <at> enge.fr> writes:

> Hello,
>
> Am Sun, May 04, 2025 at 03:16:49PM +0800 schrieb 宋文武:
>> I have fixed kmime (by set LC_ALL=en_US.utf8) and kconfig (by upgrade to
>> 6.13.0) locally.
>> Will update the qt-team branch some minutes later, with KDE frameworks
>> 6.13.0.
>
> thanks for the updates!
>
> I am still learning how QA works. At
>    https://qa.guix.gnu.org/branch/qt-team
> things look good, on x86_64 there are fewer packages failing on qt-team
> than on master.
> But when clicking through on the 471 failing packages in qt-team, I see at
>    https://qa.guix.gnu.org/branch/qt-team/package-changes?x86_64-linux-change=broken&x86_64-linux-change=still-failing&x86_64-linux-change=unknown-to-failing&x86_64-linux-change=new-failing
> that some packages are newly failing, which look important, such as
> akonadi and kwin.

Yes, it seems update the KDE framwork libraries to 6.13.0 only is not
good enough.


CC to the KDE team, I think it's time to do a full KDE upgrade here on
the qt-team branch with Plasma 6.3.4 and Gear (Applications) 25.04.
What do you think?  thanks!

Message #53 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Greg Hogan <code <at> greghogan.com>
To: 宋文武 <iyzsong <at> envs.net>
Cc: Sharlatan Hellseher <sharlatanus <at> gmail.com>, 76044 <at> debbugs.gnu.org,
 maxim.cournoyer <at> gmail.com, Sughosha <sughosha <at> disroot.org>,
 Andreas Enge <andreas <at> enge.fr>, Zheng Junjie <z572 <at> z572.online>
Subject: Re: [bug#76044] Request for merging "qt-team" branch
Date: Mon, 5 May 2025 14:37:07 -0400

On Mon, May 5, 2025 at 9:49 AM 宋文武 via Guix-patches via
<guix-patches <at> gnu.org> wrote:
>
[...cut...]
>
> Yes, it seems update the KDE framwork libraries to 6.13.0 only is not
> good enough.
>
> CC to the KDE team, I think it's time to do a full KDE upgrade here on
> the qt-team branch with Plasma 6.3.4 and Gear (Applications) 25.04.
> What do you think?  thanks!

You can close this issue to allow other team branches to be processed
and you will reclaim your position at the head of the queue when your
patches are ready and you reopen this issue.

Message #56 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Z572 <z572 <at> z572.online>
To: 宋文武 <iyzsong <at> envs.net>
Cc: Sharlatan Hellseher <sharlatanus <at> gmail.com>, 76044 <at> debbugs.gnu.org,
 maxim.cournoyer <at> gmail.com, Sughosha <sughosha <at> disroot.org>,
 Andreas Enge <andreas <at> enge.fr>, Zheng Junjie <z572 <at> z572.online>
Subject: Re: Request for merging "qt-team" branch
Date: Tue, 06 May 2025 09:16:41 +0800

[Message part 1 (text/plain, inline)]

宋文武 <iyzsong <at> envs.net> writes:

> Andreas Enge <andreas <at> enge.fr> writes:
>
>> Hello,
>>
>> Am Sun, May 04, 2025 at 03:16:49PM +0800 schrieb 宋文武:
>>> I have fixed kmime (by set LC_ALL=en_US.utf8) and kconfig (by upgrade to
>>> 6.13.0) locally.
>>> Will update the qt-team branch some minutes later, with KDE frameworks
>>> 6.13.0.
>>
>> thanks for the updates!
>>
>> I am still learning how QA works. At
>>    https://qa.guix.gnu.org/branch/qt-team
>> things look good, on x86_64 there are fewer packages failing on qt-team
>> than on master.
>> But when clicking through on the 471 failing packages in qt-team, I see at
>>    https://qa.guix.gnu.org/branch/qt-team/package-changes?x86_64-linux-change=broken&x86_64-linux-change=still-failing&x86_64-linux-change=unknown-to-failing&x86_64-linux-change=new-failing
>> that some packages are newly failing, which look important, such as
>> akonadi and kwin.
>
> Yes, it seems update the KDE framwork libraries to 6.13.0 only is not
> good enough.
>
>
> CC to the KDE team, I think it's time to do a full KDE upgrade here on
> the qt-team branch with Plasma 6.3.4 and Gear (Applications) 25.04.
> What do you think?  thanks!

I pushed some plasma updates, except for kwin, plasma-browser-integration
plasma-workspace and powerdevil.

kwin uses some functions that our current gcc does not support. However,
we cannot compile with a higher version of gcc because the qt plugin
needs to be compiled with the same compiler; otherwise, it will report
that the symbol cannot be found.

It seems that the code generated by qt in plasma-workspace also requires
a higher version of gcc for compilation; otherwise, some c++ operators
cannot be found in gcc 11.

[signature.asc (application/pgp-signature, inline)]

Message #61 received at 76044-close <at> debbugs.gnu.org (full text, mbox):

From: 宋文武 <iyzsong <at> envs.net>
To: Greg Hogan <code <at> greghogan.com>
Cc: Sharlatan Hellseher <sharlatanus <at> gmail.com>, maxim.cournoyer <at> gmail.com,
 Sughosha <sughosha <at> disroot.org>, Andreas Enge <andreas <at> enge.fr>,
 76044-close <at> debbugs.gnu.org, Zheng Junjie <z572 <at> z572.online>
Subject: Re: [bug#76044] Request for merging "qt-team" branch
Date: Tue, 06 May 2025 20:35:50 +0800

Greg Hogan <code <at> greghogan.com> writes:

> On Mon, May 5, 2025 at 9:49 AM 宋文武 via Guix-patches via
> <guix-patches <at> gnu.org> wrote:
>>
> [...cut...]
>>
>> Yes, it seems update the KDE framwork libraries to 6.13.0 only is not
>> good enough.
>>
>> CC to the KDE team, I think it's time to do a full KDE upgrade here on
>> the qt-team branch with Plasma 6.3.4 and Gear (Applications) 25.04.
>> What do you think?  thanks!
>
> You can close this issue to allow other team branches to be processed
> and you will reclaim your position at the head of the queue when your
> patches are ready and you reopen this issue.

Okay, I'm close this, and will reopen when it's ready.

Thanks.

Message #64 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: 宋文武 <iyzsong <at> envs.net>
To: Z572 <z572 <at> z572.online>
Cc: Sharlatan Hellseher <sharlatanus <at> gmail.com>, 76044 <at> debbugs.gnu.org,
 maxim.cournoyer <at> gmail.com, Sughosha <sughosha <at> disroot.org>,
 Andreas Enge <andreas <at> enge.fr>, Janneke Nieuwenhuizen <janneke <at> gnu.org>
Subject: Re: Request for merging "qt-team" branch
Date: Tue, 06 May 2025 20:44:06 +0800

Z572 <z572 <at> z572.online> writes:

> [...]
>
> I pushed some plasma updates, except for kwin, plasma-browser-integration
> plasma-workspace and powerdevil.
>
> kwin uses some functions that our current gcc does not support. However,
> we cannot compile with a higher version of gcc because the qt plugin
> needs to be compiled with the same compiler; otherwise, it will report
> that the symbol cannot be found.
>
> It seems that the code generated by qt in plasma-workspace also requires
> a higher version of gcc for compilation; otherwise, some c++ operators
> cannot be found in gcc 11.

Okay, I think we can rest for a bit and try again after
core-packages-team <https://issues.guix.gnu.org/75518>

Which will have gcc-14 by deafult.

Message #67 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: 宋文武 <iyzsong <at> envs.net>
Cc: Sharlatan Hellseher <sharlatanus <at> gmail.com>, 76044 <at> debbugs.gnu.org,
 maxim.cournoyer <at> gmail.com, Sughosha <sughosha <at> disroot.org>,
 Z572 <z572 <at> z572.online>, Janneke Nieuwenhuizen <janneke <at> gnu.org>
Subject: Re: Request for merging "qt-team" branch
Date: Tue, 6 May 2025 14:54:50 +0200

Am Tue, May 06, 2025 at 08:44:06PM +0800 schrieb 宋文武:
> Okay, I think we can rest for a bit and try again after
> core-packages-team <https://issues.guix.gnu.org/75518>
> Which will have gcc-14 by deafult.

Yes, indeed! We are close to reopening this issue.

Andreas

Message #70 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: 宋文武 <iyzsong <at> envs.net>
Cc: Andreas Enge <andreas <at> enge.fr>, Sharlatan Hellseher <sharlatanus <at> gmail.com>,
 76185 <at> debbugs.gnu.org, 76044 <at> debbugs.gnu.org,
 Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
Subject: Re: Request for merging "qt-team" branch
Date: Wed, 07 May 2025 10:54:33 +0900

Hi,

宋文武 <iyzsong <at> envs.net> writes:

> Andreas Enge <andreas <at> enge.fr> writes:
>
>> Hello all,
>>
>> qt-team is almost built by QA:
>>    https://qa.guix.gnu.org/branch/qt-team
>> So far I see no newly failed builds, just a few blocked ones;
>> if you think that the branch is ready, please feel free to push
>> to master soon.
>
> Hi, compared with master 15 packages are failed according to the data
> service:
>
> https://data.qa.guix.gnu.org/compare/package-derivations?base_commit=56999614a45449c4b93c8614540210b609c2b356&target_commit=49958a6a2ae31259d35bfb9ed5912db96643ce9a&system=x86_64-linux&target=none&build_change=broken&after_name=&limit_results=&all_results=on
>
> florence                     0.6.3
> gnuradio                     3.10.11.0
> jami                         20240524.0

Jami has a few system tests (for the jami-service-type), so ideally
should be fixed before this gets merged.

-- 
Thanks,
Maxim

Message #77 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: 76044 <at> debbugs.gnu.org, 76899 <at> debbugs.gnu.org, 78689 <at> debbugs.gnu.org
Cc: Christopher Baines <mail <at> cbaines.net>, iyzsong <at> envs.net,
 Maxim Cournoyer <maxim.cournoyer <at> gmail.com>, Greg Hogan <code <at> greghogan.com>
Subject: After the merge is before the merge
Date: Fri, 18 Jul 2025 21:13:42 +0200

Hello all,

after the core-packages-team merge, your three branches are next in
line; could you maybe rebase them on master (a commit after
4d8c55de60cf9a5cafc4b881035131921d07314d, preferably one known to the
QA data service as shown here:
   https://data.qa.guix.gnu.org/repository/1/branch/master

The qt-team branch was closed for a while, since it required the
core-packages-team branch to be merged; to repair breakage in the
latter, we actually moved some of its commits already, so part of the
branch is already applied. If you are ready, you can reopen the bug,
and qt-team will go to the front.

The nss-updates and c++-team branches come in a certain order right now,
but this needs not be fixed. Depending on how well QA and CI work,
respectively, it might also be an option to have them built by CI
instead. In theory, they should just work and just need to be built for
getting substitutes, but who knows!
As for qt-team, you may also update your updates to latest releases and
force-push the branches.

Andreas

Message #80 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Andreas Enge <andreas <at> enge.fr>
Cc: 76044 <at> debbugs.gnu.org, Christopher Baines <mail <at> cbaines.net>,
 Greg Hogan <code <at> greghogan.com>, Zheng Junjie <z572 <at> z572.online>,
 iyzsong <at> envs.net, 76899 <at> debbugs.gnu.org, 78689 <at> debbugs.gnu.org
Subject: Re: After the merge is before the merge
Date: Sat, 19 Jul 2025 21:19:31 +0900

Hi Andreas,

+CC Zheng

Andreas Enge <andreas <at> enge.fr> writes:

> Hello all,
>
> after the core-packages-team merge, your three branches are next in
> line; could you maybe rebase them on master (a commit after
> 4d8c55de60cf9a5cafc4b881035131921d07314d, preferably one known to the
> QA data service as shown here:
>    https://data.qa.guix.gnu.org/repository/1/branch/master
>
> The qt-team branch was closed for a while, since it required the
> core-packages-team branch to be merged; to repair breakage in the
> latter, we actually moved some of its commits already, so part of the
> branch is already applied. If you are ready, you can reopen the bug,
> and qt-team will go to the front.

Which bug must be reopened? The merge request?

[...]

> As for qt-team, you may also update your updates to latest releases and
> force-push the branches.

I tried to rebase it, but there are lots of tricky conflicts to resolve
in KDE applications; I'll defer to Zheng, as they authored the changes
and probably know which variants are the most up to date/correct.

-- 
Thanks,
Maxim

Message #83 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: Zheng Junjie <z572 <at> z572.online>, iyzsong <at> envs.net, 76044 <at> debbugs.gnu.org
Subject: Re: After the merge is before the merge
Date: Sat, 19 Jul 2025 14:22:55 +0200

Am Sat, Jul 19, 2025 at 09:19:31PM +0900 schrieb Maxim Cournoyer:
> Which bug must be reopened? The merge request?

Yes, the merge request, which is in cc. I have limited to the qt-team.

Andreas

Message #86 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Greg Hogan <code <at> greghogan.com>
To: Andreas Enge <andreas <at> enge.fr>
Cc: 76044 <at> debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer <at> gmail.com>,
 Christopher Baines <mail <at> cbaines.net>, iyzsong <at> envs.net, 76899 <at> debbugs.gnu.org,
 78689 <at> debbugs.gnu.org
Subject: Re: After the merge is before the merge
Date: Sat, 19 Jul 2025 16:08:58 -0400

On Fri, Jul 18, 2025 at 3:13 PM Andreas Enge <andreas <at> enge.fr> wrote:
>
> Hello all,
>
> after the core-packages-team merge, your three branches are next in
> line; could you maybe rebase them on master (a commit after
> 4d8c55de60cf9a5cafc4b881035131921d07314d, preferably one known to the
> QA data service as shown here:
>    https://data.qa.guix.gnu.org/repository/1/branch/master
>
> The qt-team branch was closed for a while, since it required the
> core-packages-team branch to be merged; to repair breakage in the
> latter, we actually moved some of its commits already, so part of the
> branch is already applied. If you are ready, you can reopen the bug,
> and qt-team will go to the front.
>
> The nss-updates and c++-team branches come in a certain order right now,
> but this needs not be fixed. Depending on how well QA and CI work,
> respectively, it might also be an option to have them built by CI
> instead. In theory, they should just work and just need to be built for
> getting substitutes, but who knows!
> As for qt-team, you may also update your updates to latest releases and
> force-push the branches.
>
> Andreas

Sharlatan has been quicker on the draw, but I have also been rebasing
the c++-team branch and fixing the conflicts on
b22edc407e34848745106ce29040bbfa29aeeec3, which showed "Failed to
import data" rather than the usual "No information yet" and did not
appear to work, and now 9bff5e0ecb40fe3988ea8b33d679dedca03a7bdc shows
green.

Greg

Message #89 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Z572 <z572 <at> z572.online>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: Andreas Enge <andreas <at> enge.fr>, iyzsong <at> envs.net, 76044 <at> debbugs.gnu.org
Subject: Re: [bug#78689] After the merge is before the merge
Date: Mon, 21 Jul 2025 10:42:26 +0800

[Message part 1 (text/plain, inline)]

Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:

> Hi Andreas,
>
> +CC Zheng
>
>> As for qt-team, you may also update your updates to latest releases and
>> force-push the branches.
>
> I tried to rebase it, but there are lots of tricky conflicts to resolve
> in KDE applications; I'll defer to Zheng, as they authored the changes
> and probably know which variants are the most up to date/correct.

after core-packages-team merged, kde update can just merge into master,
and qt6 update is always on master, so i think only qt5 update is
neededs. when https://codeberg.org/guix/guix/pulls/1376 merged, i will
rebase qt-team branch.

[signature.asc (application/pgp-signature, inline)]

Message #94 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Greg Hogan <code <at> greghogan.com>
To: Andreas Enge <andreas <at> enge.fr>
Cc: 76044 <at> debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer <at> gmail.com>,
 Christopher Baines <mail <at> cbaines.net>, iyzsong <at> envs.net, 76899 <at> debbugs.gnu.org,
 78689 <at> debbugs.gnu.org
Subject: Re: After the merge is before the merge
Date: Mon, 21 Jul 2025 10:05:14 -0400

The c++-team is currently at the head of the queue at qa.guix.gnu.org
and displays the following message:
  "Submitting builds for this branch suspended as master branch
substitute availability is low for: armhf-linux i686-linux"
and no builds have been attempted on the team branch.

Substitute availability on master is shown as 33.1% for armhf-linux
and 78.1% for i686-linux. I'm not noticing much improvement in those
numbers, but I can track this better now that I have recorded a point
in time.

This seems like a less than optimal behavior for the system to shut
down building on primary architectures for team branches when the
secondary architectures have large numbers of blocked builds,
presumably due to the recent core-packages-team merge.

Greg

Message #97 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Greg Hogan <code <at> greghogan.com>
Cc: 76044 <at> debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer <at> gmail.com>,
 Christopher Baines <mail <at> cbaines.net>, iyzsong <at> envs.net, 76899 <at> debbugs.gnu.org,
 78689 <at> debbugs.gnu.org
Subject: Re: After the merge is before the merge
Date: Mon, 21 Jul 2025 16:52:05 +0200

Hello Greg,

Am Mon, Jul 21, 2025 at 10:05:14AM -0400 schrieb Greg Hogan:
> Substitute availability on master is shown as 33.1% for armhf-linux
> and 78.1% for i686-linux. I'm not noticing much improvement in those
> numbers, but I can track this better now that I have recorded a point
> in time.
> 
> This seems like a less than optimal behavior for the system to shut
> down building on primary architectures for team branches when the
> secondary architectures have large numbers of blocked builds,
> presumably due to the recent core-packages-team merge.

indeed this is a problem! In particular now since I think the number
of buildable packages has gone below the limit of 80% on these two
architectures, so we will never reach this barrier. (I deduce this from
the numbers not going up.) However, on i686 I think we are on our way to
above 80% with all the recent changes on master.

I have submitted a PR here:
   https://codeberg.org/guix/qa-frontpage/pulls/8
and am working on integrating and deploying it.

The qt-team branch has also reopened and gone to the front of the queue,
since it had been waiting longer and just been suspended while waiting
for core-packages-team, on which it depends, to let other branches go to
the front.

The c++-team branch has started on CI as well:
   https://ci.guix.gnu.org/jobset/c++-team
but I am rather puzzled by the outcome.
The page itself shows an enormous number of failed packages in the red
box (almost all of them, plus some that are still in progress); when
clicking on the red box, I find packages such as ocaml that failed their
test phase with 0 failed tests. On the other hand, when clicking on the
dashboard (the monitor symbol to the right), almost all packages are
either green or transparent, and when one clicks on a transparent dot,
it shows the build as scheduled. But I know very little about CI.

All of qt-team, c++-team and nss-updates are accessible from CI as well,
so as soon as one of them is seen to be ready there, it can be pushed
to master.

Andreas

Message #100 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Greg Hogan <code <at> greghogan.com>
To: Andreas Enge <andreas <at> enge.fr>
Cc: 76044 <at> debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer <at> gmail.com>,
 Christopher Baines <mail <at> cbaines.net>, iyzsong <at> envs.net, 76899 <at> debbugs.gnu.org,
 78689 <at> debbugs.gnu.org
Subject: Re: After the merge is before the merge
Date: Mon, 21 Jul 2025 12:54:59 -0400

On Mon, Jul 21, 2025 at 10:52 AM Andreas Enge <andreas <at> enge.fr> wrote:
>
> The qt-team branch has also reopened and gone to the front of the queue,
> since it had been waiting longer and just been suspended while waiting
> for core-packages-team, on which it depends, to let other branches go to
> the front.

Yes, and likely a good thing since the qt-build-system inherits from
the cmake-build-system which is the focus of the c++-team branch.

The qt-team branch is rebased off the latest commit on master rather
than the latest processed commit so is showing the dreaded "Merge base
has not been processed by the data service yet".

> The c++-team branch has started on CI as well:
>    https://ci.guix.gnu.org/jobset/c++-team
> but I am rather puzzled by the outcome.
> The page itself shows an enormous number of failed packages in the red
> box (almost all of them, plus some that are still in progress); when
> clicking on the red box, I find packages such as ocaml that failed their
> test phase with 0 failed tests. On the other hand, when clicking on the
> dashboard (the monitor symbol to the right), almost all packages are
> either green or transparent, and when one clicks on a transparent dot,
> it shows the build as scheduled. But I know very little about CI.

It is helpful that the ci dashboard can select for a single
architecture, but is there a way to compare against the merge base as
with qa? On master we are concerned with the state of all packages,
but on team branches is there any other question than to find the
newly failing packages relative to the base commit?

Greg

Message #103 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Greg Hogan <code <at> greghogan.com>
Cc: 76044 <at> debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer <at> gmail.com>,
 Christopher Baines <mail <at> cbaines.net>, iyzsong <at> envs.net, 76899 <at> debbugs.gnu.org,
 78689 <at> debbugs.gnu.org
Subject: Re: After the merge is before the merge
Date: Mon, 21 Jul 2025 19:02:22 +0200

Am Mon, Jul 21, 2025 at 12:54:59PM -0400 schrieb Greg Hogan:
> The qt-team branch is rebased off the latest commit on master rather
> than the latest processed commit so is showing the dreaded "Merge base
> has not been processed by the data service yet".

Yes, but the latest commits on master are also Qt related, so we need
to wait and maybe rebase on the first commit that will have been
processed after that.

> It is helpful that the ci dashboard can select for a single
> architecture, but is there a way to compare against the merge base as
> with qa? On master we are concerned with the state of all packages,
> but on team branches is there any other question than to find the
> newly failing packages relative to the base commit?

I do not think so, I have the impression that it is always with respect
to the previous commit on the same branch.

Andreas

Message #106 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: 宋文武 <iyzsong <at> envs.net>
Cc: Z572 <z572 <at> z572.online>, maxim.cournoyer <at> gmail.com, 76044 <at> debbugs.gnu.org
Subject: Re: Request for merging "qt-team" branch
Date: Tue, 22 Jul 2025 16:50:56 +0200

Hello,

I have just rebased on the (almost latest) master commit
1187787c6fbf65cf2bfbc8860ba4ab154a0e3f94 known to data.qa.guix.gnu.org.

"guix refresh -l qtbase <at> 5" shows about 1500 packages, so once it is
started, I suppose that the branch will be built quickly.

Andreas

PS: "guix refresh -l qtbase" shows only about 1200 packages, way to go!

Message #109 received at 76044 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: 宋文武 <iyzsong <at> envs.net>
Cc: Z572 <z572 <at> z572.online>, maxim.cournoyer <at> gmail.com, 76044 <at> debbugs.gnu.org,
 mail <at> cbaines.net
Subject: Re: Request for merging "qt-team" branch
Date: Fri, 25 Jul 2025 10:52:13 +0200

Hello all,

as you can see on QA, the qt-team branch would be ready to merge from
the x86_64 perspective:
   https://qa.guix.gnu.org/branch/qt-team

On i686, there are lots of "blocked" packages, before and after; but
when I click on "qtbase" it is marked as "scheduled" and not blocked by
anything. However, qtbase <at> 5 has clearly not been built by QA for i686,
but is available on the master branch. So there is potentially a
regression. On CI I had not enabled the builds for i686 and will do so
now; I will also rebase on commit 6566207b0fe82cc6db21461fddc759c7e7bb5d49
which should get CI going on a new evaluation. And I am trying to build
qtbase <at> 5 locally.

For aarch64, I do not know the situation; qtbase <at> 5 seems to be
unavailable as well on master as on the new branch, so maybe there is no
regression preventing us from merging (although it would be good to sort
out the situation; there was some bug about Qt6 on aarch64 on Codeberg,
if I remember well).

Andreas

Message #114 received at 76044-done <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: 宋文武 <iyzsong <at> envs.net>
Cc: Z572 <z572 <at> z572.online>, maxim.cournoyer <at> gmail.com,
 76044-done <at> debbugs.gnu.org, mail <at> cbaines.net
Subject: Re: Request for merging "qt-team" branch
Date: Fri, 25 Jul 2025 16:04:43 +0200

Hi again,

QA has not picked up the rebased branch after four hours, CI does not manage
to import it. But it is Friday afternoon, what could possibly go worng? Yolo!

I have built everything up to python-pyqt <at> 5 on i686.
On aarch64, we do not get up to Qt, due to:
   https://codeberg.org/guix/guix/issues/1377
which is being fixed.

So I have pushed to master. Thanks to all who made this update possible,
in particular 宋文武!

Andreas

Message #117 received at 76044-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Andreas Enge <andreas <at> enge.fr>
Cc: Z572 <z572 <at> z572.online>, 76044-done <at> debbugs.gnu.org,
 宋文武 <iyzsong <at> envs.net>, mail <at> cbaines.net
Subject: Re: Request for merging "qt-team" branch
Date: Sat, 26 Jul 2025 11:37:29 +0900

Hi,

Andreas Enge <andreas <at> enge.fr> writes:

> Hi again,
>
> QA has not picked up the rebased branch after four hours, CI does not manage
> to import it. But it is Friday afternoon, what could possibly go worng? Yolo!
>
> I have built everything up to python-pyqt <at> 5 on i686.
> On aarch64, we do not get up to Qt, due to:
>    https://codeberg.org/guix/guix/issues/1377
> which is being fixed.
>
> So I have pushed to master. Thanks to all who made this update possible,
> in particular 宋文武!

Thank you, Andreas!

-- 
Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.