Your message dated Sat, 13 Aug 2022 07:34:02 +0000
with message-id <e1omlek-003dei...@fasolo.debian.org>
and subject line Bug#1012974: fixed in libcrypto++ 8.7.0-1
has caused the Debian Bug report #1012974,
regarding libcrypto++: ftbfs with GCC-12
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.)


-- 
1012974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libcrypto++
Version: 8.6.0-3
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/libcrypto++_8.6.0-3_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.

[...]
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP256r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP320r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP192r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP256r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP320r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP192r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP256r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP320r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP192r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP256r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP320r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP192r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP256r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP320r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP192r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
passed    brainpoolP256r1 using RIPEMD-160
passed    signature key validation
passed    signature and verification
passed    checking invalid signature
make[1]: *** [debian/rules:54: override_dh_auto_test-arch] Bus error
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:72: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: libcrypto++
Source-Version: 8.7.0-1
Done: Laszlo Boszormenyi (GCS) <g...@debian.org>

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS) <g...@debian.org> (supplier of updated libcrypto++ 
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: Sat, 13 Aug 2022 07:22:58 +0200
Source: libcrypto++
Architecture: source
Version: 8.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) <g...@debian.org>
Changed-By: Laszlo Boszormenyi (GCS) <g...@debian.org>
Closes: 1012974
Changes:
 libcrypto++ (8.7.0-1) unstable; urgency=medium
 .
   * New upstream release (closes: #1012974).
   * Add -fno-devirtualize to CXXFLAGS for GCC 12 not to remove code member
     function needed for self-testing.
Checksums-Sha1:
 0eea394640576a0c25e4bfeef7fd1ea09440a6da 1999 libcrypto++_8.7.0-1.dsc
 a1b41b84cbb72f93165da71b13cd074da68e47c9 9139064 libcrypto++_8.7.0.orig.tar.gz
 cf3956ccb2a43e8522cfb98dc7a0105530a905e7 15564 
libcrypto++_8.7.0-1.debian.tar.xz
Checksums-Sha256:
 3dd4f79406d6b2913434e30daf63ad23660c2a893322badd68553c5f40056c23 1999 
libcrypto++_8.7.0-1.dsc
 8d6a4064b8e9f34cd3e838f5a12c40067ee7b95ee37d9173ec273cb0913e7ca2 9139064 
libcrypto++_8.7.0.orig.tar.gz
 ca4f340e1e16b249a80c141dcefa551211bce834eac256574ea2fcb21ee33e84 15564 
libcrypto++_8.7.0-1.debian.tar.xz
Files:
 c858280a1e5c72c3cc0e1b580995ab7e 1999 libs optional libcrypto++_8.7.0-1.dsc
 69b11e59094c10d437f295f11e51c16a 9139064 libs optional 
libcrypto++_8.7.0.orig.tar.gz
 e7c319f1d92ff162d03eb010e6ccf2b1 15564 libs optional 
libcrypto++_8.7.0-1.debian.tar.xz

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

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmL3TyYACgkQ3OMQ54ZM
yL/HUxAAoH4tv64sb+UYDZGwGnDZ1wwCfrY8VjvfIv2lbFtQgb7glL6kRRXjNFfB
+0Wc1ulSn+qfwK413NLpX2EMZUMH3wrRQ6jeNerr/0Nszw61Zj4Jp3P3vej5g0sj
HWMaZT+fhxQGUGDKBX8OAgkrNeir+ZWjgWfguyLxN1YO3xuWu+q/NJl889ZB3S+s
yoJOOr+ZsWwt3uG6ko+2HL2bYRU5PtSL9PE/iIKTNOY51ndYQsjs9POauWjyrQZF
GFZAZ/4HQu7q9Tdx4senUYoMQZmvH8DV8W6hRf879Jnd2YO9blZ3Ymsu/MWl939R
CbmclBmOTyFMXOqmF2TcSVlJvHHTnFgB+RTevfKcUsQk00SEWbddoUrf0t7odOZE
i+BHMqmExEq5Zp0SCiM51Dqf5I8Gw7EETztgY7a3YNJ/g+OhOZk6hBLB/qIfAkYv
4xYK2DdoTrSkTqRLyqI6CA9Z2QyoJ9etmJUOYN9Wjxcxeg6Zb833v97SLU+VYtB6
biqq46DGrmGROzSSyTk8cWbshO/nZOO3JjBGWjoiD7LmohCrpz91X951sVtTWqGL
7Md5kI1lQ71o+dujzr/vXpK+QzmIrHi3W4UthSYp74ggZdOLX9B9PFk22uvipe6/
EwjyFMIkNHrizaz0pYjxEThlrNbzpBG5GDm5qBjYevLD5QpRi8g=
=2yxX
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to