[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1075409: marked as done (pyliblo: ftbfs with GCC-14)

Your message dated Tue, 31 Dec 2024 16:58:50 +0000
with message-id <E1tSfZy-0076v7-Sy@fasolo.debian.org>
and subject line Bug#1075409: fixed in pyliblo 0.16.2-1
has caused the Debian Bug report #1075409,
regarding pyliblo: ftbfs with GCC-14
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 owner@bugs.debian.org
immediately.)


-- 
1075409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075409
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:pyliblo
Version: 0.10.0-6
Severity: important
Tags: sid trixie
User: debian-gcc@lists.debian.org
Usertags: ftbfs-gcc-14

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/pyliblo_0.10.0-6_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html

[...]
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:311: python3.11 setup.py clean 
running clean
removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build' (and everything under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.11' does not exist -- can't clean it
I: pybuild base:311: python3.12 setup.py clean 
running clean
removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build' (and everything under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.12' does not exist -- can't clean it
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
 debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.11 setup.py config 
running config
I: pybuild base:311: python3.12 setup.py config 
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3.11 setup.py build 
running build
running build_ext
cythoning src/liblo.pyx to src/liblo.c
/usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: Cython directive 'language_level' not set, using 2 for now (Py2). This will change in a later release! File: /<<PKGBUILDDIR>>/src/liblo.pxd
  tree = Parsing.p_module(s, pxd, full_module_name)
building 'liblo' extension
creating build
creating build/temp.linux-x86_64-cpython-311
creating build/temp.linux-x86_64-cpython-311/src
x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -Werror=implicit-function-declaration -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.11 -c src/liblo.c -o build/temp.linux-x86_64-cpython-311/src/liblo.o -fno-strict-aliasing -Werror-implicit-function-declaration -Wfatal-errors
src/liblo.c: In function ‘__pyx_f_5liblo__msg_callback’:
src/liblo.c:4764:94: error: passing argument 1 of ‘lo_blob_dataptr’ from incompatible pointer type [-Wincompatible-pointer-types]
 4764 |         __pyx_t_6 = __Pyx_PyBytes_FromCString(((unsigned char *)lo_blob_dataptr((__pyx_v_argv[__pyx_v_i])))); if (unlikely(!__pyx_t_6)) __PYX_ERR(0, 235, __pyx_L1_error)
      |                                                                                 ~~~~~~~~~~~~~^~~~~~~~~~~~
      |                                                                                              |
      |                                                                                              lo_arg *
src/liblo.c:831:78: note: in definition of macro ‘__Pyx_PyBytes_FromCString’
  831 | #define __Pyx_PyBytes_FromCString(s)   __Pyx_PyBytes_FromString((const char*)s)
      |                                                                              ^
compilation terminated due to -Wfatal-errors.
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1: /usr/bin/python3.11 setup.py build 
I: pybuild base:311: /usr/bin/python3 setup.py build 
running build
running build_ext
skipping 'src/liblo.c' Cython extension (up-to-date)
building 'liblo' extension
creating build/temp.linux-x86_64-cpython-312
creating build/temp.linux-x86_64-cpython-312/src
x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.12 -c src/liblo.c -o build/temp.linux-x86_64-cpython-312/src/liblo.o -fno-strict-aliasing -Werror-implicit-function-declaration -Wfatal-errors
src/liblo.c: In function ‘__pyx_f_5liblo__msg_callback’:
src/liblo.c:4764:94: error: passing argument 1 of ‘lo_blob_dataptr’ from incompatible pointer type [-Wincompatible-pointer-types]
 4764 |         __pyx_t_6 = __Pyx_PyBytes_FromCString(((unsigned char *)lo_blob_dataptr((__pyx_v_argv[__pyx_v_i])))); if (unlikely(!__pyx_t_6)) __PYX_ERR(0, 235, __pyx_L1_error)
      |                                                                                 ~~~~~~~~~~~~~^~~~~~~~~~~~
      |                                                                                              |
      |                                                                                              lo_arg *
src/liblo.c:831:78: note: in definition of macro ‘__Pyx_PyBytes_FromCString’
  831 | #define __Pyx_PyBytes_FromCString(s)   __Pyx_PyBytes_FromString((const char*)s)
      |                                                                              ^
