Your message dated Sun, 21 Aug 2022 13:49:23 +0000
with message-id <[email protected]>
and subject line Bug#1013072: fixed in yade 2022.01a-10
has caused the Debian Bug report #1013072,
regarding yade: 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 [email protected]
immediately.)


-- 
1013072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013072
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:yade
Version: 2022.01a-9
Severity: normal
Tags: sid bookworm
User: [email protected]
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/yade_2022.01a-9_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.

[...]
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp: In static member 
function ‘static std::string AabbVisitor<Box>::__str__(const 
boost::python::api::object&) [with Box = Eigen::AlignedBox<double, 2>]’:
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp:975:39: note: unnamed 
temporary defined here
  975 |                 const Box&         self = py::extract<Box>(obj)();
      |                                       ^~~~~~~~~~~~~~~~~
In member function ‘const Eigen::AlignedBox<Scalar, Dim>::VectorType& 
Eigen::AlignedBox<Scalar, Dim>::max() const [with _Scalar = double; int 
_AmbientDim = 3]’,
    inlined from ‘static std::string AabbVisitor<Box>::__str__(const 
boost::python::api::object&) [with Box = Eigen::AlignedBox<double, 3>]’ at 
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp:980:78:
/usr/include/eigen3/unsupported/Eigen/../../Eigen/src/Geometry/AlignedBox.h:146:51:
 error: dangling pointer to an unnamed temporary may be used 
[-Werror=dangling-pointer=]
  146 |   EIGEN_DEVICE_FUNC inline const VectorType& (max)() const { return 
m_max; }
      |                                                   ^~~~~
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp: In static member 
function ‘static std::string AabbVisitor<Box>::__str__(const 
boost::python::api::object&) [with Box = Eigen::AlignedBox<double, 3>]’:
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp:975:39: note: unnamed 
temporary defined here
  975 |                 const Box&         self = py::extract<Box>(obj)();
      |                                       ^~~~~~~~~~~~~~~~~
In member function ‘const Eigen::AlignedBox<Scalar, Dim>::VectorType& 
Eigen::AlignedBox<Scalar, Dim>::min() const [with _Scalar = double; int 
_AmbientDim = 3]’,
    inlined from ‘static std::string AabbVisitor<Box>::__str__(const 
boost::python::api::object&) [with Box = Eigen::AlignedBox<double, 3>]’ at 
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp:978:78:
/usr/include/eigen3/unsupported/Eigen/../../Eigen/src/Geometry/AlignedBox.h:142:51:
 error: dangling pointer to an unnamed temporary may be used 
[-Werror=dangling-pointer=]
  142 |   EIGEN_DEVICE_FUNC inline const VectorType& (min)() const { return 
m_min; }
      |                                                   ^~~~~
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp: In static member 
function ‘static std::string AabbVisitor<Box>::__str__(const 
boost::python::api::object&) [with Box = Eigen::AlignedBox<double, 3>]’:
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp:975:39: note: unnamed 
temporary defined here
  975 |                 const Box&         self = py::extract<Box>(obj)();
      |                                       ^~~~~~~~~~~~~~~~~
In member function ‘const Eigen::AlignedBox<Scalar, Dim>::VectorType& 
Eigen::AlignedBox<Scalar, Dim>::max() const [with _Scalar = 
boost::multiprecision::number<boost::multiprecision::backends::float128_backend,
 boost::multiprecision::et_off>; int _AmbientDim = 3]’,
    inlined from ‘static std::string AabbVisitor<Box>::__str__(const 
boost::python::api::object&) [with Box = 
Eigen::AlignedBox<boost::multiprecision::number<boost::multiprecision::backends::float128_backend,
 boost::multiprecision::et_off>, 3>]’ at 
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp:980:78:
/usr/include/eigen3/unsupported/Eigen/../../Eigen/src/Geometry/AlignedBox.h:146:51:
 error: dangling pointer to an unnamed temporary may be used 
[-Werror=dangling-pointer=]
  146 |   EIGEN_DEVICE_FUNC inline const VectorType& (max)() const { return 
m_max; }
      |                                                   ^~~~~
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp: In static member 
function ‘static std::string AabbVisitor<Box>::__str__(const 
boost::python::api::object&) [with Box = 
Eigen::AlignedBox<boost::multiprecision::number<boost::multiprecision::backends::float128_backend,
 boost::multiprecision::et_off>, 3>]’:
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp:975:39: note: unnamed 
temporary defined here
  975 |                 const Box&         self = py::extract<Box>(obj)();
      |                                       ^~~~~~~~~~~~~~~~~
