Your message dated Fri, 31 Jul 2015 12:18:37 +0200
with message-id <55bb4b7d.8050...@xs4all.nl>
and subject line Re: Bug#793976: ruby-netcdf: FTBFS with netcdf in experimental 
/ update to 0.7.1
has caused the Debian Bug report #793976,
regarding ruby-netcdf: FTBFS with netcdf in experimental
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 ---
fixed 793976 ruby-netcdf/0.7.1.1-2
thanks

Hi Youhei,

Thanks for your quick second revision to include the -rc version patch.

Your latest ruby-netcdf package builds successfully with the new netcdf
packages in experimental.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

--- 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