Re: Bug#712688: transition: gdal
-----BEGIN PGP SIGNED MESSAGE-----
On 01/01/2014 03:12 PM, Sebastiaan Couwenberg wrote:
> An outstanding issue with the GDAL 1.10.1 package in Debian is that
> we still need to update the symbols files.
> The README.source states that this process involved "a bit of
> vi/sed magics", which I didn't use but a quick and dirty Perl
> I should probably rerun the script on the 1.10.1+dfsg-2 packages
> to see if the changes remained stable between -1 and -2.
The changes to the common C symbols have remained stable between -1
and -2, only the C++ symbols for s390x changed for -2.
I've cleaned up the script used to generate the symbols files, and
added it to the GDAL package.
The symbols files still use @GDAL_1.8 via debian/gdal.ver, which I
suspect should be changed to @GDAL_1.10 now.
I'm not sure how the gdal.ver file should be maintained, and hope it
doesn't require adding symbols per upstream version to use the correct
The new GDAL version also fixes the FTBFS on hurd-i386 where it could
finally be build now that the xerces-c build was fixed.
So we should soon have GDAL on all archs again, allowing the same for
its reverse dependencies. But the symbols question is not entirely
GnuPG: 0xE88D4AF1 (new) / 0x77A975AD (old)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
-----END PGP SIGNATURE-----