Hi On 24-11-2022 21:59, Filippo Rusconi wrote:
It is weeks that I monitor the salsa stuff, but I do not understand what thesetests mean. One example (bear with me): CMake Error at CMakeLists.txt:5 (FIND_PACKAGE): By not providing "FindQt5PrintSupport.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5PrintSupport", but CMake did not find one.Could not find a package configuration file provided by "Qt5PrintSupport"with any of the following names: Qt5PrintSupportConfig.cmake qt5printsupport-config.cmake debian/control -------------- Build-Depends: debhelper (>= 13), cmake (>= 3.18), qtbase5-dev (>= 5.12), qt6-base-dev (>= 6.2.0) % apt-file search Qt5PrintSupportConfig.cmakeqtbase5-dev: /usr/lib/x86_64-linux-gnu/cmake/Qt5PrintSupport/Qt5PrintSupportConfig.cmakeSo, I do not understand why the autopkgtest does not do the right thing: installthe packages I have listed in Build-Depends...
https://ci.debian.net/data/autopkgtest/testing/amd64/q/qcustomplot/28672069/log.gz has this: """ Setting up qtbase5-dev:amd64 (5.15.6+dfsg-2+b1) ... """ So that binary is installed.
I always build my packages with cowbuilder (gbp buildpackage) in a pristineenviroment... Further, how can that be that the build passes and then the buildof autopkgtest fails?
But autopkgtest doesn't build the package (by default). It only runs the test you specify.
""" autopkgtest [15:24:02]: build not needed """So is there maybe something that the test depends on that in a full build gets built but is lacking in the test build? (I'm not experienced with cmake).
I'd be happy to learn more about all this, but for the moment these inconsistencies make me dubitative...
Maybe you can check what happens if you run the test manually (in a pristine environment)?
Paul
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature