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

Bug#1037765: marked as done (maildir-utils: ftbfs with GCC-13)



Your message dated Sun, 16 Jul 2023 17:09:36 +0000
with message-id <E1qL5FY-00BWui-BP@fasolo.debian.org>
and subject line Bug#1037765: fixed in maildir-utils 1.8.14-2
has caused the Debian Bug report #1037765,
regarding maildir-utils: ftbfs with GCC-13
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.)


-- 
1037765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037765
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:maildir-utils
Version: 1.8.14-1
Severity: normal
Tags: sid trixie
User: debian-gcc@lists.debian.org
Usertags: ftbfs-gcc-13

[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-13/g++-13, but succeeds to build with gcc-12/g++-12. 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/2023/05/22/logs/maildir-utils_1.8.14-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html

[...]
   67 |                                 throw Mu::Error{Error::Code::Command,
      |                                                        ^~~~
mu-command-parser.cc:67:56: error: no matching function for call to ‘Mu::Error::Error(<brace-enclosed initializer list>)’
../../lib/utils/mu-error.hh:93:9: note: candidate: ‘Mu::Error::Error(const Mu::Error&)’
   93 |         Error(const Error& rhs) = default;
      |         ^~~~~
../../lib/utils/mu-error.hh:93:9: note:   conversion of argument 1 would be ill-formed:
../../lib/utils/mu-error.hh:92:9: note: candidate: ‘Mu::Error::Error(Mu::Error&&)’
   92 |         Error(Error&& rhs)      = default;
      |         ^~~~~
../../lib/utils/mu-error.hh:92:9: note:   conversion of argument 1 would be ill-formed:
mu-command-parser.cc:67:48: error: expected primary-expression before ‘{’ token
   67 |                                 throw Mu::Error{Error::Code::Command,
      |                                                ^
mu-command-parser.cc:77:48: error: ‘Code’ is not a member of ‘Mu::Error’
   77 |                         throw Mu::Error{Error::Code::Command,
      |                                                ^~~~
mu-command-parser.cc:77:48: error: no matching function for call to ‘Mu::Error::Error(<brace-enclosed initializer list>)’
../../lib/utils/mu-error.hh:93:9: note: candidate: ‘Mu::Error::Error(const Mu::Error&)’
   93 |         Error(const Error& rhs) = default;
      |         ^~~~~
../../lib/utils/mu-error.hh:93:9: note:   conversion of argument 1 would be ill-formed:
../../lib/utils/mu-error.hh:92:9: note: candidate: ‘Mu::Error::Error(Mu::Error&&)’
   92 |         Error(Error&& rhs)      = default;
      |         ^~~~~
../../lib/utils/mu-error.hh:92:9: note:   conversion of argument 1 would be ill-formed:
mu-command-parser.cc:77:40: error: expected primary-expression before ‘{’ token
   77 |                         throw Mu::Error{Error::Code::Command,
      |                                        ^
mu-command-parser.cc:90:48: error: ‘Code’ is not a member of ‘Mu::Error’
   90 |                         throw Mu::Error{Error::Code::Command,
      |                                                ^~~~
mu-command-parser.cc:90:48: error: no matching function for call to ‘Mu::Error::Error(<brace-enclosed initializer list>)’
../../lib/utils/mu-error.hh:93:9: note: candidate: ‘Mu::Error::Error(const Mu::Error&)’
   93 |         Error(const Error& rhs) = default;
      |         ^~~~~
../../lib/utils/mu-error.hh:93:9: note:   conversion of argument 1 would be ill-formed:
../../lib/utils/mu-error.hh:92:9: note: candidate: ‘Mu::Error::Error(Mu::Error&&)’
   92 |         Error(Error&& rhs)      = default;
      |         ^~~~~
../../lib/utils/mu-error.hh:92:9: note:   conversion of argument 1 would be ill-formed:
mu-command-parser.cc:90:40: error: expected primary-expression before ‘{’ token
   90 |                         throw Mu::Error{Error::Code::Command,
      |                                        ^
mu-command-parser.cc: In function ‘std::vector<Mu::Sexp>::const_iterator find_param_node(const Mu::Command::Parameters&, const std::string&)’:
mu-command-parser.cc:104:36: error: ‘Code’ is not a member of ‘Mu::Error’
  104 |                 throw Error(Error::Code::InvalidArgument, "params must not be empty");
      |                                    ^~~~
mu-command-parser.cc:107:36: error: ‘Code’ is not a member of ‘Mu::Error’
  107 |                 throw Error(Error::Code::InvalidArgument,
      |                                    ^~~~
mu-command-parser.cc: In function ‘Mu::Error wrong_type(Mu::Sexp::Type, Mu::Sexp::Type)’:
mu-command-parser.cc:123:29: error: ‘Code’ is not a member of ‘Mu::Error’
  123 |         return Error(Error::Code::InvalidArgument,
      |                             ^~~~
libtool: compile:  g++ -std=gnu++17 -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -Wall -Wextra -Wundef -Wwrite-strings -Wpointer-arith -Wmissing-declarations -Wredundant-decls -Wno-unused-parameter -Wno-missing-field-initializers -Wformat=2 -Wcast-align -Wformat-nonliteral -Wformat-security -Wsign-compare -Wstrict-aliasing -Wshadow -Winline -Wpacked -Wmissing-format-attribute -Wmissing-noreturn -Winit-self -Wmissing-include-dirs -Wunused-but-set-variable -Warray-bounds -Wreturn-type -Wno-overloaded-virtual -Wswitch-enum -Wswitch-default -Wno-error=unused-parameter -Wno-error=missing-field-initializers -Wno-error=overloaded-virtual -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/libmount -I/usr/include/blkid -I../../lib -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-inline -c mu-logger.cc -o mu-logger.o >/dev/null 2>&1
make[4]: *** [Makefile:582: mu-command-parser.lo] Error 1
make[4]: *** Waiting for unfinished jobs....
libtool: compile:  g++ -std=gnu++17 -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -Wall -Wextra -Wundef -Wwrite-strings -Wpointer-arith -Wmissing-declarations -Wredundant-decls -Wno-unused-parameter -Wno-missing-field-initializers -Wformat=2 -Wcast-align -Wformat-nonliteral -Wformat-security -Wsign-compare -Wstrict-aliasing -Wshadow -Winline -Wpacked -Wmissing-format-attribute -Wmissing-noreturn -Winit-self -Wmissing-include-dirs -Wunused-but-set-variable -Warray-bounds -Wreturn-type -Wno-overloaded-virtual -Wswitch-enum -Wswitch-default -Wno-error=unused-parameter -Wno-error=missing-field-initializers -Wno-error=overloaded-virtual -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/libmount -I/usr/include/blkid -I../../lib -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-inline -c mu-sexp.cc -o mu-sexp.o >/dev/null 2>&1
libtool: compile:  g++ -std=gnu++17 -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -Wall -Wextra -Wundef -Wwrite-strings -Wpointer-arith -Wmissing-declarations -Wredundant-decls -Wno-unused-parameter -Wno-missing-field-initializers -Wformat=2 -Wcast-align -Wformat-nonliteral -Wformat-security -Wsign-compare -Wstrict-aliasing -Wshadow -Winline -Wpacked -Wmissing-format-attribute -Wmissing-noreturn -Winit-self -Wmissing-include-dirs -Wunused-but-set-variable -Warray-bounds -Wreturn-type -Wno-overloaded-virtual -Wswitch-enum -Wswitch-default -Wno-error=unused-parameter -Wno-error=missing-field-initializers -Wno-error=overloaded-virtual -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/libmount -I/usr/include/blkid -I../../lib -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-inline -c mu-utils.cc -o mu-utils.o >/dev/null 2>&1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/lib/utils'
make[3]: *** [Makefile:698: all-recursive] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/lib'
make[2]: *** [Makefile:578: all-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [Makefile:488: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:9: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: maildir-utils
Source-Version: 1.8.14-2
Done: David Bremner <bremner@debian.org>

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

Debian distribution maintenance software
pp.
David Bremner <bremner@debian.org> (supplier of updated maildir-utils 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: SHA256

Format: 1.8
Date: Sun, 16 Jul 2023 13:32:26 -0300
Source: maildir-utils
Architecture: source
Version: 1.8.14-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team <debian-emacsen@lists.debian.org>
Changed-By: David Bremner <bremner@debian.org>
Closes: 1037765
Changes:
 maildir-utils (1.8.14-2) unstable; urgency=medium
 .
   * Team upload
   * Bug fix: "ftbfs with GCC-13", thanks to Matthias Klose (Closes:
     #1037765). Thanks to Jeremy Sowden for the fix.
   * Install missing info files (also thanks to Jeremy Sowden)
Checksums-Sha1:
 2bf0db825304384fde094253d81bdd52b92adaaa 2267 maildir-utils_1.8.14-2.dsc
 6f002e25ad4374b03da7df9a2abe38089e74eb06 11212 maildir-utils_1.8.14-2.debian.tar.xz
Checksums-Sha256:
 1f272312f30665796baa47938eaae509fc933e21cb842849b4df8506b450702a 2267 maildir-utils_1.8.14-2.dsc
 378464b08195be2fb92d8b9f6fc02c1ff17d39c736d445aeb4443f2256d4a997 11212 maildir-utils_1.8.14-2.debian.tar.xz
Files:
 924001f47c53e1dae4448204d013a75e 2267 mail optional maildir-utils_1.8.14-2.dsc
 eeb466643fb76dc2e2b4a7780bc05764 11212 mail optional maildir-utils_1.8.14-2.debian.tar.xz

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

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmS0Hv8ACgkQA0U5G1Wq
FSFt9xAAqi/rtxUqCQxqTFyHzm/E2ffa7Zbb32nmFsvq8M014xFk6QXjx26aQWq2
PxPh06supoTofHk6Q0M7WhWlZ9gooFwGgUcAWPuoyIDwV0GOYSqQIAvJNLJCTm3h
uIVi2CsnYwSj6f9vSKFxfaTu1SpNl2XHk71OAuLOKUohrB8BX5+rzhtsCf8qxoFB
iyqQFNuGuYaEiiFh+W83pGOgJYV34DMWDBJ1pAoV0DhBeFbRhwZPG1GqNQyu69gH
5tp66tBng1Ht8CEnPK9lnAczpmdRPVdllvvZ6Xw2YY9orRi7Vftdx0QtOPfHO+T2
Av+6MsbtO94hTeOisedjXHuQZQo5qyzCtNJv6/n3vr7U/e+J+x9UMl4SqodIr6OL
EhkDu6entWzT6c/LQaVkLBF0x07J20eOOMZliRUna921FzpK3dlAZn34Nzg42hHM
pEljCIfO6kfdwLMqr16dK5Bu9MMIgpuo9a4BOgWN8bfPNx/9ERGVsLFd+v7cXd7r
CoZ+1inBy8UOFQfnyH1apcRgzQeyELHGXXhWA1S25nCV2ShzcskVQ0O0VBtYsJhE
mTXYy8piUa9QoFyvgJuFxnuCnCPU8MEIFhhndve1ON8S09kVy6vB1nStHlh8mt0w
PmUBEvpb3dLZn+3Hz+7YQELQOfnQNVrJoR++AIfDn5ZFDe6nzv4=
=yo5a
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: