[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#712688: transition: gdal



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

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
> script.
> 
> [...]
> 
> 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.

http://anonscm.debian.org/gitweb/?p=pkg-grass/gdal.git;a=blob;f=debian/gdal-symbols.pl

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
@GDAL_<version>.

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
resolved yet.

Kind Regards,

Bas

- -- 
GnuPG: 0xE88D4AF1 (new) / 0x77A975AD (old)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBCgAGBQJS0URMAAoJEGdQ8QrojUrxZa8QAIGYEfoTAjqfGCtaPJcfwxtv
EiQutJKFSV63+my5qpXJe2cTKISWGuCkapWXwGuv1Hww7mwJdWKBFJZBOExi12VC
sQQ5OHuiC3zNxtKmLQW8G4rwNfgIWP5XOhTzGFKXbj7t48D9a/fLeB43oWDVnH4Y
iLxfwZixbgWE7VlsJRW5637voIKisqvsGbE5X08S/EdAoMWMTfcHjCHyJGgDMcbR
0zNjVNxTVpHw3oU+pa/JH2Ra5xvu2Lh1T8wih9Kfaa4k7Vc5KUyWO87eMD70zNrJ
iKUrWeKHbkwSVU+ejuLHO/njDIXao0z1t25kDU33B/IX4A2wiamnvzrmhfMrbfGC
M3pMXQi4vCqDZLjLaX1CmWAfO07BRNGxcUXY5U7bseR1HEBJIarfVwkEKn25g5gk
Yi8tFg4AtcyqXRoBV+05bewzMcIxlFrQx9rAZXz3Pb+a2Rd/FNVprpbn54/AnZBD
TPGUJXcfyhn92n8WmRBpRw+AR4+KRkT/1CxwC1j02ohBOCQfJeEI9T34mPw80onw
kvjIbFYBvFUYIDfAOU9V8cO/ceO+hUTrhmP/FbN/byjRoeW5FgWiqQQ86A4yWkQq
9X1u+V5+8szFx8hGEpiKafP8WEOgFv0Pwa2KeVdcI20NEzaseXb4nlnDr13Vzxkx
Jzo3BoehzdRf7ollzyWl
=lLoH
-----END PGP SIGNATURE-----


Reply to: