Your message dated Tue, 28 Jun 2022 19:50:28 +0000
with message-id <e1o6hec-0008ax...@fasolo.debian.org>
and subject line Bug#984406: fixed in zookeeper 3.8.0-1
has caused the Debian Bug report #984406,
regarding zookeeper: 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.)


-- 
984406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:zookeeper
Version: 3.4.13-6
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/zookeeper_3.4.13-6_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.

[...]
ZkAdaptor.h:187:54: error: ISO C++17 does not allow dynamic exception 
specifications
  187 |             ZooKeeperAdapter(ZooKeeperConfig config) 
throw(ZooKeeperException);
      |                                                      ^~~~~
ZkAdaptor.h:206:30: error: ISO C++17 does not allow dynamic exception 
specifications
  206 |             void reconnect() throw(ZooKeeperException);
      |                              ^~~~~
ZkAdaptor.h:229:50: error: ISO C++17 does not allow dynamic exception 
specifications
  229 |                     bool createAncestors = true) 
throw(ZooKeeperException);
      |                                                  ^~~~~
ZkAdaptor.h:246:39: error: ISO C++17 does not allow dynamic exception 
specifications
  246 |                     int version = -1) throw(ZooKeeperException);
      |                                       ^~~~~
ZkAdaptor.h:255:65: error: ISO C++17 does not allow dynamic exception 
specifications
  255 |             vector<string> getNodeChildren( const string &path) 
throw(ZooKeeperException);
      |                                                                 ^~~~~
ZkAdaptor.h:264:49: error: ISO C++17 does not allow dynamic exception 
specifications
  264 |             bool nodeExists(const string &path) 
throw(ZooKeeperException);
      |                                                 ^~~~~
ZkAdaptor.h:274:52: error: ISO C++17 does not allow dynamic exception 
specifications
  274 |             string getNodeData(const string &path) 
throw(ZooKeeperException);
      |                                                    ^~~~~
ZkAdaptor.h:289:39: error: ISO C++17 does not allow dynamic exception 
specifications
  289 |                     int version = -1) throw(ZooKeeperException);
      |                                       ^~~~~
ZkAdaptor.h:299:58: error: ISO C++17 does not allow dynamic exception 
specifications
  299 |             static void validatePath(const string &path) 
throw(ZooKeeperException);
      |                                                          ^~~~~
ZkAdaptor.h:310:37: error: ISO C++17 does not allow dynamic exception 
specifications
  310 |             void verifyConnection() throw(ZooKeeperException);
      |                                     ^~~~~
ZkAdaptor.cc:92:64: error: ISO C++17 does not allow dynamic exception 
specifications
   92 |     ZooKeeperAdapter::ZooKeeperAdapter(ZooKeeperConfig config) 
throw(ZooKeeperException) :
      |                                                                ^~~~~
ZkAdaptor.cc:130:61: error: ISO C++17 does not allow dynamic exception 
specifications
  130 |     void ZooKeeperAdapter::validatePath(const string &path) 
throw(ZooKeeperException)
      |                                                             ^~~~~
ZkAdaptor.cc:170:40: error: ISO C++17 does not allow dynamic exception 
specifications
  170 |     void ZooKeeperAdapter::reconnect() throw(ZooKeeperException)
      |                                        ^~~~~
ZkAdaptor.cc:238:47: error: ISO C++17 does not allow dynamic exception 
specifications
  238 |     void ZooKeeperAdapter::verifyConnection() throw(ZooKeeperException)
      |                                               ^~~~~
ZkAdaptor.cc:265:35: error: ISO C++17 does not allow dynamic exception 
specifications
  265 |             bool createAncestors) throw(ZooKeeperException)
      |                                   ^~~~~
ZkAdaptor.cc:334:26: error: ISO C++17 does not allow dynamic exception 
specifications
  334 |             int version) throw(ZooKeeperException)
      |                          ^~~~~
ZkAdaptor.cc:383:77: error: ISO C++17 does not allow dynamic exception 
specifications
  383 |     vector< string > ZooKeeperAdapter::getNodeChildren (const string 
&path) throw (ZooKeeperException)
      |                                                                         
    ^~~~~
ZkAdaptor.cc:426:59: error: ISO C++17 does not allow dynamic exception 
specifications
  426 |     bool ZooKeeperAdapter::nodeExists(const string &path) 
throw(ZooKeeperException)
      |                                                           ^~~~~
ZkAdaptor.cc:456:62: error: ISO C++17 does not allow dynamic exception 
specifications
  456 |     string ZooKeeperAdapter::getNodeData(const string &path) 
throw(ZooKeeperException)
      |                                                              ^~~~~
ZkAdaptor.cc:491:26: error: ISO C++17 does not allow dynamic exception 
specifications
  491 |             int version) throw(ZooKeeperException)
      |                          ^~~~~
make[4]: *** [Makefile:383: ZkAdaptor.o] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/src/contrib/zktreeutil/src'
make[3]: *** [Makefile:362: all-recursive] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/src/contrib/zktreeutil'
make[2]: *** [Makefile:303: all] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/src/contrib/zktreeutil'
make[1]: *** [debian/rules:38: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:20: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: zookeeper
Source-Version: 3.8.0-1
Done: Pierre Gruet <p...@debian.org>

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

Debian distribution maintenance software
pp.
Pierre Gruet <p...@debian.org> (supplier of updated zookeeper 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: Tue, 28 Jun 2022 18:02:04 +0200
Source: zookeeper
Architecture: source
Version: 3.8.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 
<pkg-java-maintain...@lists.alioth.debian.org>
Changed-By: Pierre Gruet <p...@debian.org>
Closes: 927673 949517 984406 990345 1001959 1012770
Changes:
 zookeeper (3.8.0-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version 3.8.0 (Closes: #927673):
     - Checking it is affected by no known security vulnerability
       (Closes: #990345)
     - Checking it does not use xml2-config anymore (Closes: #949517)
     - Checking the package does not FTBFS with gcc-11 (Closes: #984406)
   * Refreshing patches
   * Building with Maven, adapting B-D, refreshing d/rules and adapting install
     paths accordingly
   * Adapting install paths after switching to Maven
   * Updates in debian/control:
     - Depending on debhelper-compat 13
     - Removing X-Python3-Version field
     - Raising Standards version to 4.6.1 (no change)
     - Adding a Pre-Depends field in d/control for zookeeperd so that it
       pre-depends on init-system-helpers
     -  zookeeper needs to depend on default-jre, not only the headless version
   * Refreshing d/copyright
   * Updating / refreshing the packaging style:
     - New upstream signing keys
     - Rewriting d/watch, set to version 4, no repack
     - Removing debian/gbp.conf
     - Removing debian/orig-tar.sh, repacking is done via debian/copyright
     - Set upstream metadata fields: Bug-Database, Repository,
       Repository-Browse.
   * Providing patches related to the new Maven build:
     - Adding missing versions of some Maven plugins in the POM files
     - Skipping the unpackaged Timeout annotations in the tests
     - Using the ValueSource annotation with ints instead of booleans, which are
       not available in Debian-package junit5
     - Omitting the TempDir annotation in the tests, as it is not available yet
     - Correcting call to deprecated method in Bouncycastle
     -  Switching from test-jar type to tests classifier in the POM files
     - Omitting the dependency of the assembly POM on the
       zookeeper-prometheus-metrics jar, which cannot be built right now
     - Adding missing artifacts in the zookeeper-contrib-rest POM file
     - Skipping some classes because of unpackaged org.openjdk-jmh package
     - Building the Python3 artifacts without OpenSSL
     - Omitting test classes needing junit5 unpackaged classes or attempting to
       use the network
   * Correcting tiny spelling errors in the code
   * Reworking debian/rules:
     - Updating the overrides of dh_clean and dh_auto_clean
     - Stopping parsing changelog in d/rules
   * Providing an up-to-date d/libzookeeper-java.manifest file, updating
     dependencies of the binary package accordingly
   * Refreshing the doc-base files
   * Stopping providing zktreeutil, providing a NEWS file to explain this
   * Adding a NEWS entry about possible failure at startup and how to solve it
     (Closes: #1012770)
   * Adding a Lintian override for the embedded js in the javadoc
   * Adding a Lintian override for files with long lines
   * Adding missing patch headers
   * Hacking in the libtool file to prevent -rpath flags when building
   * Changing USER to NAME in d/zookeeper.postinst and d/zookeeper.postrm to be
     sure the script is doing the right thing (actually the shell uses USER for
     the logged in name)
   * Using --remove-home in d/zookeeper.postrm to ensure everything is properly
     deleted (Closes: #1001959)
Checksums-Sha1:
 fdc2e49bac0fd09e72eea2d0e5964d2db52dd344 3763 zookeeper_3.8.0-1.dsc
 c6556b6e4237f78955e3d8cd313d0ef04ed1b7e9 3485515 zookeeper_3.8.0.orig.tar.gz
 c2622953992c4495ac935662243a60c4e40d8828 488 zookeeper_3.8.0.orig.tar.gz.asc
 b2900d43f0ad3ea2bfa882ea7f59742abc25a16e 88676 zookeeper_3.8.0-1.debian.tar.xz
 282cb46c5aa0cec072a0846a489dbc95b0661513 23016 
zookeeper_3.8.0-1_amd64.buildinfo
Checksums-Sha256:
 4d6fd52c05097a30c427396aec78a4ffb44c4d4e20d4073cba4b8df02d213355 3763 
zookeeper_3.8.0-1.dsc
 b0c5684640bea2d8bd6610b47ff41be2aefd6c910ba48fcad5949bd2bf2fa1ac 3485515 
zookeeper_3.8.0.orig.tar.gz
 22bd6c0fe38b3184cb2b7d5039392f7a63a506915b27a58328f1b4f9731ebfc3 488 
zookeeper_3.8.0.orig.tar.gz.asc
 1539f248585654f13e46970940f3ff6a442f77d427d62ea2a6123bcb54cd4e4d 88676 
zookeeper_3.8.0-1.debian.tar.xz
 3100ede69e765b210c5d784506a4640359b71244feeb3745edc3b39d51c1aa91 23016 
zookeeper_3.8.0-1_amd64.buildinfo
Files:
 b401f5843a31789b118a1cd00bebe1f6 3763 java optional zookeeper_3.8.0-1.dsc
 dd50b329f3e17c03d2da8ed8497babb6 3485515 java optional 
zookeeper_3.8.0.orig.tar.gz
 0309b972507b7ef0f1851660618d090e 488 java optional 
zookeeper_3.8.0.orig.tar.gz.asc
 8a59fb47ca044aebf194aabcffda2964 88676 java optional 
zookeeper_3.8.0-1.debian.tar.xz
 ee50a3850b0e3806b5e07f4e4e5d4045 23016 java optional 
zookeeper_3.8.0-1_amd64.buildinfo

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

iQIzBAEBCgAdFiEEM8soQxPpC9J9y0UjYAMWptwndHYFAmK7V+oACgkQYAMWptwn
dHY/AA//UAapTaviN/9VnvYtC6Z22NTvKIEbC5dJ5R7BUBMVTlTLhCIRUyOe+sJh
ZCpqeo9551kqCln0m0ZIXE3Yde9QNKevLpv6Z12mES/i78eQaadMklrVo2P1o2G/
GUDFNrskJk2n3ixIeTL6qTaPJdZBvBkEemqnQA+KUQ7kVPxU/Aw1xXOZLb513LAl
aMVp01hAgR+DRH3aiz0FLUE2BdFqRJFshr0atWd3NblB/EE/swgbku0b2gYBOnTx
I6UoBT6ztjl6MqmD8UYrFBGfCo7yLnWFkOoQISL/HKajjgAzII2Z46DOKvEpHfJY
TIn1t2SzeUXr0qPDjAN9LY/ORPMiEe6BVA2p6uLfR0F4EnzW3mkrVM97ebR5CPcp
gpgedm6n/ffKwmVp1aVjhMvK82wDt1QCv7+w+f/R3+dFiPEjgm+fEEUSYwwZhWnL
E2Z/GMvKTFAaSZ76/TBLOoguHF80VuCbCJsSWm2J9CJyMtMYv8spIUzgqQmTZgqj
MvlWS//XlMkd55t4SOjoCcjLK/LcmqLcXYjr68XA2Gb6PvnvaWddcylyOEQ8gCdH
EQm6jJz7LLhohBUB8JhcLLBCLt2RQ1ItQdIkMsQoBscRTwI1ufiDFxY2jzB7t5T4
9oiZyeZRqTmZbXRe0MrEpZqm9kXONnREfYsQ6j4sLhXxh3hm0LM=
=o+63
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to