Package: src:libmcfp
Version: 1.4.2-1
Severity: grave
Tags: sid
Dear maintainer:
During a rebuild of all packages in unstable, packages "cif-tools"
and "dssp" no longer build from source because of the new libmcfp-dev.
cif-tools fails in this way:
-------------------------------------------------------------------------------------------
CMake Warning (dev) at
/usr/share/cmake-3.31/Modules/FindPackageHandleStandardArgs.cmake:441 (message):
The package name passed to `find_package_handle_standard_args` (mrc) does
not match the name of the calling package (Mrc). This can lead to problems
in calling code that expects `find_package` result variables (e.g.,
`_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
/usr/share/mrc/cmake/mrc-config.cmake:84 (find_package_handle_standard_args)
CMakeLists.txt:85 (find_package)
This warning is for project developers. Use -Wno-dev to suppress it.
-- Found mrc: /usr/bin/mrc (found version "1.3.16")
CMake Error at CMakeLists.txt:99 (find_package):
By not providing "Findlibmcfp.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "libmcfp", but
CMake did not find one.
Could not find a package configuration file provided by "libmcfp" with any
of the following names:
libmcfpConfig.cmake
libmcfp-config.cmake
Add the installation prefix of "libmcfp" to CMAKE_PREFIX_PATH or set
"libmcfp_DIR" to a directory containing one of the above files. If
"libmcfp" provides a separate development package or SDK, be sure it has
been installed.
-------------------------------------------------------------------------------------------
and dssp fails in this way:
-------------------------------------------------------------------------------------------
CMake Error at CMakeLists.txt:144 (target_link_libraries):
Target "mkdssp" links to:
libmcfp::libmcfp
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.
-------------------------------------------------------------------------------------------
The options I see are:
A) Do nothing until trixie is released as stable.
This bug should prevent the new package from entering testing.
B) Reupload 1.3.5-2 as 1.4.2+really1.3.5 or similar.
Thanks.
