Your message dated Sun, 02 Feb 2025 12:23:40 +0000
with message-id <e1tez0m-009cwi...@fasolo.debian.org>
and subject line Bug#1057346: fixed in qt6-base 6.7.2+dfsg-6
has caused the Debian Bug report #1057346,
regarding qt6-base-dev-tools is wrongly marked Multi-Arch: foreign
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.)


-- 
1057346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qt6-base-dev-tools
User: debian-cr...@lists.debian.org
Severity: important
Usertags: ftcbfs
Control: affects -1 + src:kuserfeedback
X-Debbugs-Cc: debian-cr...@lists.debian.org

Hi Qt maintainers and cross people,

I think I've found one of those innocent looking cross build failures
that turn into something big. src:kuserfeedback actually cross builds
successfully, but what comes out is broken:

qml6-module-org-kde-userfeedback_1.3.0-3_arm64.deb contains
./usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/userfeedback/libKUserFeedbackQmlQt6.so

qt6-kuserfeedback-dev_1.3.0-3_arm64.deb contains
./usr/lib/x86_64-linux-gnu/qt6/mkspecs/modules/qt_KUserFeedbackCoreQt6.pri
and
./usr/lib/x86_64-linux-gnu/qt6/mkspecs/modules/qt_KUserFeedbackWidgetsQt6.pri

Evidently, something inserts build architecture multiarch libdirs
somehow and that's bad. Digging into kuserfeedback, I think the origin
of the earlier one is KDE_INSTALL_QMLDIR (see
src/provider/qml/CMakeLists.txt). Looking beyond, I think this is set
from extra-cmake-modules. It's not exactly clear to me how this comes
about to be. If you know please tell.

So I looked into how extra-cmake-modules constructs such paths and found
kde-modules/KDEInstallDirs6.cmake which looks related. I cannot really
draw the connection and assume there is one. Is that still convincing
enough? Is someone able to fill this gap?

Assuming we're still on track, I think stuff comes out of ecm_query_qt,
which is defined in modules/ECMQueryQt.cmake. This works differently for
Qt5 and Qt6. For Qt5, it invokes Qt5::qmake -query. This is something we
redirected to point at ${DEB_HOST_GNU_TYPE}-qmake and this generally
gives the right variables. Getting there was a longer journey, but this
now works neatly. What we're looking at here though is the Qt6 case and
there we use Qt6::qtpaths. As far as I understand it, this is new in
Qt6. While we did add a ${DEB_HOST_GNU_TYPE}-qmake6 wrapper script, I am
not aware of any qtpaths6 wrapper. Running it like qtpaths6 --query
QT_INSTALL_QML gives /usr/lib/x86_64-linux-gnu/qt6/qml here and that
very plausibly explains the original failure.

It also tells us that qtpaths6 definitely is not something that is
appropriate for shipping in a Multi-Arch: foreign package as is.
qt6-base-dev-tools is that package and it is currently marked
Multi-Arch: foreign. Just removing the marking is not the solution here.
We really want the qtpaths6 executable to reside in a Multi-Arch:
foreign package. Otherwise, we cannot run it. What we need here is a
wrapper script ${DEB_HOST_GNU_TYPE}-qtpaths6 for qtpaths6 that sets
architecture-dependent properties in matching ways. This probably
belongs to some Multi-Arch: same package. Then Qt6::qtpaths needs to be
redefined to point at the triplet-prefixed one. It is not clear to me
how packages have to be reorganized. That package containing
${DEB_HOST_GNU_TYPE}-qtpaths6 somehow needs to be pulled into the build
for kuserfeedback. The most obvious option is to rename
qt6-base-dev-tools to qt6-base-dev-tools-bin and use the previous name
for the Multi-Arch: same package. That may not be the best of solutions
though. Possibly, there already is a suitable Multi-Arch: same package
that is required anyway, which can hold these wrappers.

This is as far as I got. Does that make sense to you? Is that actionable
to Qt maintainers?

Helmut

--- End Message ---
--- Begin Message ---
Source: qt6-base
Source-Version: 6.7.2+dfsg-6
Done: Sandro Knauß <he...@debian.org>

