Bug#1028527: i2masschroq: FTBFS in local pbuilder

[Tobias Frost]

Source: i2masschroq
Version: 0.4.54-1
Severity: serious
Tags: ftbfs
Justification: FTBFS

Dear maintainer,

I've observerd that the package is currently not built for sid.
It is in state "Dep-Wait (libodsstream-dev (>= 0.9.1-2.1))",
so to investiate the reason I've tried to locally build it in a sid pbuilder env.

It fails with

CMake Error at /usr/lib/x86_64-linux-gnu/cmake/QCustomPlot/QCustomPlotTargets.cmake:71 (set_target_properties):
The link interface of target "QCustomPlot::QCustomPlot" contains:

Qt5::Widgets

but the target was not found. Possible reasons include:

* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.

Call Stack (most recent call first):
/usr/lib/x86_64-linux-gnu/cmake/QCustomPlot/QCustomPlotConfig.cmake:37 (include)
CMakeStuff/toolchains/unix-toolchain.cmake:23 (find_package)
CMakeLists.txt:118 (include)


CMake Error at /usr/lib/x86_64-linux-gnu/cmake/odsstream/OdsStreamTargets.cmake:71 (set_target_properties):
The link interface of target "OdsStream::Core" contains:

Qt6::Xml

but the target was not found. Possible reasons include:

* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.


Interestingly, it seems to mix Qt5 with Qt6… That looks weird.
(It seems to be *possible* to do so, but it is not officially supported, according
to [1])

Said that, it might be that this bug is either in libqcustomplot or libodsstream or both…

Please reassign if you think so…

[1] https://doc.qt.io/qt-6/cmake-qt5-and-qt6-compatibility.html#mixing-qt-5-and-qt-6

[Debian Bug Tracking System]

Your message dated Tue, 15 Oct 2024 17:58:10 +0000
with message-id <E1t0loA-009gHy-***@fasolo.debian.org>
and subject line Bug#1081324: Removed package(s) from unstable
has caused the Debian Bug report #1028527,
regarding i2masschroq: FTBFS in local pbuilder
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 ***@bugs.debian.org
immediately.)