Your message dated Wed, 09 Oct 2019 14:37:39 +0000
with message-id <e1iid5v-000f6i...@fasolo.debian.org>
and subject line Bug#925706: fixed in graywolf 0.1.6-2
has caused the Debian Bug report #925706,
regarding graywolf: ftbfs with GCC-9
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.)


-- 
925706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:graywolf
Version: 0.1.6-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

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-9/g++-9, but succeeds to build with gcc-8/g++-8. 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/gcc9-20190321/graywolf_0.1.6-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

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

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
-pin name sr<1> signal sr<1> layer 1 -340 5040
+pin name sr<1> signal sr<1> layer 1 -340 1540
 
 pad 34 name twpin_sr<2>
 corners 4
--440 5120 -440 5280 -240 5280 -240 5120 
+-440 1240 -440 1400 -240 1400 -240 1240 
 orient 7
-pin name sr<2> signal sr<2> layer 1 -340 5200
+pin name sr<2> signal sr<2> layer 1 -340 1320
 
 pad 35 name twpin_sr<3>
 corners 4
--440 5280 -440 5440 -240 5440 -240 5280 
+-440 1020 -440 1180 -240 1180 -240 1020 
 orient 7
-pin name sr<3> signal sr<3> layer 1 -340 5360
+pin name sr<3> signal sr<3> layer 1 -340 1100
 
 pad 36 name twpin_sr<4>
 corners 4
--440 5440 -440 5600 -240 5600 -240 5440 
+-440 800 -440 960 -240 960 -240 800 
 orient 7
-pin name sr<4> signal sr<4> layer 1 -340 5520
+pin name sr<4> signal sr<4> layer 1 -340 880
 
 pad 37 name twpin_sr<5>
 corners 4
--440 5600 -440 5760 -240 5760 -240 5600 
+-440 580 -440 740 -240 740 -240 580 
 orient 7
-pin name sr<5> signal sr<5> layer 1 -340 5680
+pin name sr<5> signal sr<5> layer 1 -340 660
 
 pad 38 name twpin_sr<6>
 corners 4
--440 5760 -440 5920 -240 5920 -240 5760 
+-440 360 -440 520 -240 520 -240 360 
 orient 7
-pin name sr<6> signal sr<6> layer 1 -340 5840
+pin name sr<6> signal sr<6> layer 1 -340 440
 
 pad 39 name twpin_sr<7>
 corners 4
--440 5920 -440 6080 -240 6080 -240 5920 
+-440 140 -440 300 -240 300 -240 140 
 orient 7
-pin name sr<7> signal sr<7> layer 1 -340 6000
+pin name sr<7> signal sr<7> layer 1 -340 220
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/tests

4/6 Test #3: map9v3-twsc ......................   Passed    3.81 sec
5/6 Test #2: map9v3 ...........................   Passed    3.90 sec
6/6 Test #6: map9v3_other_seed ................   Passed    4.45 sec

83% tests passed, 1 tests failed out of 6

Total Test time (real) =   4.49 sec

The following tests FAILED:
          5 - map9v3-twmc (Failed)
Errors while running CTest
make[2]: *** [Makefile:100: test] Error 8
make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
dh_auto_test: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit 
code 2
make[1]: *** [debian/rules:19: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:13: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

--- End Message ---
--- Begin Message ---
Source: graywolf
Source-Version: 0.1.6-2

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

Debian distribution maintenance software
pp.
Ruben Undheim <ruben.undh...@gmail.com> (supplier of updated graywolf 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: Wed, 09 Oct 2019 16:09:25 +0200
Source: graywolf
Architecture: source
Version: 0.1.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Ruben Undheim <ruben.undh...@gmail.com>
Closes: 925706
Changes:
 graywolf (0.1.6-2) unstable; urgency=medium
 .
   * debian/control:
     - Build-depend on ninja-build, xvfb, xauth and xfonts-base
     - Debhelper 12
     - Standars version 4.4.0 - no changes
   * debian/gitlab-ci.yml: Enable CI on salsa
   * d/patches/0003-Run-the-test-case-within-xvfb-run-since-the-n-option.patch:
     - Run graywolf component in graphical mode during test makes the test pass
       also on i386. (Clearly some hidden bug inside there causing the
       unpredictable test result in non-graphical mode, but no time to debug
       it now)
   * debian/rules:
     - Change from -O2 to -O1 optimisation. (Closes: #925706)
       (Clearly some hidden bug inside there causing the unpredictable test
       result for optimisation level 2, but no time to debug it now)
     - Change to ninja build system
     - Re-enable test for i386
Checksums-Sha1:
 f04432e80266813236fbfbf0014a3bb59255ce2b 2326 graywolf_0.1.6-2.dsc
 da38a9346d7b874c4f42f16805b5d6754467b7ec 9432 graywolf_0.1.6-2.debian.tar.xz
Checksums-Sha256:
 fcf35a75372c986f196bba43ace9cb1fee83bd2d52bff6a07a2d5db8cacc8731 2326 
graywolf_0.1.6-2.dsc
 77bbf8d86479cbdfae32da1beaa2e75aea6546c454b3b82648f37fcdd01a1c57 9432 
graywolf_0.1.6-2.debian.tar.xz
Files:
 5a64a0b66ab720b998728fa38eeaf9a3 2326 electronics optional graywolf_0.1.6-2.dsc
 0b4b1e78e504fc2106bbfe9a1f746e3e 9432 electronics optional 
graywolf_0.1.6-2.debian.tar.xz

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

iQJMBAEBCgA2FiEETeTfPeKePuppVOXOGnb1/BKWi3kFAl2d6j8YHHJ1YmVuLnVu
ZGhlaW1AZ21haWwuY29tAAoJEBp29fwSlot5+bEP/3xVpFHG7Fk3SYlMnU/YK3Vp
p90T7hrt9fdrj5+tgMJfCFpWwOzLEtipwLFYUCJjfqwBo88HnGD2KdLQVIrWGzKe
zpH7+MLGO8PMegZYwuZDyTHtRlS1Q9A1/7SsO5864l7hf6OzT79zovDPrlOzYs+C
IdvSducYzt4vZx/4g4AYx6RxXMHzLEDe3ZPtmCfjLzcoeqCiAYuVnus65fisQxET
09bMkpVzFbH0yqXKpOGIPLxETUBf8q550C5phBLoIpUn5M9bimWmad+ywMXpsGRU
Uocvs04EAk8nUe20Tolu/kEuyZVKdVNFMLcw56B79YSkdIWtd/dJOBiyxVdysEIV
r80WdS6Z/tWYvl/CACaU5UVi14XQQZVvRWk9In+bUkTcgx7Kd9+a8XRjsgTwk4xB
1wG/8NAXeg1TlQVg+Qv+kiMzXvG39VZXXgEbh/nUXo3eNy7ZFHsP/0KeeyalV01p
UyED7Hz/SEy8lhKRqu8AL2yWUgFuz4Yu781ik9bong6FgOTJDlv7uJ1c52r/P5Zh
UYLUD40ip37A10EUFwknvOizKSyVcf5UEwcdu7eClo4UO1/QqeT8nQsUyXeAxs8Q
LgYoLEhDpfAMDyBXaGjucs0Ys0gEQor6gM1IH3HopE0t/5Oyp3NFbcd7sUw8pyUN
yX0+cNGdIb3oPRTdm4kL
=sKIi
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to