[Aptitude-devel] Bug#1012895: aptitude: ftbfs with GCC-12
Package: src:aptitude Version: 0.8.13-4 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/aptitude_0.8.13-4_unstable_gcc12.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. [...] /usr/include/cppunit/tools/StringHelper.h:25:9: note: mismatched types ‘const _CharT*’ and ‘std::vector >’ 25 | ost << x; | ^~~~ /usr/include/c++/12/bits/ostream.tcc:302:5: note: candidate: ‘template std::basic_ostream<_Ch, _Tr>& std::operator<<(basic_ostream<_Ch, _Tr>&, const char*)’ 302 | operator<<(basic_ostream<_CharT, _Traits>& __out, const char* __s) | ^~~~ /usr/include/c++/12/bits/ostream.tcc:302:5: note: template argument deduction/substitution failed: /usr/include/cppunit/tools/StringHelper.h:25:9: note: cannot convert ‘x’ (type ‘const std::vector >’) to type ‘const char*’ 25 | ost << x; | ^~~~ /usr/include/c++/12/ostream:615:5: note: candidate: ‘template std::basic_ostream& std::operator<<(basic_ostream&, const char*)’ 615 | operator<<(basic_ostream& __out, const char* __s) | ^~~~ /usr/include/c++/12/ostream:615:5: note: template argument deduction/substitution failed: /usr/include/cppunit/tools/StringHelper.h:25:9: note: cannot convert ‘x’ (type ‘const std::vector >’) to type ‘const char*’ 25 | ost << x; | ^~~~ /usr/include/c++/12/ostream:628:5: note: candidate: ‘template std::basic_ostream& std::operator<<(basic_ostream&, const signed char*)’ 628 | operator<<(basic_ostream& __out, const signed char* __s) | ^~~~ /usr/include/c++/12/ostream:628:5: note: template argument deduction/substitution failed: /usr/include/cppunit/tools/StringHelper.h:25:9: note: cannot convert ‘x’ (type ‘const std::vector >’) to type ‘const signed char*’ 25 | ost << x; | ^~~~ /usr/include/c++/12/ostream:633:5: note: candidate: ‘template std::basic_ostream& std::operator<<(basic_ostream&, const unsigned char*)’ 633 | operator<<(basic_ostream& __out, const unsigned char* __s) | ^~~~ /usr/include/c++/12/ostream:633:5: note: template argument deduction/substitution failed: /usr/include/cppunit/tools/StringHelper.h:25:9: note: cannot convert ‘x’ (type ‘const std::vector >’) to type ‘const unsigned char*’ 25 | ost << x; | ^~~~ /usr/include/c++/12/ostream:754:5: note: candidate: ‘template _Ostream&& std::operator<<(_Ostream&&, const _Tp&)’ 754 | operator<<(_Ostream&& __os, const _Tp& __x) | ^~~~ /usr/include/c++/12/ostream:754:5: note: template argument deduction/substitution failed: /usr/include/c++/12/ostream: In substitution of ‘template _Ostream&& std::operator<<(_Ostream&&, const _Tp&) [with _Ostream = std::__cxx11::basic_ostringstream&; _Tp = std::vector >]’: /usr/include/cppunit/tools/StringHelper.h:25:9: required from ‘typename std::enable_if<(! std::is_enum<_Tp>::value), std::__cxx11::basic_string >::type CppUnit::StringHelper::toString(const T&) [with T = std::vector >; typename std::enable_if<(! std::is_enum<_Tp>::value), std::__cxx11::basic_string >::type = std::__cxx11::basic_string]’ /usr/include/cppunit/TestAssert.h:74:50: required from ‘static std::string CppUnit::assertion_traits::toString(const T&) [with T = std::vector >; std::string = std::__cxx11::basic_string]’ /usr/include/cppunit/TestAssert.h:168:58: required from ‘void CppUnit::assertEquals(const T&, const T&, SourceLine, const std::string&) [with T = std::vector >; std::string = std::__cxx11::basic_string]’ ../../tests/test_parsers.cc:140:3: required from ‘void verify_success(const std::st
[Aptitude-devel] Bug#1012895: Bug#1012895: aptitude: ftbfs with GCC-12
Control: tag -1 + moreinfo Hi Matthias, Matthias Klose wrote: > The package fails to build in a test rebuild on at least amd64 with > gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. Thanks for the heads up! > To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, I think you mean 12 instead of 11. > 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. Is the same copy & paste error from the GCC 11 bug reports back then as above or is this actually correct for GCC 12? Please clarify. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE ___ Aptitude-devel mailing list Aptitude-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Processed: Re: Bug#1012895: aptitude: ftbfs with GCC-12
Processing control commands: > tag -1 + moreinfo Bug #1012895 [src:aptitude] aptitude: ftbfs with GCC-12 Added tag(s) moreinfo. -- 1012895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Aptitude-devel mailing list Aptitude-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#1012895: Bug#1012895: aptitude: ftbfs with GCC-12
On 16.06.22 15:05, Axel Beckert wrote: Control: tag -1 + moreinfo Hi Matthias, Matthias Klose wrote: The package fails to build in a test rebuild on at least amd64 with gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. Thanks for the heads up! To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, I think you mean 12 instead of 11. yes, sorry about that. ___ Aptitude-devel mailing list Aptitude-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#1013075: aptitude: "aptitude why" outputs a chain with a package that is not installed
Package: aptitude Version: 0.8.13-4 Severity: normal zira:~> aptitude why gobject-introspection i libglib2.0-dev Suggests libgirepository1.0-dev (>= 1.62) p libgirepository1.0-dev Depends gobject-introspection (= 1.72.0-1+b1) while libgirepository1.0-dev isn't installed. So this doesn't give an explanation of why gobject-introspection is automatically installed. FYI, this is after Start-Date: 2022-06-16 14:53:32 Commandline: apt install dh-sequence-gir gtk-doc-tools libgirepository1.0-dev libnss3-dev libglib2.0-doc libcairo2-doc Install: libglib2.0-doc:amd64 (2.72.2-2), libnspr4-dev:amd64 (2:4.34-1, automatic), libnss3-dev:amd64 (2:3.79-1), python3-mako:amd64 (1.1.3+ds1-3, automatic), gobject-introspection:amd64 (1.72.0-1+b1), docbook:amd64 (4.5-10, automatic), python3-markdown:amd64 (3.3.7-1, automatic), gtk-doc-tools:amd64 (1.33.2-1), libcairo2-doc:amd64 (1.16.0-5), libgirepository1.0-dev:amd64 (1.72.0-1+b1), docbook-to-man:amd64 (1:2.0.0-45, automatic) End-Date: 2022-06-16 14:53:36 Start-Date: 2022-06-16 15:01:07 Commandline: apt remove --purge dh-sequence-gir gtk-doc-tools libgirepository1.0-dev libnss3-dev libglib2.0-doc libcairo2-doc docbook-to-man libnspr4-dev Purge: libglib2.0-doc:amd64 (2.72.2-2), libnspr4-dev:amd64 (2:4.34-1), libnss3-dev:amd64 (2:3.79-1), gtk-doc-tools:amd64 (1.33.2-1), libcairo2-doc:amd64 (1.16.0-5), libgirepository1.0-dev:amd64 (1.72.0-1+b1), docbook-to-man:amd64 (1:2.0.0-45) End-Date: 2022-06-16 15:01:09 -- Package-specific info: Terminal: xterm-256color $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.8.13 Compiler: g++ 11.3.0 Compiled against: apt version 6.0.0 NCurses version 6.3 libsigc++ version: 2.10.4 Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 6.3.20220423 cwidget version: 0.5.18 Apt version: 6.0.0 aptitude linkage: linux-vdso.so.1 (0x7ffe39dfe000) libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 (0x7faba6b3b000) libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 (0x7faba6946000) libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 (0x7faba690b000) libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 (0x7faba68d9000) libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x7faba68d) libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 (0x7faba67c8000) libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x7faba666c000) libboost_iostreams.so.1.74.0 => /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7faba6653000) libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 (0x7faba643) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7faba640f000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7faba61f4000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7faba60b) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7faba608e000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7faba5eb5000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7faba5eaf000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7faba5e95000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7faba5e78000) libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x7faba5e65000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7faba5e3b000) liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x7faba5e18000) libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 (0x7faba5d5f000) libudev.so.1 => /usr/lib/x86_64-linux-gnu/libudev.so.1 (0x7faba5d35000) libsystemd.so.0 => /usr/lib/x86_64-linux-gnu/libsystemd.so.0 (0x7faba5c62000) libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 (0x7faba5b1b000) libxxhash.so.0 => /usr/lib/x86_64-linux-gnu/libxxhash.so.0 (0x7faba5b04000) /lib64/ld-linux-x86-64.so.2 (0x7faba6f79000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7faba5afa000) libuuid.so.1 => /usr/lib/x86_64-linux-gnu/libuuid.so.1 (0x7faba5af1000) libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7faba5ae6000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x7faba5abb000) -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=POSIX, LC_CTYPE=
[Aptitude-devel] Bug#1012895: Bug#1012895: Bug#1012895: aptitude: ftbfs with GCC-12
Hi Matthias, Matthias Klose wrote: > > > To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, > > > > I think you mean 12 instead of 11. > > yes, sorry about that. No problem. That was the obvious one. But what about my second and more important question? Axel Beckert wrote: > > 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. > > Is the same copy & paste error from the GCC 11 bug reports back then > as above or is this actually correct for GCC 12? Please clarify. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE ___ Aptitude-devel mailing list Aptitude-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#1012895: Bug#1012895: Bug#1012895: aptitude: ftbfs with GCC-12
On 16.06.22 15:17, Axel Beckert wrote: Hi Matthias, Matthias Klose wrote: To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, I think you mean 12 instead of 11. yes, sorry about that. No problem. That was the obvious one. But what about my second and more important question? Axel Beckert wrote: 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. Is the same copy & paste error from the GCC 11 bug reports back then as above or is this actually correct for GCC 12? Please clarify. yes, the default C++ standard didn't change for GCC 12. ___ Aptitude-devel mailing list Aptitude-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#1012895: Bug#1012895: Bug#1012895: aptitude: ftbfs with GCC-12
Control: tag -1 - moreinfo Hi Matthias, Matthias Klose wrote: > > > > 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. > > > > > > Is the same copy & paste error from the GCC 11 bug reports back then > > > as above or is this actually correct for GCC 12? Please clarify. > > yes, the default C++ standard didn't change for GCC 12. Thanks! Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE ___ Aptitude-devel mailing list Aptitude-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Processed: Re: Bug#1012895: Bug#1012895: aptitude: ftbfs with GCC-12
Processing control commands: > tag -1 - moreinfo Bug #1012895 [src:aptitude] aptitude: ftbfs with GCC-12 Removed tag(s) moreinfo. -- 1012895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Aptitude-devel mailing list Aptitude-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel
