Your message dated Mon, 20 Feb 2023 19:47:15 -0300 with message-id <2829431.mvXUDI8C0e@minerva> and subject line has caused the Debian Bug report #1030980, regarding Qt6::qmake IMPORTED_LOCATION points to build architecture qmake6 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.) -- 1030980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: qt6-base-dev User: debian-cr...@lists.debian.org Usertags: ftcbfs Control: affects -1 + src:fcitx-qt5 Hi, thanks for adding the <triplet>-qmake6 wrapper. This piece seems to work fine. The next step is making packages actually use it and this is where it gets difficult. fcitx-qt6 extracts the Qt6::qmake IMPORTED_LOCATION and expects to find a working qmake there. What it gets is the build architecture qmake instead of our lovely wrapper. Bummer. I looked into how this could be fixed and got entangled in the mess of cmake files until I completely lost track. What I found is that the imported location is (wrongly) defined in /usr/lib/<triplet>/cmake/Qt6CoreTools/Qt6CoreToolsTargets-none.cmake as ${_IMPORT_PREFIX}/lib/qt6/libexec/qmake aka /usr/lib/qt6/libexec/qmake while it should be /usr/bin/<triplet>-qmake6. Tracking down how this file is generated is where I failed. Would someone be available to support me with that task? Thanks in advance Helmut
--- End Message ---
--- Begin Message ---Version: 6.4.2+dfsg-4 Closed the wrong bug, so fixing here.signature.asc
Description: This is a digitally signed message part.
--- End Message ---