Control: reassign -1 cmake

I disagree. cmake should be able to handle the trailing indicator about
prereleases, beta releases and release candidates.

On 07.07.2017 01:11, Adrian Bunk wrote:
> Source: python2.7
> Version: 2.7.13-3
> Severity: serious
> Control: affects -1 cmake src:libsolv
> 
> mips* are the only release architectures where python2.7 2.7.13-3
> built successfully, on all other architectures it FTBFS (#866800).
> 
> This makes the following libsolv FTBFS appear only on mips*:
> 
> https://buildd.debian.org/status/package.php?p=libsolv&suite=sid
> 
> ...
> -- Found PythonLibs: /usr/lib/mips-linux-gnu/libpython2.7.so (found suitable 
> version "2.7.13+", minimum required is "2") 
> CMake Error at bindings/python/CMakeLists.txt:9 (FIND_PACKAGE):
>   find_package called with invalid argument "2.7.13+"
> 
> 
> -- Python executable: 
> -- Python installation dir: 
> -- Python include path: /usr/include/python2.7
> CMake Error at bindings/python/CMakeLists.txt:39 (INSTALL):
>   install TARGETS given no LIBRARY DESTINATION for module target
>   "bindings_python".
> 
> 
> CMake Error at bindings/python/CMakeLists.txt:40 (INSTALL):
>   install FILES given no DESTINATION!
> 
> 
> -- Python3 executable: /usr/bin/python3
> -- Python3 installation dir: /usr/lib/python3/dist-packages
> -- Python3 include path: /usr/include/python3.5m
> -- Found Perl: /usr/bin/perl (found version "5.24.1") 
> -- Perl executable: /usr/bin/perl
> -- Perl installation dir: /usr/lib/mips-linux-gnu/perl5/5.24
> -- Version: 0.6.28
> -- Writing spec file...
> -- Writing pkg-config files...
> -- Configuring incomplete, errors occurred!
> See also "/<<PKGBUILDDIR>>/obj-mips-linux-gnu/CMakeFiles/CMakeOutput.log".
> See also "/<<PKGBUILDDIR>>/obj-mips-linux-gnu/CMakeFiles/CMakeError.log".
> /usr/share/cdbs/1/class/cmake.mk:66: recipe for target 
> 'obj-mips-linux-gnu/CMakeCache.txt' failed
> make: *** [obj-mips-linux-gnu/CMakeCache.txt] Error 1
> 
> 
> It is not clear to me whether the bug is in python2.7
> or cmake (cmake maintainer Cc'ed).
> 

Reply via email to