Bug#1038699: qt6-declarative-dev: files missing ... somehow

[Oswald Buddenhagen]

Package: qt6-declarative-dev
Version: 6.4.2+dfsg-1
Severity: normal

while building qt creator, cmake spits out this message during the
generation phase (that is, after configuration is done):

======
CMake Error in src/plugins/qmldesigner/CMakeLists.txt:
Imported target "Qt::QmlPrivate" includes non-existent path

"/usr/include/x86_64-linux-gnu/qt6/QtQml/6.4.2"

in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include:

* The path was deleted, renamed, or moved to another location.

* An install or uninstall procedure did not complete successfully.

* The installation package was faulty and references files it does not
provide.
======

i have no clue where this is coming from, because there are no obvious
hits for QmlPrivate in the cmake directory.

but once i install qt6-declarative-private-dev, the error goes away.

i suppose this might be some dynamic magic in the upstream code that
isn't prepared for actually being split into public and private.

-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.3.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qt6-declarative-dev depends on:
ii libqt6labsanimation6 6.4.2+dfsg-1
ii libqt6labsfolderlistmodel6 6.4.2+dfsg-1
ii libqt6labsqmlmodels6 6.4.2+dfsg-1
ii libqt6labssettings6 6.4.2+dfsg-1
ii libqt6labssharedimage6 6.4.2+dfsg-1
ii libqt6labswavefrontmesh6 6.4.2+dfsg-1
ii libqt6opengl6-dev 6.4.2+dfsg-11
ii libqt6qml6 6.4.2+dfsg-1
ii libqt6qmlcompiler6 6.4.2+dfsg-1
ii libqt6qmlcore6 6.4.2+dfsg-1
ii libqt6qmllocalstorage6 6.4.2+dfsg-1
ii libqt6qmlmodels6 6.4.2+dfsg-1
ii libqt6qmlworkerscript6 6.4.2+dfsg-1
ii libqt6qmlxmllistmodel6 6.4.2+dfsg-1
ii libqt6quick6 6.4.2+dfsg-1
ii libqt6quickcontrols2-6 6.4.2+dfsg-1
ii libqt6quickcontrols2impl6 6.4.2+dfsg-1
ii libqt6quickdialogs2-6 6.4.2+dfsg-1
ii libqt6quickdialogs2quickimpl6 6.4.2+dfsg-1
ii libqt6quickdialogs2utils6 6.4.2+dfsg-1
ii libqt6quicklayouts6 6.4.2+dfsg-1
ii libqt6quickparticles6 6.4.2+dfsg-1
ii libqt6quickshapes6 6.4.2+dfsg-1
ii libqt6quicktemplates2-6 6.4.2+dfsg-1
ii libqt6quicktest6 6.4.2+dfsg-1
ii libqt6quickwidgets6 6.4.2+dfsg-1
ii qt6-base-dev 6.4.2+dfsg-11
ii qt6-declarative-dev-tools 6.4.2+dfsg-1
ii qt6-qmltooling-plugins 6.4.2+dfsg-1

qt6-declarative-dev recommends no packages.

qt6-declarative-dev suggests no packages.

-- no debconf information

[Oswald Buddenhagen]

huh?

if the declaration of the private dependency is just missing in that qtc
plugin, then fair enough. but that doesn't explain the total garbage
error message which suggests some kind of internal error (it sort of
suggests that an incomplete package is installed like in the other bug i
reported, except that it's just not there).

please investigate whether this is a result of splitting, and forward
the bug to upstream with your findings.

[Lisandro Damian Nicanor Perez Meyer]

On miércoles, 21 de junio de 2023 05:51:37 -03 Oswald Buddenhagen wrote:
> huh?
>
> if the declaration of the private dependency is just missing in that qtc
> plugin , then fair enough.

You need the QML private headers for that part since ages.

> but that doesn't explain the total garbage
> error message which suggests some kind of internal error (it sort of
> suggests that an incomplete package is installed like in the other bug i
> reported, except that it's just not there).

Exactly, it suggests you are missing the private headers. Whoever coded that
made them a dependency. The fact that we split them and do not install them by
default makes the code show that error message.

> please investigate whether this is a result of splitting, and forward
> the bug to upstream with your findings.

No need to, the answer will be "install the private headers".

[Lisandro Damian Nicanor Perez Meyer]

On miércoles, 12 de julio de 2023 19:15:20 -03 Lisandro Damian Nicanor Perez

Meyer wrote:
> On miércoles, 21 de junio de 2023 05:51:37 -03 Oswald Buddenhagen wrote:
> > huh?
> >
> > if the declaration of the private dependency is just missing in that qtc
> > plugin , then fair enough.
>
> You need the QML private headers for that part since ages.
>
> > but that doesn't explain the total garbage
> > error message which suggests some kind of internal error (it sort of
> > suggests that an incomplete package is installed like in the other bug i
> > reported, except that it's just not there).
>
> Exactly, it suggests you are missing the private headers. Whoever coded that
> made them a dependency. The fact that we split them and do not install them
> by default makes the code show that error message.

Or maybe you where suggesting that the error message is not as helpful as a
more direct one. If that's the case... I don't think any of us will put time
on that. If you want I can reopen the bug and mark it as wishlist. But you
know the upstream procedure better than I, and maybe you can sen a patch to
upstream!

[Oswald Buddenhagen]

turns out my suspicion was correct.
the issue is tracked upstream at
https://bugreports.qt.io/browse/QTBUG-87776 .
please re-open the bug and retitle it appropriately.

[Lisandro Damián Nicanor Pérez Meyer]

reopen 1038699
reassign 1038699 src:qt6-base
tag 1038699 upstream
forwarded 1038699 https://bugreports.qt.io/browse/QTBUG-87776
thanks

I must admit I clearly did not understand you, now by reading that bug report I get it. You are right, this should be fixed. Tagging accordingly.

Thanks!!!