In member function ‘const Eigen::AlignedBox<Scalar, Dim>::VectorType& 
Eigen::AlignedBox<Scalar, Dim>::min() const [with _Scalar = 
boost::multiprecision::number<boost::multiprecision::backends::float128_backend,
 boost::multiprecision::et_off>; int _AmbientDim = 3]’,
    inlined from ‘static std::string AabbVisitor<Box>::__str__(const 
boost::python::api::object&) [with Box = 
Eigen::AlignedBox<boost::multiprecision::number<boost::multiprecision::backends::float128_backend,
 boost::multiprecision::et_off>, 3>]’ at 
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp:978:78:
/usr/include/eigen3/unsupported/Eigen/../../Eigen/src/Geometry/AlignedBox.h:142:51:
 error: dangling pointer to an unnamed temporary may be used 
[-Werror=dangling-pointer=]
  142 |   EIGEN_DEVICE_FUNC inline const VectorType& (min)() const { return 
m_min; }
      |                                                   ^~~~~
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp: In static member 
function ‘static std::string AabbVisitor<Box>::__str__(const 
boost::python::api::object&) [with Box = 
Eigen::AlignedBox<boost::multiprecision::number<boost::multiprecision::backends::float128_backend,
 boost::multiprecision::et_off>, 3>]’:
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp:975:39: note: unnamed 
temporary defined here
  975 |                 const Box&         self = py::extract<Box>(obj)();
      |                                       ^~~~~~~~~~~~~~~~~
In member function ‘const Eigen::AlignedBox<Scalar, Dim>::VectorType& 
Eigen::AlignedBox<Scalar, Dim>::max() const [with _Scalar = 
boost::multiprecision::number<boost::multiprecision::backends::float128_backend,
 boost::multiprecision::et_off>; int _AmbientDim = 2]’,
    inlined from ‘static std::string AabbVisitor<Box>::__str__(const 
boost::python::api::object&) [with Box = 
Eigen::AlignedBox<boost::multiprecision::number<boost::multiprecision::backends::float128_backend,
 boost::multiprecision::et_off>, 2>]’ at 
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp:980:78:
/usr/include/eigen3/unsupported/Eigen/../../Eigen/src/Geometry/AlignedBox.h:146:51:
 error: dangling pointer to an unnamed temporary may be used 
[-Werror=dangling-pointer=]
  146 |   EIGEN_DEVICE_FUNC inline const VectorType& (max)() const { return 
m_max; }
      |                                                   ^~~~~
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp: In static member 
function ‘static std::string AabbVisitor<Box>::__str__(const 
boost::python::api::object&) [with Box = 
Eigen::AlignedBox<boost::multiprecision::number<boost::multiprecision::backends::float128_backend,
 boost::multiprecision::et_off>, 2>]’:
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp:975:39: note: unnamed 
temporary defined here
  975 |                 const Box&         self = py::extract<Box>(obj)();
      |                                       ^~~~~~~~~~~~~~~~~
In member function ‘const Eigen::AlignedBox<Scalar, Dim>::VectorType& 
Eigen::AlignedBox<Scalar, Dim>::min() const [with _Scalar = 
boost::multiprecision::number<boost::multiprecision::backends::float128_backend,
 boost::multiprecision::et_off>; int _AmbientDim = 2]’,
    inlined from ‘static std::string AabbVisitor<Box>::__str__(const 
boost::python::api::object&) [with Box = 
Eigen::AlignedBox<boost::multiprecision::number<boost::multiprecision::backends::float128_backend,
 boost::multiprecision::et_off>, 2>]’ at 
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp:978:78:
/usr/include/eigen3/unsupported/Eigen/../../Eigen/src/Geometry/AlignedBox.h:142:51:
 error: dangling pointer to an unnamed temporary may be used 
[-Werror=dangling-pointer=]
  142 |   EIGEN_DEVICE_FUNC inline const VectorType& (min)() const { return 
m_min; }
      |                                                   ^~~~~
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp: In static member 
function ‘static std::string AabbVisitor<Box>::__str__(const 
boost::python::api::object&) [with Box = 
Eigen::AlignedBox<boost::multiprecision::number<boost::multiprecision::backends::float128_backend,
 boost::multiprecision::et_off>, 2>]’:
/<<PKGBUILDDIR>>/py/high-precision/minieigen/visitors.hpp:975:39: note: unnamed 
temporary defined here
  975 |                 const Box&         self = py::extract<Box>(obj)();
      |                                       ^~~~~~~~~~~~~~~~~
