Your message dated Thu, 18 Nov 2021 14:34:16 +0000 with message-id <e1mnius-0003b7...@fasolo.debian.org> and subject line Bug#983996: fixed in blist 1.3.6-8 has caused the Debian Bug report #983996, regarding blist: ftbfs with GCC-11 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 ow...@bugs.debian.org immediately.) -- 983996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: src:blist Version: 1.3.6-7 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/blist_1.3.6-7_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] blist/_blist.c:2759:20: warning: ‘p’ may be used uninitialized [-Wmaybe-uninitialized] 2759 | return _ob(blist_get1(p, i - so_far)); | ^ blist/_blist.c:1061:19: note: in definition of macro ‘_ob’ 1061 | #define _ob(ret) (ret) | ^~~ blist/_blist.c: In function ‘py_blist_repr’: blist/_blist.c:2748:18: note: ‘p’ declared here 2748 | PyBList *p; | ^ In function ‘blist_get1’, inlined from ‘py_blist_repr’ at blist/_blist.c:6430:15, inlined from ‘py_blist_repr’ at blist/_blist.c:6368:1: blist/_blist.c:2759:20: warning: ‘p’ may be used uninitialized [-Wmaybe-uninitialized] 2759 | return _ob(blist_get1(p, i - so_far)); | ^ blist/_blist.c:1061:19: note: in definition of macro ‘_ob’ 1061 | #define _ob(ret) (ret) | ^~~ blist/_blist.c: In function ‘py_blist_repr’: blist/_blist.c:2748:18: note: ‘p’ declared here 2748 | PyBList *p; | ^ In function ‘blist_get1’, inlined from ‘blist_delitem_return’ at blist/_blist.c:2817:14, inlined from ‘py_blist_ass_subscript’ at blist/_blist.c:6022:48: blist/_blist.c:2759:20: warning: ‘p’ may be used uninitialized [-Wmaybe-uninitialized] 2759 | return _ob(blist_get1(p, i - so_far)); | ^ blist/_blist.c:1061:19: note: in definition of macro ‘_ob’ 1061 | #define _ob(ret) (ret) | ^~~ blist/_blist.c: In function ‘py_blist_ass_subscript’: blist/_blist.c:2748:18: note: ‘p’ declared here 2748 | PyBList *p; | ^ In function ‘blist_get1’, inlined from ‘py_blist_subscript’ at blist/_blist.c:6987:30: blist/_blist.c:2759:20: warning: ‘p’ may be used uninitialized [-Wmaybe-uninitialized] 2759 | return _ob(blist_get1(p, i - so_far)); | ^ blist/_blist.c:1061:19: note: in definition of macro ‘_ob’ 1061 | #define _ob(ret) (ret) | ^~~ blist/_blist.c: In function ‘py_blist_subscript’: blist/_blist.c:2748:18: note: ‘p’ declared here 2748 | PyBList *p; | ^ x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-z,relro -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.9/blist/_blist.o -o /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_blist/build/blist/_blist.cpython-39-x86_64-linux-gnu.so dh_auto_test -O--buildsystem=pybuild pybuild --test -i python{version} -p 3.9 I: pybuild base:232: python3.9 setup.py test running test WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox. running egg_info writing blist.egg-info/PKG-INFO writing dependency_links to blist.egg-info/dependency_links.txt writing top-level names to blist.egg-info/top_level.txt reading manifest file 'blist.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'blist.rst' writing manifest file 'blist.egg-info/SOURCES.txt' running build_ext copying /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_blist/build/blist/_blist.cpython-39-x86_64-linux-gnu.so -> blist test_LIFO (test_blist.BListTest) ... Segmentation fault E: pybuild pybuild:353: test: plugin distutils failed with: exit code=139: python3.9 setup.py test rm -fr -- /tmp/dh-xdg-rundir-B3ksYJOz dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13 make: *** [debian/rules:7: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---Source: blist Source-Version: 1.3.6-8 Done: Stefano Rivera <stefa...@debian.org> We believe that the bug you reported is fixed in the latest version of blist, 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 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera <stefa...@debian.org> (supplier of updated blist 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 ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Thu, 18 Nov 2021 09:51:39 -0400 Source: blist Architecture: source Version: 1.3.6-8 Distribution: unstable Urgency: medium Maintainer: Debian Python Team <team+pyt...@tracker.debian.org> Changed-By: Stefano Rivera <stefa...@debian.org> Closes: 983996 999365 Changes: blist (1.3.6-8) unstable; urgency=medium . [ Stefano Rivera ] * Team upload. * Bump Standards-Version to 4.6.0, no changes needed. * Bump watch file version to 4. * Update homepage. * Add upstream metadata. * Build with -O1 to workaround FTBFS with gcc-11, thanks Steve Langasek (Closes: #983996). * Patch: Python 3.10 support, thanks Steve Langasek (Closes: #999365). . [ Debian Janitor ] * Remove overrides for lintian tags that are no longer supported. Checksums-Sha1: e99dfa0affce72b104b4ba7087a3f075e267d4d3 1377 blist_1.3.6-8.dsc e417b467fba1c1be04d7ed55be715eaf23284604 7116 blist_1.3.6-8.debian.tar.xz f397dcb101a52d52270baebdecc03080dc52e17e 6004 blist_1.3.6-8_source.buildinfo Checksums-Sha256: 8423a9199408551054883bec3937f19c016e3cdf234f2f523e0f13dd6686a6bf 1377 blist_1.3.6-8.dsc bc6f1b2790266f17bc0715e5ffbad8c6f63695334dec45058fa7bd7a94a7c102 7116 blist_1.3.6-8.debian.tar.xz 454a3c8d83a6410a97fadab4377ff4fb190e018fa48af0dc22e96077851a2fd6 6004 blist_1.3.6-8_source.buildinfo Files: 6eb1e084a61b7d8f3b4f5061f54d7853 1377 python optional blist_1.3.6-8.dsc 2d627b46cae3602fa7ef4b3a10d051ae 7116 python optional blist_1.3.6-8.debian.tar.xz 6c02a7b229635955e76276dc18e9757f 6004 python optional blist_1.3.6-8_source.buildinfo -----BEGIN PGP SIGNATURE----- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYZZaihQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2FuBAP0QexNxCdF3+IF8RVx0e7w46UJFLgUj o4+Ssk0+Y2DYygD/TxJQVWoUXYVtuPuOKkE6ZlsvtjTAK+RHTB/YmF3y1go= =h+ph -----END PGP SIGNATURE-----
--- End Message ---
