Your message dated Thu, 13 Mar 2025 17:30:44 +0100
with message-id <1df3706e-29c2-4caa-89c1-c7ada7d12...@debian.org>
and subject line Re: Bug#1098901: transition: Qt 6.8.2
has caused the Debian Bug report #1098901,
regarding transition: Qt 6.8.2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1098901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: delta...@debian.org
User: release.debian....@packages.debian.org
Usertags: transition

Hi Release Team,

we would like to request a transition for Qt 6.8.2 such that it can make it
into trixie.
As usual, we have the ABI changes for the private headers. In addition, one
binary package has been removed (qml6-module-qtqml-base), so 2 packages
depending on it need to be binNMUed as well for that.

This time, we did not build reverse dependencies against Qt 6.8.2 due to a
lack of time. However, Ubuntu has already done the transition to Qt 6.8.2
and their packaging is based on ours. Any issue we encounter, Ubuntu has
likely faced as well and maybe fixes have already been backported to
Debian.
pyside6 which can be difficult builds sucessfully against Qt 6.8.2 and
will simply have to uploaded once Qt 6.8.2 is uploaded to unstable.
KDE packages normally don't cause issues as they get build aginst new
Qt version all the time.


Here is the Ben file:

title = "Qt 6.8.2";
is_affected = .depends ~ /qt6-.*-private-abi \(= 6\.7\.2\)/ | .depends ~ 
/qt6-.*-private-abi \(= 6\.8\.2\)/ & .depends ~ 
/\b(qml6\-module\-qtqml\-base)\b/;
is_good = .depends ~ /qt6-.*-private-abi \(= 6\.8\.2\)/ & !.depends ~ 
/\b(qml6\-module\-qtqml\-base)\b/;
is_bad = .depends ~ /qt6-.*-private-abi \(= 6\.7\.2\)/ & .depends ~ 
/\b(qml6\-module\-qtqml\-base)\b/;


I hope I didn't screw up the Ben file. Thank you very much.


-- 
Med vänliga hälsningar

Patrick Franz

--- End Message ---
--- Begin Message ---
On 06/03/2025 10:25, Emilio Pozuelo Monfort wrote:
On 01/03/2025 11:03, Emilio Pozuelo Monfort wrote:
Control: tags -1 confirmed

On 01/03/2025 01:09, Patrick Franz wrote:
Hej Emilio,

Am Donnerstag, 27. Februar 2025, 08:47:58 MEZ schrieb Emilio Pozuelo
Monfort:
[...]
This close to the freeze, we'll need test rebuild results. And note
that the freeze is just around the corner, so please provide them
quickly if you want to see this in trixie.

I've managed to test build all packages against Qt 6.8.2 in
experimental.

* 3 packages (layer-shell-qt, libkscreen, plasma-workspace) produce
symbol errors, but they are easily fixable once these packages have been
built against Qt 6.8.2 in unstable.

* pyside6 in unstable will highly likely fail to build against 6.8.2,
but the version in experimental builds successfully against 6.8.2 and
just needs to be uploaded simultaneously.

* I could not verify nvidia-cuda-toolkit as I ran out of memory.

The remaining packages all build successfully against Qt 6.8.2.

That sounds good. Please go ahead.

There seems to be a test regression with pyqt6, which is blocking the
transition. Can you take a look?

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pyqt6/58505053/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pyqt6/58505053/log.gz

I added some hints, and Qt6 migrated.

Cheers,
Emilio

--- End Message ---

Reply via email to