compilation terminated due to -Wfatal-errors.
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1: /usr/bin/python3 setup.py build 
dh_auto_build: error: pybuild --build -i python{version} -p "3.11 3.12" returned exit code 13
make: *** [debian/rules:6: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Source: pyliblo
Source-Version: 0.16.2-1
Done: Dennis Braun <snd@debian.org>

We believe that the bug you reported is fixed in the latest version of
pyliblo, 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 1075409@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dennis Braun <snd@debian.org> (supplier of updated pyliblo 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 31 Dec 2024 15:28:18 +0100
Source: pyliblo
Architecture: source
Version: 0.16.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Dennis Braun <snd@debian.org>
Closes: 1075409
Changes:
 pyliblo (0.16.2-1) unstable; urgency=medium
 .
   * Team upload
   * Fix FTBFS with GCC-14 (Closes: #1075409)
   * Set debian-multimedia team as maintainer again
Checksums-Sha1:
 028e1383b17e73edeb63b0af6393038e07b48727 2292 pyliblo_0.16.2-1.dsc
 be089297ed7dd820781e1a6d54f4a313dbc25904 199126 pyliblo_0.16.2.orig.tar.gz
 e8fcdbc1fd3b9403730faa25b60d23e7b6d995e2 5936 pyliblo_0.16.2-1.debian.tar.xz
 50a9ada2545796b1c2e4ad42173342629015b6dc 7772 pyliblo_0.16.2-1_source.buildinfo
Checksums-Sha256:
 cf24f55a014c5ffd4add57dd156e100a71813f5c31a6c24d4343b4f97d20f6f6 2292 pyliblo_0.16.2-1.dsc
 60db8e7c77fd5dd2cd2fb9e19196804ba1117cc32714892f9ea5b5ddfd30c090 199126 pyliblo_0.16.2.orig.tar.gz
 32950e58585e45f30c12330d821bc5bf1a80863314d5ebcdc00dfb5a7ecfe0b8 5936 pyliblo_0.16.2-1.debian.tar.xz
 0b4ffacba9179ee4f9b712f46d0153d1bd082a2075e0d14f9b60842b05a27a5e 7772 pyliblo_0.16.2-1_source.buildinfo
Files:
 782cd443669a2fe3516b213fdf6087de 2292 devel optional pyliblo_0.16.2-1.dsc
 c0d391c013b1d1d3cb3a65a02872bddc 199126 devel optional pyliblo_0.16.2.orig.tar.gz
 549eb0a3afbe7bd0b08de0fc8698a979 5936 devel optional pyliblo_0.16.2-1.debian.tar.xz
 6fe014c26ed338683382996aa27f1f12 7772 devel optional pyliblo_0.16.2-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJDBAEBCgAtFiEEPLfDAq+1fmGoxhfdY06lXZArmDYFAmd0HKkPHHNuZEBkZWJp
YW4ub3JnAAoJEGNOpV2QK5g28CMQAL3T7UBOr18c3OaW+LkDRL44WFvY1LTqGj9k
XS1lXJtKUO0U6CzbHtlNlVggTrDDFoA4AxfWGnGS+KlyVVVqlCaiZ3QlhGxDnWr6
C6Du/9JiHz4yQfmzwWn+v85756NGgAz2LlSuYQjH67GUK+j3ic6qkSEojhR5RSo5
VbfOYNCmgMyoX75UxBRbdMjRdamP7OdsaLVkoMj/d+VdkNn95UtrW3kxJ9P6szs7
beVsYKQxRVcprjK2OMuoKfRVPP8P8SRX0syk1ZEZDMORXvP6p/V1bhOxUWBzwYYi
HXhf0ykpyF0OQtpZ8cfXDE8rqlgyBJ4F/dRP+8reKLKq/grQGZIwpbDa+sCQWbtr
wqV5pWyYFC1glEID8lYY2XqA2ASbj1POSexkcdPv02A/UAhL0UFcCzEH8m32vjuA
IfdSF48eMYl99COLz0XqnTopDYxcXPs56d7YkpSXBv16J+9Nw0DSEK2O5YBP/87h
R3b0QOBHZbWvvMF0bTFfggoYF8TsrJ4EV3RaqwTJR3R0HratYqQc08iugr+kv0Rp
miSfYD7kSThuQoF9F4gCbhUdx2LCL/uWZaV6Fc5BluSZk7cTITzDcwjAg4Qm9s3c
vc30FjX40RBiVdN2PUcqpr97c0cMU8PK6t4wzSP528lIxF30xomT/nVpBu2x7Q/2
i32Qe+4f
=ljo6
-----END PGP SIGNATURE-----

Attachment: pgpvTwawv5vIY.pgp
Description: PGP signature


--- End Message ---
Reply to: