It was raised there 4.5 years ago: http://bugzilla.maptools.org/show_bug.cgi?id=1463.
Might be nice if PostGIS maintainers could "bug" that developer about resolution? The proposed local patch is changing int to long on three variables. While that may not be graceful, could it work as a temporary workaround? <http://bugzilla.maptools.org/show_bug.cgi?id=1463>Aren On Sat, Jan 1, 2011 at 7:05 AM, Mark Cave-Ayland < mark.cave-ayl...@siriusit.co.uk> wrote: > On 01/01/11 06:46, Paul Ramsey wrote: > > No workarounds. I thought there was a braindead patch on that ticket >> already, but it's not a patch I feel good enough to apply as a >> permanent fix. >> >> P. >> > > Yeah. Also since we've recently resynced with upstream shapelib, I'd much > rather the issue is raised/fixed there and then we can just resync once > again. > > > ATB, > > Mark. > > -- > Mark Cave-Ayland - Senior Technical Architect > PostgreSQL - PostGIS > Sirius Corporation plc - control through freedom > http://www.siriusit.co.uk > t: +44 870 608 0063 > > Sirius Labs: http://www.siriusit.co.uk/labs > > _______________________________________________ > postgis-users mailing list > postgis-users@postgis.refractions.net > http://postgis.refractions.net/mailman/listinfo/postgis-users >
_______________________________________________ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
