Control: severity -1 important X-Debbug-CC: peter@pblackman.plus.com bunk@debian.org On Sat, 11 Jan 2025 17:59:46 +0200 Adrian Bunk <bunk@debian.org> wrote:
Package: libtag-dev
Version: 2.0.2-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:strawberry src:kid3
https://buildd.debian.org/status/logs.php?pkg=strawberry&ver=1.2.3-1%2Bb1
...
CMake Error at /usr/lib/x86_64-linux-gnu/cmake/taglib/taglib-targets.cmake:100 (message):
The imported target "TagLib::tag_c" references the file
"/usr/lib/x86_64-linux-gnu/libtag_c.so.2.0.2"
but this file does not exist. Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
"/usr/lib/x86_64-linux-gnu/cmake/taglib/taglib-targets.cmake"
but not all the files it references.
Call Stack (most recent call first):
/usr/lib/x86_64-linux-gnu/cmake/taglib/taglib-config.cmake:37 (include)
CMakeLists.txt:202 (find_package)
-- Configuring incomplete, errors occurred!
Is there a good reason why libtag-c-dev has to be a separate package?
Merging it into libtag-dev would avoid such hassle.
A stopgap workaround has been implemented in taglib 2.0.2-2, although I agree with you that we may no longer should split between libtag-dev and libtag-c-dev. See details below. The C development files and C++ development files were put into separate packages from the very beginning because no CMake Config files were provided back then, and theses packages provide individual pkg-config files which was reasonable and self-contained. Now in the era of taglib 2.x, upstream is starting to provide the CMake config files, which is often preferred compared to the pkg-config ecosystem. However, the cmake config files integrate both the C and C++ parts, makes them unable to be separated anymore. That is the origin of this bug report. Should we just eliminate libtag-c-dev now? Or do it after next Stable release? Or ask upstream to disintegrate cmake files? I think that could be an open question. Anyway at least for now with taglib/2.0.2-2 this bug is not causing FTBFS. Thanks, Boyuan Yang
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature