Bug#1087385: [Pkg-cmake-team] Bug#1087385: cmake 3.31.0-1 breaks Qt6Qml builds

[Timo Röhling]

Control: reassign -1 qt6-declarative-dev
Control: retitle -1 qt6-declarative-dev depends on qt6-declarative-private-dev

* Brad King <brad.k...@kitware.com> [2024-11-14 10:21]:

On Thu, Nov 14, 2024 at 7:14 AM Sune Stolborg Vuorela wrote:

> * https://gitlab.kitware.com/cmake/cmake/-/issues/25728

I suggest we upload a cmake with that fix reverted as a short term solution while figuring out what to do with the rest of it What does the cmake maintainers say?

It seems that `qt6-declarative-dev`'s `Qt6QmlTargets.cmake` has a dependency on content of `qt6-declarative-private-dev`, so why not express that dependency in the `qt6-declarative-dev` package?

I think this is the best short term solution, as it accurately reflects the current state of affairs. I understand the Qt/KDE Maintainers' desire to keep the private API separate (and I agree with the notion), but the onus is on them to make it work, not on CMake to retain loopholes.

Cheers
Timo


--
⢀⣴⠾⠻⢶⣦⠀   ╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling                                       │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄⠀⠀⠀⠀   ╰────────────────────────────────────────────────────╯

Besides, this keeps the issue contained within a single source package, so it is easy to drop the workaround as soon as the underlying problem has been solved, without the need to involve the CMake maintainers and possibly the Release Team in case the fix will be delayed beyond the toolchain freeze for trixie.

signature.asc
Description: PGP signature