Your message dated Sat, 01 Aug 2015 10:10:14 +0200
with message-id <55bc7ee6.2000...@debian.org>
and subject line now fixed in gcc-5 5.2.1-14
has caused the Debian Bug report #778112,
regarding schroot: ftbfs with GCC-5
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.)
--
778112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:schroot
Version: 1.6.10-1
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5
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-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/schroot_1.6.10-1_unstable_gcc5.log
The last lines of the build log are at the end of this report.
To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t experimental install g++
Common build failures are C11 as the default C mode, 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-5/porting_to.html
[...]
6: - regex_error
6:
6:
6: 2) test: test_run_parts::test_run (E)
6: uncaught exception of type std::regex_error
6: - regex_error
6:
6:
6: 3) test: test_run_parts::test_run3 (E)
6: uncaught exception of type std::regex_error
6: - regex_error
6:
6:
6/8 Test #6: sbuild-run-parts .................***Failed 0.01 sec
test 7
Start 7: schroot-base-option-action
7: Test command: /«PKGBUILDDIR»/debian/build/test/schroot-base-option-action
7: Test timeout computed to be: 9.99988e+06
7: ........
7:
7:
7: OK (8 tests)
7:
7:
7/8 Test #7: schroot-base-option-action ....... Passed 0.01 sec
test 8
Start 8: cleanup-test-data
8: Test command: /«PKGBUILDDIR»/debian/build/test/cleanup-test-data
8: Test timeout computed to be: 9.99988e+06
8/8 Test #8: cleanup-test-data ................ Passed 0.01 sec
75% tests passed, 2 tests failed out of 8
Total Test time (real) = 0.17 sec
The following tests FAILED:
Errors while running CTest
2 - sbuild-chroot-chroot (Failed)
6 - sbuild-run-parts (Failed)
make[2]: *** [test] Error 8
Makefile:117: recipe for target 'test' failed
make[2]: Leaving directory '/«PKGBUILDDIR»/debian/build'
make[1]: *** [install-arch] Error 2
debian/rules:83: recipe for target 'install-arch' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [binary-arch] Error 2
debian/rules:39: recipe for target 'binary-arch' failed
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit
status 2
--- End Message ---
--- Begin Message ---
the regex issue is now fixed in the default GCC in unstable. confirmed by a
non-change rebuild of schroot.
--- End Message ---
