Processed: Re: Bug#793976: ruby-netcdf: FTBFS with netcdf in experimental / update to 0.7.1
Processing commands for cont...@bugs.debian.org: fixed 793976 ruby-netcdf/0.7.1.1-2 Bug #793976 [ruby-netcdf] ruby-netcdf: FTBFS with netcdf in experimental Marked as fixed in versions ruby-netcdf/0.7.1.1-2. thanks Stopping processing here. Please contact me if you need assistance. -- 793976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#793976: ruby-netcdf: FTBFS with netcdf in experimental / update to 0.7.1
Control: found -1 ruby-netcdf/0.7.1.1-1 Control: tags -1 patch Hi Youhei, Thanks for packaging the latest upstream release and your prompt response. On 29-07-15 16:23, Youhei SASAKI wrote: I'll prepare new upstream release ASAP. ruby-netcdf (0.7.1.1-1) no longer fails the main() check, but it doesn't accept the 4.4.0-rc version we currently have in experimental: extconf.rb:55:in `main': Invalid netcdf version: 4.4.0-rc. Use --with-netcdf-version= (RuntimeError) Patching the version check regex to support an optional -rc suffix allows the build to start (patch attached), but it fails to find the HDF5 libraries: gcc -shared -o netcdfraw.so netcdfraw.o -L. \ -L/usr/lib/x86_64-linux-gnu -L/usr/lib -L/usr/local/lib \ -L/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0 -L. \ -Wl,-z,relro -L/build/ruby2.1-_39Jjj/ruby2.1-2.1.5/debian/lib \ -fstack-protector -rdynamic -Wl,-export-dynamic \ -L/usr/lib -lnetcdf -lhdf5_hl -lhdf5 -lz -ldl -lm -lcurl -lruby-2.1 \ -lpthread -lgmp -ldl -lcrypt -lm -lc /usr/bin/ld: cannot find -lhdf5_hl /usr/bin/ld: cannot find -lhdf5 collect2: error: ld returned 1 exit status This is a common problem with the new netcdf packages in experimental. I'm not sure all affected reverse dependencies need to specify the hdf5 library themselves, we should probably fix this in libnetcdf-dev by patching nc-config netcdf.pc. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 0001-Add-patch-to-support-NetCDF-4.4.0-rc-version.patch Description: application/pgp-encrypted ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Processed: Re: Bug#793976: ruby-netcdf: FTBFS with netcdf in experimental / update to 0.7.1
Processing control commands: found -1 ruby-netcdf/0.7.1.1-1 Bug #793976 [ruby-netcdf] ruby-netcdf: FTBFS with netcdf in experimental / update to 0.7.1 The source ruby-netcdf and version 0.7.1.1-1 do not appear to match any binary packages Marked as found in versions ruby-netcdf/0.7.1.1-1. tags -1 patch Bug #793976 [ruby-netcdf] ruby-netcdf: FTBFS with netcdf in experimental / update to 0.7.1 Added tag(s) patch. -- 793976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#793976: ruby-netcdf: FTBFS with netcdf in experimental / update to 0.7.1
On 30-07-15 14:00, Sebastiaan Couwenberg wrote: On 29-07-15 16:23, Youhei SASAKI wrote: I'll prepare new upstream release ASAP. ruby-netcdf (0.7.1.1-1) no longer fails the main() check, but it doesn't accept the 4.4.0-rc version we currently have in experimental: extconf.rb:55:in `main': Invalid netcdf version: 4.4.0-rc. Use --with-netcdf-version= (RuntimeError) Patching the version check regex to support an optional -rc suffix allows the build to start (patch attached), but it fails to find the HDF5 libraries: [...] This is a common problem with the new netcdf packages in experimental. I'm not sure all affected reverse dependencies need to specify the hdf5 library themselves, we should probably fix this in libnetcdf-dev by patching nc-config netcdf.pc. The netcdf rc version patch is still required to build successfully with the new netcdf packages in experimental, but no changes are required for the HDF5 linking issue. In netcdf (1:4.4.0~rc2-1~exp4) I've patched nc-config and netcdf.pc to include the HDF5 library include paths. That solves the linking issue for all affected packages. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#793976: ruby-netcdf: FTBFS with netcdf in experimental / update to 0.7.1
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 ruby-netcdf_0.6.6-3_netcdf-ftbfs.build.xz Description: application/xz ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#793976: ruby-netcdf: FTBFS with netcdf in experimental / update to 0.7.1
Hi, thanks for your notice. I'll prepare new upstream release ASAP. 2015/07/29 wrote: 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 ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
