Your message dated Wed, 29 Jul 2020 17:49:18 +0000
with message-id <e1k0qcc-0008u2...@fasolo.debian.org>
and subject line Bug#957440: fixed in libgetdata 0.10.0-8
has caused the Debian Bug report #957440,
regarding libgetdata: 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.)


-- 
957440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libgetdata
Version: 0.10.0-6
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/libgetdata_0.10.0-6_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

[...]
  435 |   GD_COMPLEX128, data_out)
      |                 2                                                   
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(COMPLEX(4)/COMPLEX(8)).
getdata.f90:406:66:

  406 |   first_frame, first_sample, num_frames, num_samples, GD_FLOAT64, 
data_out)
      |                                                                  1
......
  435 |   GD_COMPLEX128, data_out)
      |                 2                                                 
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(REAL(8)/COMPLEX(8)).
getdata.f90:392:66:

  392 |   first_frame, first_sample, num_frames, num_samples, GD_FLOAT32, 
data_out)
      |                                                                  1
......
  435 |   GD_COMPLEX128, data_out)
      |                 2                                                 
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(REAL(4)/COMPLEX(8)).
getdata.f90:378:64:

  378 |   first_frame, first_sample, num_frames, num_samples, GD_INT64, 
data_out)
      |                                                                1
......
  435 |   GD_COMPLEX128, data_out)
      |                 2                                               
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(8)/COMPLEX(8)).
getdata.f90:364:64:

  364 |   first_frame, first_sample, num_frames, num_samples, GD_INT32, 
data_out)
      |                                                                1
......
  435 |   GD_COMPLEX128, data_out)
      |                 2                                               
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(4)/COMPLEX(8)).
getdata.f90:350:64:

  350 |   first_frame, first_sample, num_frames, num_samples, GD_INT16, 
data_out)
      |                                                                1
......
  435 |   GD_COMPLEX128, data_out)
      |                 2                                               
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(2)/COMPLEX(8)).
getdata.f90:336:63:

  336 |   first_frame, first_sample, num_frames, num_samples, GD_INT8, data_out)
      |                                                               1
......
  435 |   GD_COMPLEX128, data_out)
      |                 2                                              
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(1)/COMPLEX(8)).
getdata.f90:322:63:

  322 |   first_frame, first_sample, num_frames, num_samples, GD_NULL, 0)
      |                                                               1
......
  435 |   GD_COMPLEX128, data_out)
      |                 2                                              
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(4)/COMPLEX(8)).
make[4]: *** [Makefile:665: getdata.o] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/build-main/bindings/f77'
make[3]: *** [Makefile:581: all-recursive] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/build-main/bindings'
make[2]: *** [Makefile:585: all-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>/build-main'
dh_auto_build: error: cd build-main && make -j4 returned exit code 2
make[1]: *** [debian/rules:37: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:22: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: libgetdata
Source-Version: 0.10.0-8
Done: Alastair McKinstry <mckins...@debian.org>

We believe that the bug you reported is fixed in the latest version of
libgetdata, 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.
Alastair McKinstry <mckins...@debian.org> (supplier of updated libgetdata 
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: SHA256

Format: 1.8
Date: Thu, 23 Jul 2020 18:52:16 +0100
Source: libgetdata
Architecture: source
Version: 0.10.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Alastair McKinstry <mckins...@debian.org>
Closes: 957440
Changes:
 libgetdata (0.10.0-8) unstable; urgency=medium
 .
   * Fix FTBFS with fortran 10. Closes: #957440
   * Use debhelper level 13
   * Ship files pointed out by dh_missing.
   * Add lintian-overrides for false positives on libc linking
   * Drop xz hard-coded compression
Checksums-Sha1:
 9696c4e541b0e32eefe4bec04d7e379688dd177d 2752 libgetdata_0.10.0-8.dsc
 95766faac1db7d736e066011f8d4a6b4b67b705c 6496 libgetdata_0.10.0-8.debian.tar.xz
Checksums-Sha256:
 f83aa5b3b174a87f9ea4efab4399b5f1195e90fcfcaf4e97d0a3fbcdf5ff4ca8 2752 
libgetdata_0.10.0-8.dsc
 80565559c218b599c97850faa6cb8c9f04d42744999bc5968199d5aa1b498312 6496 
libgetdata_0.10.0-8.debian.tar.xz
Files:
 eff05a6466808d3e9c70885fb0a32ee3 2752 science optional libgetdata_0.10.0-8.dsc
 33bd5e5b5b6f1ab1b3236668f838a69f 6496 science optional 
libgetdata_0.10.0-8.debian.tar.xz

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

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl8htEgACgkQy+a7Tl2a
06X4Wg/+LTZJsdvA7R2syaaEOxeOYHEWgcuAsvinFEF0nn4tQ6aSpuccL3hooCYh
sM1X037eJYOci4OVrFu9JiLZXuy7RQO6uo6TPHSPiqU/9omOr7kGzIwZpRc+ORbl
DsQEWJqckJeKzRIRor71LR5Rc6IRlGabH7jScsLKyVcPLdbTQq66gMoUTH0MVXys
9iOZMD4iDjxNJO25P5994LSFo5ExyDfLm/B8xWI4HlG+B2VOuoCJWSRU7ZsOv+ng
0/ELTuZ+WEZ2IyZEt0Z5NaVTD+dhh0KN1O0YTPf8NVbFvgCVSCyQb7juLNrYKsyr
aCrY8QcUPLr5I2SXxh8eeT9xogK95UUntp1C90bw2pfluRzfCsw4wcT5oItfJYAz
RJwOUNxR6+ee9WRqtpqr4iIcG3m4An5JVAsbOojKr1TbFP1fyH81tHGUv3cwtmqg
Jy+cXrrDqSnPd2KfNOkXaqPsojImy+tFYbxZK7825UYZve3iw7KxigaFV6xV/zfD
O0Cu4tQUuD0+ICLY8xJq+5vofw+FFoMW9nWEko2k2c2Iqwev5h1xUGRZiENknuIM
wW32fxTn9R6Jc2mo1rH6OLbrSwe9EmOPozL17ARhaHlQeAFUfIUs4WykGnNOpNaE
MpH2dz4LDFi7jcrf9DwJAhQiTmp4uUwXDib9ApDpzKdpUBa595M=
=lyxJ
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to