Your message dated Mon, 03 Aug 2020 18:04:24 +0000
with message-id <e1k2eoy-000a0h...@fasolo.debian.org>
and subject line Bug#957932: fixed in whitedb 0.7.3+git200711-1
has caused the Debian Bug report #957932,
regarding whitedb: ftbfs with GCC-10
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.)


-- 
957932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:whitedb
Version: 0.7.3-4
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/whitedb_0.7.3-4_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

[...]
checking fixpoint enc/dec for j 2, value 790.345600
checking fixpoint enc/dec for j 3, value -799.789100
checking fixpoint enc/dec for j 4, value 0.002346
checking str enc/dec for j 0, value "abc", extra "(null)"
checking str enc/dec for j 1, value "abcdefghijklmnop", extra "(null)"
checking str enc/dec for j 2, value "1234567890123456789012345678901234567890", 
extra "op12345"
checking str enc/dec for j 3, value "", extra "asdasdasdsd"
checking str enc/dec for j 4, value "", extra "(null)"
checking xmlliteral enc/dec for j 0, value "ffoo", extra "bar:we"
checking xmlliteral enc/dec for j 1, value "ffooASASASasaasweerrtttyyuuu", 
extra "bar:weasdasdasdasdasdasdasdasdasdasdasdasdasddas"
checking uri enc/dec for j 0, value "dasdasdasd", extra ""
checking uri enc/dec for j 1, value "dasdasdasd12345678901234567890", extra 
"fofofofof"
checking blob enc/dec for j 0, len 10 extra "type1"
checking blob enc/dec for j 1, len 200 extra "type2"
checking blob enc/dec for j 2, len 10 extra "(null)"
checking rec creation, content read/write for j 0, length 0
checking rec creation, content read/write for j 1, length 1
checking rec creation, content read/write for j 2, length 2
checking rec creation, content read/write for j 3, length 3
checking rec creation, content read/write for j 4, length 4
checking rec creation, content read/write for j 5, length 5
checking rec creation, content read/write for j 6, length 100
checking rec creation, content read/write for j 7, length 101
checking rec creation, content read/write for j 8, length 10000
checking rec creation, content read/write for j 9, length 10001
checking var enc/dec for j 0, value 0
checking var enc/dec for j 1, value 999882
checking decoding data that doesn't fit the decode buffer (expecting some 
errors)
********* check_datatype_writeread ended without errors ************
********* testing string parsing ************
parsing string: ""
parsing string: " "
check_parse_encode: expected value " ", got "�,6
"

***** Quick test failed ******
FAIL Test/common.test (exit status: 1)

SKIP: Test/log
==============

logging disabled, skipping checks

***** Log test succeeded ******
SKIP Test/log.test (exit status: 77)

============================================================================
Testsuite summary for WhiteDB 0.7.3
============================================================================
# TOTAL: 2
# PASS:  0
# SKIP:  1
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0
============================================================================
See ./test-suite.log
============================================================================
make[4]: *** [Makefile:818: test-suite.log] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>'
make[3]: *** [Makefile:926: check-TESTS] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>'
make[2]: *** [Makefile:1150: check-am] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [Makefile:703: check-recursive] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:19: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

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

We believe that the bug you reported is fixed in the latest version of
whitedb, 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 957...@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 whitedb 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: Mon, 03 Aug 2020 18:39:28 +0200
Source: whitedb
Architecture: source
Version: 0.7.3+git200711-1
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) <g...@debian.org>
Changed-By: Laszlo Boszormenyi (GCS) <g...@debian.org>
Closes: 957932
Changes:
 whitedb (0.7.3+git200711-1) unstable; urgency=medium
 .
   * Git snapshot release:
     - fixes FTBFS with GCC 10 (closes: #957932).
   * Add source Lintian overrides.
   * Update watch file.
   * Update debhelper level to 12 .
   * Update Standards-Version to 4.5.0:
     - don't specify parallel to debhelper.
Checksums-Sha1:
 ad16309baf8d759f43a02f31122647708e670660 1876 whitedb_0.7.3+git200711-1.dsc
 c767027c986d9996af81621a82be2205d6b9c5a6 539508 
whitedb_0.7.3+git200711.orig.tar.xz
 55acd29352175ac656e0de629624c75ddf88cd52 3548 
whitedb_0.7.3+git200711-1.debian.tar.xz
Checksums-Sha256:
 4e80cf90e931cbd2f61456299c7db82299e6dd29392135697970f4f0423b0622 1876 
whitedb_0.7.3+git200711-1.dsc
 3b1510d90ad325b962c6be55228fe6a895194c2c8ad0da5492a42928fbd04d82 539508 
whitedb_0.7.3+git200711.orig.tar.xz
 a01d343d80dfdf48b581a196cb47b3abcce773e10c3238e18ddc0cb9444ec87d 3548 
whitedb_0.7.3+git200711-1.debian.tar.xz
Files:
 89e16b0407738278bbdc9f13addb64a1 1876 devel optional 
whitedb_0.7.3+git200711-1.dsc
 9ee638126c2006403127112cc3de23e1 539508 devel optional 
whitedb_0.7.3+git200711.orig.tar.xz
 bdeb430d9a9d69c02612a6fda468ed21 3548 devel optional 
whitedb_0.7.3+git200711-1.debian.tar.xz

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

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl8oTHYACgkQ3OMQ54ZM
yL+iTw/8DI9VzHN8lrS+CgdMYkg6Rj4cO45CgIAtcNqWrJpoeJxiASNvJ9JaYfLT
z0wJmKEmeSMaXMn1dv2/KtknJzDcGrPfCw3MIDiVaanTr0y8ygNAJMVx13NKBOx+
sZ05skbuCR55vknwy8gTPMhjpArhJEfO+f6z4BmIc8wLiRj15Yh9/eFvOY+kt330
XBGkS3G50Ct+ocVZxnEOcFQ7xgKK0CjvSCgd9tscRVCwady4Iixjkp29qZKmeBQj
j7n8/JY2j4QlI26eDIQDdn7J9+VryS5E+RREV+ijaFB3oGkpPRXLfGBJzAerVsWs
5XSW0C0yzJAsHmg5/oPwRw1E+QaFAalNoDkpHlsr6vV6lGMORxTt9ykB1TjOoOQk
Ss5f29AGhjyYAJsaeRsnxI7j1pdm38NL+QGmcVqJDXkUWxgfTK5spyOzMR3PZz+2
1PSax7BxBiAIe0oj58nescovErtNtiILrHDBwEKeA/HUjfVwzkTyUcMu0yEaYU+m
0Z6KvxOifmT2tJetGakOkwVuSWHh9hPf9XQzQf250m9J/RzZi+3vXzgkTqLHQZVs
UomkahIQgAqUSaTYbLcNH0angVMNzi2D9wte/aTCfNYFR2lCg626IR++ETMG1qzV
fi3OSlyVkL5tPEWZlQcH3Pp9KiMxmCcU9QZxK5vHWUPNsc2hKSA=
=KEGh
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to