Hello Bas,

On Tue, 20 Oct 2015 09:06:02 +0200, Sebastiaan Couwenberg wrote:
With JEJK_topoC9k_ZABA10mHbpv.nc I can now confirm that the issue is not
present in gdal (1.11.2+dfsg-3+b2) on unstable:

thank you for the suggestion.
Since the full downgrade is difficult for me (due to dependencies of other software), I'd rather upgrade.

After short investigation I found the only related difference between unstable and testing in libnetcdf7. And yes, it was there! When I upgraded just from libnetcdf7_4.4.0~rc2-1 (testing) to libnetcdf7_4.4.0~rc2-1+b1 (unstable) it seems, all (in the chain) started to work correctly.

My current version of related packages shoud be the same as in unstable, i.e. gmt 5.1.2+dfsg1-2+b1, gdal and libgdal1i 1.11.2+dfsg-3+b2, libhdf5-10 1.8.15-patch1+docs-4 and libnetcdf7 1:4.4.0~rc2-1+b1.

Therefore, it seems to be just a temporary issue of testing, that should be solved with libnetcdf7_4.4.0~rc2-1+b1 migration.

So, one might consider to close the bug.
Meanwhile, just the dependence of libgdal1i could be restricted to an appropriate version of libnetcdf7, nevertheless, it is safe to ignore this issue completely, because just a 'temporary' libnetcdf7_4.4.0~rc2-1 seems to be broken.

Best regards,


Pkg-grass-devel mailing list

Reply via email to