We believe that the bug you reported is fixed in the latest version of
qt6-base, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Knauß <he...@debian.org> (supplier of updated qt6-base package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 02 Feb 2025 13:00:45 +0100
Source: qt6-base
Architecture: source
Version: 6.7.2+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org>
Changed-By: Sandro Knauß <he...@debian.org>
Closes: 1057346 1089600
Changes:
 qt6-base (6.7.2+dfsg-6) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * Create <triplet>-qtpaths6 cross wrapper (Closes: 1057346).
   * Fix FTCBFS: Update debian/not-installed. (Closes: #1089600)
 .
   [ Sandro Knauß ]
   * Install the qtpaths6 wrapper scripts within qt6-base-dev.
   * Remove version contrain on firebird-dev, as it does not exist << 4.0
     anymore.
Checksums-Sha1:
 db92a679be5e369f298aed558dc86f86723974d6 5470 qt6-base_6.7.2+dfsg-6.dsc
 94e02c75326545f7ea2a0731ef5565ffa9f9e0f4 184296 
qt6-base_6.7.2+dfsg-6.debian.tar.xz
 730082c2d45eea0391770504e2c5ccbc534c874e 13728 
qt6-base_6.7.2+dfsg-6_source.buildinfo
Checksums-Sha256:
 de90684974a117001f03f7343acb724d77af74ac7a618d7c64be9b086b671d98 5470 
qt6-base_6.7.2+dfsg-6.dsc
 edeac77aa956889fee30132df1559301855bb7dff424fca0468f160a5c17c49f 184296 
qt6-base_6.7.2+dfsg-6.debian.tar.xz
 91544c520a50503055528b97ae041eaf0280555f4803b546508134ca5289963d 13728 
qt6-base_6.7.2+dfsg-6_source.buildinfo
Files:
 7a009c227400cee6a3bbee03454a28ef 5470 libs optional qt6-base_6.7.2+dfsg-6.dsc
 19db177d787dececbd01cb0c6f73d757 184296 libs optional 
qt6-base_6.7.2+dfsg-6.debian.tar.xz
 84da47b164188e87dd33afbd714f508a 13728 libs optional 
qt6-base_6.7.2+dfsg-6_source.buildinfo

-----BEGIN PGP SIGNATURE-----

wsG7BAEBCgBvBYJnn16qCRDjrbAIUGBWNkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmdxbScM/vwiGJyubrTyQZnDQxFB0gql1d6DYKxYL4Ob
2hYhBDnsEaAgFrcpJkkaBuOtsAhQYFY2AABLXw/9ERuf0JgJ3UdMBhCQ6xTo6D6r
y0hSEnicPlSkfrs2BQqsoP+ByzXqmp66slNSo+LjPDcHWgjqoqw9W+VIOi6nalIp
cmGWcSpEDRy8gmt1hhO+seG24YbdkgZSaKQdkXUs90cSXWx6PJDmCywhkTKg3oyN
XrO+vRgtVou0/pSV2DX7cwN/to67BCEcDMNHt1IslKa1pTXOyi7nXMT0mS0DCgu6
ljzCMeEyjzIJ3LV8Cj+377xmFwsWH8yiz/LT9nUlAYm7NehdlenNqSqChJEaQX8A
xVriFKH54jAe+MV65KxenbvAcmT6mN5hbinluaHl41TSSc+J2Rf8zXC3nfhGN7FK
Fq8aFEa+jBx+FIFumpnEuSyX8Hrj0wYp83vV/P4SzJ25kTihCJFGVFUVrmkud84b
y7OCNT97j5zzkTdA23vS7UCKSX3Up3iYdBdSBulNt2Esu9nB9/z/C5ZLMpHgi97w
tTee2KmsF8k2u7DH2rpSnkjSTN0WOGnf75O7S1Bg960FXKadFCB6HuJoBBwMu9Ml
hrBK7Ru4z08xKRMl9tcclo8goWQ94Ldc9jk0SY3Nv5EjUHoAgaHt/ov1s99m7HXq
TKYXD7lOJKmGeG1ByZvmvzNWL5E/MujaAlBxnLWPHK5rKZ9frv2oAP2k3PHqV+9t
OMUb7fsZQTUMrxXLKUs=
=87rJ
-----END PGP SIGNATURE-----

Attachment: pgpK8NgnxMHdq.pgp
Description: PGP signature


--- End Message ---

Reply via email to