Bug#826048: [Debian-med-packaging] Bug#826048: Faulty CMake file impairs compiling against GDCM
Thanks for your reply. But IMO it is missing the point. Maybe we should first reconsider the workflow that takes place. An application, here Ginkgo CADx, is sort of querying CMake like "Could you please tell me which library is providing feature foo?" and CMake replies "Sure. It's library /usr/lib/x86_64-linux-gnu/libFoo.so.". Due to the sophisticated packaging in Debian it may very well happen that libFoo.so isn't accessible right when cmake gets invoked simply as the package providing the library isn't installed. This is what I had in mind writing the "side note" in the initial posting and what you were referring to in your reply. But the problem addressed in this report is CMake returning faulty paths or files that aren't available in the distribution at all besides they do belong to GDCM. Could you by any chance have another look at the paragraphs after the two messages above? libvtkgdcmsharpglue.so *was installed* when cmake got invoked but wasn't found as CMake didn't know the correct path. libvtkgdcmPython.so *isn't available at all* in stretch besides it is basically part of GDCM. Apparently it was succeeded by libvtkgdcmPython.x86_64-linux-gnu.so but again CMake just isn't aware of this. And both shouldn't happen, should it?
Bug#826052: New release available
Source: vtk6 Severity: normal Upstream released 7.0.0 in February. On the one hand this is simply the current stable release and as such sure good to have in Debian anyway. That aside this particular release is introducing changes regarding the header files. So including it in Debian would help adjust other software to these changes as well. The topic was already addressed in #805010 which was mainly dealing with release 6.3.0 and got hence closed as fixed.
Bug#826050: Faulty CMake file impairs compiling against VTK
Source: vtk6 Version: 6.3.0+dfsg1-1, 6.2.0+dfsg1-11.1 Severity: important Compiling recent Ginkgo CADx against VTK on Debian testing yields two cmake warnings which suggest there are corresponding errors in the packaging of VTK. > -- The imported target "vtkRenderingPythonTkWidgets" references the file >"/usr/lib/x86_64-linux-gnu/libvtkRenderingPythonTkWidgets.so" > 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/cmake/vtk-6.2/VTKTargets.cmake" > but not all the files it references. A library libvtkRenderingPythonTkWidgets.so was provided by package libvtk6-dev in jessie (VTK 6.1) but no longer exists as of stretch (VTK 6.2). The library does still exist in more recent versions of VTK as can be seen with VTK 7.0.0 on Arch Linux, 6.3 on Arch Linux or openSUSE Leap 42.1 and 6.2 on Fedora 23. In all these distributions the naming is the typical libvtkRenderingPythonTkWidgets*-*.so that VTK upstream is using to name the third-party libraries imported into the VTK source tree, though. > -- The imported target "vtk" references the file >"/usr/bin/vtk" > 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/cmake/vtk-6.2/VTKTargets.cmake" > but not all the files it references. A binary /usr/bin/vtk is provided by package tcl-vtk in jessie but is no longer available in stretch. Package vtk6 in both stretch and jessie is providing a binary /usr/bin/vtk6 only. All findings are the same when the VTK binary packages of testing are replaced with their counterparts from sid plus their additional new or changed dependencies. The reason to assume it's a packaging issue in Debian is the fact that the warning messages can not be seen when the same Ginkgo CADx checkout gets compiled against the same VTK version on Arch Linux where packaging does not involve any tweaking of VTK's paths. On a side note I'm wondering whether it's on purpose that packages libvtk6.3[-qt] as well as libvtk6.2[-qt] are stated as belonging to source package vtk6 (6.3) of sid at https://packages.debian.org/source/sid/vtk6. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Bug#826048: Faulty CMake file impairs compiling against GDCM
Source: gdcm
Version: 2.6.3-{6,5}
Severity: important
Compiling recent Ginkgo CADx against GDCM on Debian stretch yields two cmake
warnings which
suggest there are corresponding errors in the packaging of GDCM.
> -- The imported target "vtkgdcmsharpglue" references the file
> "/usr/lib/x86_64-linux-gnu/libvtkgdcmsharpglue.so"
> 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/gdcm-2.6/GDCMTargets.cmake"
> but not all the files it references.
libvtkgdcmsharpglue.so is provided by package libvtkgdcm-cil but placed in
/usr/lib/cli/vtkgdcm-sharp-2.6/.
> -- The imported target "vtkgdcmPython" references the file
> "/usr/lib/python/dist-packages/libvtkgdcmPython.so"
> 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/gdcm-2.6/GDCMTargets.cmake"
> but not all the files it references.
libvtkgdcmPython.so isn't available any longer in stretch. It used to be
provided in jessie
(GDCM 2.4.4) by package python-vtkgdcm in /usr/lib/python2.7/dist-packages/
where a library
libvtkgdcmPython.x86_64-linux-gnu.so can be found in stretch right now.
All findings are the same when the GDCM binary packages of stretch are replaced
with their
counterparts from sid plus their additional new or changed dependencies.
The reason to assume it's a packaging issue in Debian is the fact that the
warning messages
can not be seen when the same Ginkgo CADx checkout gets compiled against the
same GDCM version
on Arch Linux where packaging does not involve any tweaking of GDCM's paths.
On a side note there's by default a bunch of similar messages, see attached
ginkgo-vs-gdcm_cmake.txt,
which are simply due to the packages providing the missing files -
libvtkgdcm2.6,
libvtkgdcm-java, python-vtkgdcm and libgdcm-tools - not being installed.
Just saying as I'm not sure whether it's alright to not have those files at
hand by default.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-- The imported target "vtkgdcm" references the file
"/usr/lib/x86_64-linux-gnu/libvtkgdcm.so.2.6.3"
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/gdcm-2.6/GDCMTargets.cmake"
but not all the files it references.
-- The imported target "vtkgdcmJava" references the file
"/usr/lib/x86_64-linux-gnu/jni/libvtkgdcmJava.so"
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/gdcm-2.6/GDCMTargets.cmake"
but not all the files it references.
-- The imported target "vtkgdcmPythonD" references the file
"/usr/lib/x86_64-linux-gnu/libvtkgdcmPythonD.so.2.6.3"
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/gdcm-2.6/GDCMTargets.cmake"
but not all the files it references.
-- The imported target "gdcmdump" references the file
"/usr/bin/gdcmdump"
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/gdcm-2.6/GDCMTargets.cmake"
but not all the files it references.
-- The imported target "gdcmdiff" references the file
"/usr/bin/gdcmdiff"
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/gdcm-2.6/GDCMTargets.cmake"
but not all the files it references.
-- The imported target "gdcmraw" references the file
"/usr/bin/gdcmraw"
but this file does not exist. Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or
Bug#824357: gl2ps: Package is setting wrong soname
Source: gl2ps Version: 1.3.8-1.2 Severity: important Current packages of GL2PS are providing a shared library libgl2ps.so.0.0.0 with soname libgl2ps.so.0 but compiling upstream code from source yields a library libgl2ps.so.1.3.8 with soname libgl2ps.so.1. Problem is due to patches which were needed to compile earlier upstream versions but haven't been adjusted to recent ones, in particular to the introduction of CMake. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
