Bug#956578: libcasa-python3-4: package became uninstallable with update of libboost-python1.67.0
On Mon, 13 Apr 2020, Sebastian Ramacher wrote: This is caused by the ongoing effort to remove Python 3.7. casacore needs to be rebuilt against the new libboost-python1.67.0 version. But this build fails with: | -- Looking for python3 specific environment... | -- Found PythonInterp: /usr/bin/python3.7 (found version "3.7.7") | -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found version "3.8.2") | -- Found Boost: /usr/include (found version "1.67.0") In the source dir, find python3/CMakeLists-older-cmake.txt, in there you'll find: # Detect the python properties set(Python_ADDITIONAL_VERSIONS 3.7 3.6 3.5 3.4) add 3.8 before 3.7, so that it now reads: # Detect the python properties set(Python_ADDITIONAL_VERSIONS 3.8 3.7 3.6 3.5 3.4) then, when I run fakeroot debian/rules build it detects and tries to use python3.8. Please, see if this is enough to get the package to compile correctly with the new boost libraries. Thanks again, bye Giacomo -- _ Giacomo Mulas _ INAF - Osservatorio Astronomico di Cagliari via della scienza 5 - 09047 Selargius (CA) tel. +39 070 71180255 mob. : +39 329 6603810 _ "When the storms are raging around you, stay right where you are" (Freddy Mercury) _
Bug#956578: libcasa-python3-4: package became uninstallable with update of libboost-python1.67.0
Control: tags -1 pending Control: severity -1 serious Control: severity 956580 serious It compiles with the additional variables given as -D, and I intend to upload this soon. I however lower the severity to "serious", as this is the standard for FTBFS package (same for the aoflagger bug). Cheers Ole
Bug#956578: libcasa-python3-4: package became uninstallable with update of libboost-python1.67.0
On Mon, 13 Apr 2020, Sebastian Ramacher wrote: This is caused by the ongoing effort to remove Python 3.7. casacore needs to be rebuilt against the new libboost-python1.67.0 version. But this build fails with: | -- Looking for python3 specific environment... | -- Found PythonInterp: /usr/bin/python3.7 (found version "3.7.7") | -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found version "3.8.2") | -- Found Boost: /usr/include (found version "1.67.0") I found that the CMake build of casacore recognises these environment variables: PYTHON3_EXECUTABLE PYTHON3_LIBRARY PYTHON3_INCLUDE_DIR Did you try to explicitly set e.g. one or more of PYTHON3_EXECUTABLE=/usr/bin/python3.8 PYTHON3_LIBRARY=/usr/lib/x86_64-linux-gnu/libpython3.8.so PYTHON3_INCLUDE_DIR=/usr/include/python3.8 ? If not, could you try that and let me know? I would try myself but, as I said in my report, I pinned the boost library, so I cannot do it in the proper up to date sid environment. Bye Giacomo -- _ Giacomo Mulas _ INAF - Osservatorio Astronomico di Cagliari via della scienza 5 - 09047 Selargius (CA) tel. +39 070 71180255 mob. : +39 329 6603810 _ "When the storms are raging around you, stay right where you are" (Freddy Mercury) _
Bug#956578: libcasa-python3-4: package became uninstallable with update of libboost-python1.67.0
On Mon, 13 Apr 2020, Sebastian Ramacher wrote: This is caused by the ongoing effort to remove Python 3.7. casacore needs to be rebuilt against the new libboost-python1.67.0 version. But this build fails with: | -- Looking for python3 specific environment... | -- Found PythonInterp: /usr/bin/python3.7 (found version "3.7.7") | -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found version "3.8.2") | -- Found Boost: /usr/include (found version "1.67.0") | CMake Error at /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message): | Could NOT find Boost (missing: python37) (found version "1.67.0") | Call Stack (most recent call first): | /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 (_FPHSA_FAILURE_MESSAGE) | /usr/share/cmake-3.16/Modules/FindBoost.cmake:2179 (find_package_handle_standard_args) | python3/CMakeLists-older-cmake.txt:37 (find_package) | python3/CMakeLists.txt:4 (include) I guess this depends on CMake finding and trying to use python 3.7 instead of 3.8, even if python 3.8 libraries are then found and selected. Isn't there a way to force CMake to use python 3.8? I confess I am more familiar with autotools than with CMake, but I would be very surprised if there were not a switch in its config to explicitly select the python to use. I will try to have a look at the source package and let you know if I find it out. Thanks anyway, bye Giacomo -- _ Giacomo Mulas _ INAF - Osservatorio Astronomico di Cagliari via della scienza 5 - 09047 Selargius (CA) tel. +39 070 71180255 mob. : +39 329 6603810 _ "When the storms are raging around you, stay right where you are" (Freddy Mercury) _
Bug#956578: libcasa-python3-4: package became uninstallable with update of libboost-python1.67.0
On 2020-04-13 11:05:32 +0200, Giacomo Mulas wrote: > Package: libcasa-python3-4 > Version: 3.2.1-4+b2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > The update of libboost-python1.67.0 to 1.67.0-17+b1 on sid apparently broke > the dependencies of libcasa-python3-4, thus making it uninstallable. I am > almost sure this is a mere packaging problem, but I am not sure whether it > should be fixed in casa or in boost packages. At the moment I cannot check > in detail, since I pinned the version of boost on my laptop to avoid the > removal of libcasa-python3-4 and all packages that depend on it. > If suitable, please feel free to relay this report to the maintainer of the > boost packages. This is caused by the ongoing effort to remove Python 3.7. casacore needs to be rebuilt against the new libboost-python1.67.0 version. But this build fails with: | -- Looking for python3 specific environment... | -- Found PythonInterp: /usr/bin/python3.7 (found version "3.7.7") | -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found version "3.8.2") | -- Found Boost: /usr/include (found version "1.67.0") | CMake Error at /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message): | Could NOT find Boost (missing: python37) (found version "1.67.0") | Call Stack (most recent call first): | /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 (_FPHSA_FAILURE_MESSAGE) | /usr/share/cmake-3.16/Modules/FindBoost.cmake:2179 (find_package_handle_standard_args) | python3/CMakeLists-older-cmake.txt:37 (find_package) | python3/CMakeLists.txt:4 (include) | | | CMake Warning (dev) in /usr/share/cmake-3.16/Modules/FindBoost.cmake: | Policy CMP0011 is not set: Included scripts do automatic cmake_policy PUSH | and POP. Run "cmake --help-policy CMP0011" for policy details. Use the | cmake_policy command to set the policy and suppress this warning. | | The included script | | /usr/share/cmake-3.16/Modules/FindBoost.cmake | | affects policy settings. CMake is implying the NO_POLICY_SCOPE option for | compatibility, so the effects are applied to the including context. | Call Stack (most recent call first): | python3/CMakeLists-older-cmake.txt:37 (find_package) | python3/CMakeLists.txt:4 (include) | This warning is for project developers. Use -Wno-dev to suppress it. | | -- Configuring incomplete, errors occurred! Cheers > > Thanks in advance, best regards > Giacomo Mulas > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable > APT policy: (401, 'unstable'), (10, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.5.13-jak (SMP w/4 CPU cores) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) (ignored: LC_ALL > set to it_IT.utf8), LANGUAGE=it_IT,en_EN (charmap=UTF-8) (ignored: LC_ALL set > to it_IT.utf8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages libcasa-python3-4 depends on: > ii libboost-python1.67.0 [libboost-python1.67.0-py37] 1.67.0-17 > ii libc6 2.30-4 > ii libcasa-casa4 3.2.1-4+b2 > ii libgcc-s1 10-20200411-1 > ii libpython3.83.8.2-1+b1 > ii libstdc++6 10-20200411-1 > > libcasa-python3-4 recommends no packages. > > libcasa-python3-4 suggests no packages. > > -- no debconf information -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#956578: libcasa-python3-4: package became uninstallable with update of libboost-python1.67.0
Package: libcasa-python3-4 Version: 3.2.1-4+b2 Severity: grave Justification: renders package unusable Dear Maintainer, The update of libboost-python1.67.0 to 1.67.0-17+b1 on sid apparently broke the dependencies of libcasa-python3-4, thus making it uninstallable. I am almost sure this is a mere packaging problem, but I am not sure whether it should be fixed in casa or in boost packages. At the moment I cannot check in detail, since I pinned the version of boost on my laptop to avoid the removal of libcasa-python3-4 and all packages that depend on it. If suitable, please feel free to relay this report to the maintainer of the boost packages. Thanks in advance, best regards Giacomo Mulas -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (401, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.13-jak (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.utf8), LANGUAGE=it_IT,en_EN (charmap=UTF-8) (ignored: LC_ALL set to it_IT.utf8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libcasa-python3-4 depends on: ii libboost-python1.67.0 [libboost-python1.67.0-py37] 1.67.0-17 ii libc6 2.30-4 ii libcasa-casa4 3.2.1-4+b2 ii libgcc-s1 10-20200411-1 ii libpython3.83.8.2-1+b1 ii libstdc++6 10-20200411-1 libcasa-python3-4 recommends no packages. libcasa-python3-4 suggests no packages. -- no debconf information
