[postgis-devel] PSC Vote - PostGIS 2.5.2 release in about a week
    Regina Obe 
    lr at pcorp.us
       
    Sun Mar  3 11:20:06 PST 2019
    
    
  
I'm fine with release 2.5.2, it feels like a good time to do so.
 
Everyone okay if I release say a week from now.  I'd package this next weekend.
 
Greg is that soon enough for you?  I figure we should have 1 week time to test etc find any glaring issues.
 
Thanks,
Regina
 
From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Darafei "Kom?pa" Praliaskouski
Sent: Sunday, March 03, 2019 2:14 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: Re: [postgis-devel] PROJ 6.0.0 !!
 
This is fixed in PostGIS 2.5.2. Seems we need urgent release?
 
On Sun, Mar 3, 2019 at 8:22 PM Greg Troxel <gdt at lexort.com <mailto:gdt at lexort.com> > wrote:
I have an update to proj 6 in pkgsrc (not yet pushed because it breaks
some things), and am rebuilding things that depend on proj.  postgis is
at 2.5.1 and says:
  checking proj_api.h usability... no
  checking proj_api.h presence... no
  checking for proj_api.h... no
  configure: error: could not find proj_api.h - you may need to specify the directory of a PROJ.4 installation using --with-projdir
  *** Error code 1
which is mostly  unsurprising given
  https://github.com/OSGeo/proj.4/issues/836
As I understand it, 2.5.1 is the most recent actual release.
I am unclear on the game of declaring deprecated API usage; it is not
helpful for me to do that as a packager, since that's basically just
undoing what proj did, and it seems necessary for depending packages to
adapt before the next proj release.
I don't find either 1) not using proj_ahi.h or 2) defining the workaround
listed at
  https://trac.osgeo.org/postgis/query?status=assigned <https://trac.osgeo.org/postgis/query?status=assigned&status=new&status=reopened&group=status&milestone=PostGIS+2.5.2> &status=new&status=reopened&group=status&milestone=PostGIS+2.5.2
I am curious as to thoughts/plans.  I can file tickets if that's
helpful.  Perhaps a workaround for 2.5, and a real fix for trunk unless
it's fixed already.
_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> 
https://lists.osgeo.org/mailman/listinfo/postgis-devel
 
-- 
Darafei Praliaskouski
Support me: http://patreon.com/komzpa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20190303/c6308d1d/attachment-0001.html>
    
    
More information about the postgis-devel
mailing list