Your message dated Tue, 20 Oct 2015 12:19:02 +0200
with message-id <>
and subject line Re: Bug#802321: gdal-bin: NetCDF-4 / HDF5 support broken in 
recent gdal
has caused the Debian Bug report #802321,
regarding gdal-bin: NetCDF-4 / HDF5 support broken in recent gdal
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

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: gdal-bin
Version: 1.11.2+dfsg-3+b2
Severity: grave
Justification: causes non-serious data loss

NetCDF-4 format is not properly recognized in recent gdal (libgdal1i ?).

How to reproduce the bug: 

the attached file  is of NetCDF-4 / HDF5 format, 
see ncdump or h5dump output

$ ncdump -h
netcdf JEJK_topoC9k_ZABA10mHbpv {
        x = 501 ;
        y = 601 ;
        double x(x) ;
                x:long_name = "x" ;
                x:actual_range = -546000., -541000. ;
        double y(y) ;
                y:long_name = "y" ;
                y:actual_range = -1073000., -1067000. ;
        float z(y, x) ;
                z:long_name = "z" ;
                z:_FillValue = NaNf ;
                z:actual_range = 2.38614749908447, 11.5756139755249 ;

// global attributes:
                :Conventions = "COARDS, CF-1.5" ;
                :title = "Produced by grdreformat" ;
                :history = "grdreformat CRJK_topoC9c_ZABAGED10m.grd -R-546000/-541000/-1073000/-1067000" ;
                :GMT_version = "5.1.2 (r14256) [64-bit]" ;

$ ncdump -k 

$ h5dump -n 
HDF5 "" {
 group      /
 dataset    /x
 dataset    /y
 dataset    /z


Now see what about gdal:

$ gdalinfo 
ERROR 4: `HDF5:"":z' does not exist in the file 
and is not recognised as a supported dataset name.

gdalinfo failed - unable to open ''.

The support for NetCDF-4 / HDF-5 output is broken too:

$ gmt grdreformat JEJK_topoC9k_ZABA10mHbpv.grd JEJK_topoC9k_ZABA10mHbpv.xnc=nf
grdreformat (GMTAPI_Export_Grid): NetCDF: HDF error 
[Session gmt (0)]: Error returned from GMT API: GMT_GRID_WRITE_ERROR (19)

Previous gdal version (1.11.1 perhaps? - in stretch) worked well in this 


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gdal-bin depends on:
ii  libc6                            2.19-22
ii  libgcc1                          1:5.2.1-22
ii  libgdal1i []  1.11.2+dfsg-3+b2
ii  libstdc++6                       5.2.1-22

gdal-bin recommends no packages.

Versions of packages gdal-bin suggests:
ii  python-gdal  1.11.2+dfsg-3+b2

-- no debconf information

--- End Message ---
--- Begin Message ---
notfound 802321 gdal/1.11.2+dfsg-3

Hi Otakar,

Good to hear that the netcdf package rebuilt for the hdf5 transition resolves the issue.

The dependencies generated using the symbols verions generally don't include the binNMU version, so we can't easily prevent this kind of issue with just dependencies.

This is one of the primary reasons why transitions to new library version are coordinated with the release team to have all or most packages migrate to testing at the same time.

Kind Regards,


--- End Message ---
Pkg-grass-devel mailing list

Reply via email to