Your message dated Mon, 06 Jan 2025 20:49:20 +0000
with message-id <[email protected]>
and subject line Bug#1092263: fixed in sopt 4.2.0+dfsg-2
has caused the Debian Bug report #1092263,
regarding sopt: FTBFS with spdlog 1.15
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 [email protected]
immediately.)
--
1092263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092263
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sopt
Version: 4.2.0+dfsg-1
Severity: important
Tags: ftbfs
X-Debbugs-Cc: [email protected], [email protected]
Control: affects -1 src:spdlog
Dear Maintainer,
I plan to start spdlog 1.15 transition soon, your package FTBFS with it.
CMake Warning at CMakeLists.txt:97 (find_package):
By not providing "FindCatch2.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Catch2", but
CMake did not find one.
Could not find a package configuration file provided by "Catch2" with any
of the following names:
Catch2Config.cmake
catch2-config.cmake
Add the installation prefix of "Catch2" to CMAKE_PREFIX_PATH or set
"Catch2_DIR" to a directory containing one of the above files. If "Catch2"
provides a separate development package or SDK, be sure it has been
installed.
-- Configuring done (3.3s)
CMake Error at cmake_files/AddCatchTest.cmake:83 (target_link_libraries):
Target "test_bisection_method" links to:
Catch2::Catch2
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):
cpp/tests/CMakeLists.txt:27 (add_catch_test)
It seems fixable by replacing catch with catch2 in your B-D, since
libspdlog-dev does not depend on it any more.
Thanks,
Shengqi Chen
--- End Message ---
--- Begin Message ---
Source: sopt
Source-Version: 4.2.0+dfsg-2
Done: Ole Streicher <[email protected]>
We believe that the bug you reported is fixed in the latest version of
sopt, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher <[email protected]> (supplier of updated sopt package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 06 Jan 2025 20:38:00 +0100
Source: sopt
Architecture: source
Version: 4.2.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team <[email protected]>
Changed-By: Ole Streicher <[email protected]>
Closes: 1092263
Changes:
sopt (4.2.0+dfsg-2) unstable; urgency=medium
.
* Replace catch b-dep with catch2 (Closes: #1092263)
Checksums-Sha1:
4a5f52eff04fb98adf2fe0bb07e843d4e20ad19d 2145 sopt_4.2.0+dfsg-2.dsc
96fcefbc83a6d216644192aba7f6e4fb96f8fefe 6288 sopt_4.2.0+dfsg-2.debian.tar.xz
Checksums-Sha256:
1572fa59371af55325832421211b11e5946dae7c52cfd0851674f7b32eb44b6c 2145
sopt_4.2.0+dfsg-2.dsc
af2b18a647c549a5ac43004e1bdf67ffae854b19f92eb9aa0ea312cb35070840 6288
sopt_4.2.0+dfsg-2.debian.tar.xz
Files:
c8b366f86c5560b19cb8724bd5b49dd7 2145 science optional sopt_4.2.0+dfsg-2.dsc
628b9d72b37254767cfea12852c6a515 6288 science optional
sopt_4.2.0+dfsg-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAmd8PVcACgkQmk9WvbkO
GL0tBhAApHoN6ynHZBxQAWVtmyd4ogPzF3Vpf+SmIdcSgtUZyU5ghpvXFgWPmant
GR0sqmQVaY9qskKm/7gAlOMWcu2C4BYCxicHT9oguZ7cNCjml4JZua8e2qfVabCA
La7Q/GL/HEX7vGyIOuW1ykhdE9je+GV5OmMsnRFAfCMMi9KeOCyzh2hJfZsz1Oh3
0vd2ggn6nFJX860vAio2g+adeFlqoTHtLFM8NCiLKnrTyK3Grp29LjGOxyKvmwYh
mOI3QLCsIe4DqtRnAQFrM+m/OumvClHFSRCNgKyYBA0LuMBBU02luHZIsy56NtQ6
5OG9ye0eB0X1nlnCvN9jqRDapcaNl5rObF5vjJUHgfSeALxJ1DL8PkWOHyRkWnBD
67zihy9+0aUXM/5XHGeSFi0U+8IGvJ+1E7RVxL2quIpIzQ8+HaMvv4otfl6e9TZZ
qd22Iqp4QiH4mP9z0+MELUHCkq/OI8SnW1aOZ+2uFwlNsXA+gbkc8WGbiE1AkWAc
yqPystIWFBM2HvNyJDsGkCrygG+FW/YtIRZjAJ/yHB55eouLIkLSoUvlcRhYSQfO
Xpug6ZgMKzTuEzhuY9TmUtGugFHH2k5vTEe9XJPhJYO0FYYF8TLRlUw/mYOVeUVi
qkqTYmBfAJnT7CykJdxPsZx+YS/On1WXDySsH1LUgSShz/rnfUM=
=+Nm7
-----END PGP SIGNATURE-----
pgpniLGPYcGX2.pgp
Description: PGP signature
--- End Message ---
