Your message dated Thu, 30 Jul 2015 21:43:27 +0000
with message-id <e1zkvbr-000476...@franck.debian.org>
and subject line Bug#793976: fixed in ruby-netcdf 0.7.1.1-1
has caused the Debian Bug report #793976,
regarding ruby-netcdf: FTBFS with netcdf in experimental / update to 0.7.1
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.)


-- 
793976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-netcdf
Version: 0.6.6-2
Severity: normal
User: debian-...@lists.debian.org
Usertags: netcdf-split-c-f-cxx

Hi Youhei,

We're preparing for the upcoming netcdf transition which will update from
NetCDF 4.1.3 to 4.4.0 and its new lanuague specific releases (NetCDF
C++4 4.2.1, Netcdf C++ legacy 4.2 & NetCDF Fortran 4.4.2).

ruby-netcdf (0.6.6-2) FTBFS with these new netcdf packages in experimental:

 checking for netcdf.h... yes
 checking for main() in -lnetcdf... no
 *** extconf.rb failed ***
 Could not create Makefile due to some reason, probably lack of necessary
 libraries and/or headers.  Check the mkmf.log file for more details.
 You may
 need configuration options.

The full build log is attached.

Just specifying the Multi-Arch library path with the following is not
sufficient to resolve main() check failure:

 override_dh_auto_configure:
        dh_auto_configure -- \
                --with-netcdf-include=/usr/include \
                --with-netcdf-lib=/usr/lib/$(DEB_HOST_MULTIARCH)

While looking into this build failure I noticed that your ruby-netcdf
package limits checks for new upstream releases to the 0.6.x versions,
which excludes the recent 0.7 & 0.7.1 upstream releases.

The RubyNetCDF 0.7.x releases contain improvements for NetCDF-4 support
which is very relevant for upcoming netcdf transition.

Are there good reasons to stick to the 0.6 releases, and would you
object to removing the version constraint in the watch file?

I'd like to update the ruby-netcdf package to the latest upstream
release and upload it to experimental along with the other new netcdf
package.

It may be that the new upstream release is not sufficient either, and
that the new NetCDF built only with the HDF5 MPI variant cause the
incompatibility with ruby-netcdf.

Kind Regards,

Bas

Attachment: ruby-netcdf_0.6.6-3_netcdf-ftbfs.build.xz
Description: application/xz


--- End Message ---
--- Begin Message ---
Source: ruby-netcdf
Source-Version: 0.7.1.1-1

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

Debian distribution maintenance software
pp.
Youhei SASAKI <uwab...@gfd-dennou.org> (supplier of updated ruby-netcdf 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: Thu, 30 Jul 2015 19:23:10 +0900
Source: ruby-netcdf
Binary: ruby-netcdf ruby-netcdf-dbg
Architecture: source amd64
Version: 0.7.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
Changed-By: Youhei SASAKI <uwab...@gfd-dennou.org>
Description:
 ruby-netcdf - Ruby interface of netCDF library
 ruby-netcdf-dbg - Ruby-NetCDF debug symbols
Closes: 793976
Changes:
 ruby-netcdf (0.7.1.1-1) unstable; urgency=medium
 .
   [ Bas Couwenberg ]
   * Add gbp.conf to use pristine-tar by default.
   * Restructure control file with cme.
 .
   [ Youhei SASAKI ]
   * Update debian/watch: use gemwatch
   * Imported Upstream version 0.7.1.1 (Closes: #793976)
     - Thanks to Bas Couwenberg!
   * Running all tests during build
   * Refresh patches
   * Install "demo", "bin" as examples
Checksums-Sha1:
 bb45aa37008d37a4eea6855670826fc4f7ce5cc8 2106 ruby-netcdf_0.7.1.1-1.dsc
 eb3fcdb5f592f65812285abb9042f0afa82e7b98 87507 ruby-netcdf_0.7.1.1.orig.tar.gz
 dd164d7ff560effea01857f7884633fb842814c0 28984 
ruby-netcdf_0.7.1.1-1.debian.tar.xz
 10f90f3b37fc5819454a579041136cfc0f110d63 174154 
ruby-netcdf-dbg_0.7.1.1-1_amd64.deb
 fd5f2184626bc274dcac8b6240c0c8861b9fc263 53824 ruby-netcdf_0.7.1.1-1_amd64.deb
Checksums-Sha256:
 bd9074e8e777e36b3784be6a3222177f97d13a9064e5e6976fdfe05e57888b0e 2106 
ruby-netcdf_0.7.1.1-1.dsc
 4c509cee7ea87a7cb38152520e885767167b2f40d8c5278be1403efd903b65bb 87507 
ruby-netcdf_0.7.1.1.orig.tar.gz
 869fea48826787439e47ccdf6cb5384412dccdda737c88e2cc0a8d59b097fb86 28984 
ruby-netcdf_0.7.1.1-1.debian.tar.xz
 9d109d5eefdc9a1916bbb9b14e3d1a83ff94263d4e5e0df81456a32968b84050 174154 
ruby-netcdf-dbg_0.7.1.1-1_amd64.deb
 14fc79a00f5ca99a3609925bcb32f50a538f8c2add60e2d16c1a4e05183e4cf9 53824 
ruby-netcdf_0.7.1.1-1_amd64.deb
Files:
 45b31e99d467ab69cb5ad25aa4035607 2106 ruby optional ruby-netcdf_0.7.1.1-1.dsc
 fa6d7cc7376e4cc72b60190a61cc02d1 87507 ruby optional 
ruby-netcdf_0.7.1.1.orig.tar.gz
 76f9923e9210cd9b9be26d02a9c0fcf6 28984 ruby optional 
ruby-netcdf_0.7.1.1-1.debian.tar.xz
 ec48cf6025789bf3c6e2d91a5611d92f 174154 debug extra 
ruby-netcdf-dbg_0.7.1.1-1_amd64.deb
 e970ff491809be47f8457d6ad773eb6a 53824 ruby optional 
ruby-netcdf_0.7.1.1-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJVugLeAAoJEJOU81SJHX4HL5AP/2WEtb2c+GronJ6OzhXiQlMv
1xALK1BBfRNk1neOC2QKfKXWWOxl9zOUo5xwToEsEgQYWSVMNGM7Wihs0GjrYP0I
jLIelrcAvMiPqM0km7ZLpvO/Rrb1zE3W4vmdyGJnBiLvkiE2eMTw+LorzjXz/Q3g
EJnfY3yjdL84DJbFeoHvjOnzWIGu36yUyoT1ijOlnwB+ueevC38uwAGnR3beW3tK
sDJVbxYOMHi9D5gUG6Bay7yBBLJ53NBIyqmaEGDPElN/H4b7OEExc6wsyAois82w
0eZrt0TWxh5V4VqGE47dpWKNzImtvkzpRHm8hH8Sz7dSRF1OI5O+gMADsGbseRgt
Fxw5VysFVelLELJuJ07KSbBwhG+qmLNxRLiZGVu0nVzjMpAmCUI4HHy7XVYnJCAk
4Vw7nzGico2X3GwsK9XLMsNSuRRK1CFs8Ya7jAApc/c+iOGlA5zmdZnTrXtwtJ+Z
i+AW5EBAfz1VRyMOiIjst0VbJ420a0aPFssDO3AiE24V4icHsVOaB5M4XEtK3n75
NJ2ftK5biMUeTIbFdNDANov/JASdBI31gw3NJwhWBjGlNvMUNxrc8z/etarRXki9
h7S8TvLng0E4DMywzAjopa2U0jrifhWIGukViCIfHBcCituPcNncoaf1mAb+PiCG
gyRp+078GZz2Ylq+2qsH
=VY8p
-----END PGP SIGNATURE-----

--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Reply via email to