cc1plus: all warnings being treated as errors
make[4]: *** [py/CMakeFiles/_minieigenHP.dir/build.make:93: 
py/CMakeFiles/_minieigenHP.dir/high-precision/_ExposeBoxes.cpp.o] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/debian/build-double'
make[3]: *** [CMakeFiles/Makefile2:815: py/CMakeFiles/_minieigenHP.dir/all] 
Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>/debian/build-double'
make[2]: *** [Makefile:139: all] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/debian/build-double'
dh_auto_build: error: cd debian/build-double && make -j1 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:72: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:24: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: yade
Source-Version: 2022.01a-10
Done: Anton Gladky <[email protected]>

We believe that the bug you reported is fixed in the latest version of
yade, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky <[email protected]> (supplier of updated yade 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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 21 Aug 2022 12:23:09 +0200
Source: yade
Architecture: source
Version: 2022.01a-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<[email protected]>
Changed-By: Anton Gladky <[email protected]>
Closes: 1013072 1013932
Changes:
 yade (2022.01a-10) unstable; urgency=medium
 .
   * [5528878] Fix GCC-12 FTBFS. (Closes: #1013072)
   * [884074b] Fix tests. (Closes: #1013932)
   * [2641285] Set Standards-Version: 4.6.1
Checksums-Sha1:
 fb0856bdc23ba5586b700f03671cae386811aaa3 3251 yade_2022.01a-10.dsc
 fda1b45e2a36a9d10489e6b18d4cc278370a24b2 48284 yade_2022.01a-10.debian.tar.xz
 e933efaf68ee53dd4352257d5f06d79c0103556d 30043 
yade_2022.01a-10_source.buildinfo
Checksums-Sha256:
 f1dc2478737a730aa657f59b97ded4b1bf0ea20724844755d26a3eb204a2515d 3251 
yade_2022.01a-10.dsc
 47d213e8408348fd2aaccb220ed909d4d9dbb338114b25533dd7548e1794e791 48284 
yade_2022.01a-10.debian.tar.xz
 72d4e35eb3f061bfa72b8f815e975a30bf6276f3f9f1ffe4a9ed99a80303d6d6 30043 
yade_2022.01a-10_source.buildinfo
Files:
 9a6f845a6558a4204f4c46a9e596f1d6 3251 science optional yade_2022.01a-10.dsc
 1a8f613ec46b5f3598d30cfb8256a873 48284 science optional 
yade_2022.01a-10.debian.tar.xz
 08c25239a60c5f634e2b915fd64107e5 30043 science optional 
yade_2022.01a-10_source.buildinfo

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

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmMCNe8ACgkQ0+Fzg8+n
/wYJig/+LnyZLNiqf/2bSfCjnBIICIZ4dsAsQj0g/UNDiQXbtw5vEW+gQAgqtmhS
jp6Js06L7vdw16QD+r+tKbc+xHmXm/MuEmkLl0wGL65UhOrqbpj7CaTNQejnr9m8
/rKVhbJjg0sN6/LPbJt02f2Hg4T+EC6M1uYjzsM0E3babuZEsLARtfdjbvcJac+T
2TI6Xq2Fd85PEOcS9TSMom2IWDqrcg/YtxU+CNQrg8NucGoiUp8rV5aASfp8K7S0
xrHnxFArFkzfm/WxwjoaUcwD9QWDLcFS0l09elQPlIveeBX8I8NegH/XRZYLza6a
OdSnd4Umzau4UFkAoEL70NCb3Vq9aobPL6y8eu9Iy63wTRRyRF6PkZE528giRIgZ
toh5lmHEXKc5mn9v8zP4Ql86e/ZYPCgzMjP4RTXvFsbZwsvUVBjkVI1/0LkR5jnL
ZnNaitUD9Y1RaHYx4BHWjyCk2kwHFbFBr9TDE9kJb3DjFNrUURV9fHootRu37/3Y
j2ufn5FL8yJhrxsAUGOpxuLp4VXWvUSdgBecDYG4h7Nz4bZjAder13fDlT3K2U4K
v0WL4S5J3rhMVdiBWKb35OK0tV0Onrn/feRGS58lMIDMbik59rnhbbnzv6de3P/A
vm54r5M/2y6J1dJmSL9OQRmFB8qXqB2pwJR5noo1LkdDcdJkQUM=
=+jDd
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to