Landon Fuller wrote:
> OK, I implemented the fixes for issue #13699:
> geos2 committed in r38824.
> py25-matplotlib-basemap updated in r38825.
> py-matplotlib-basemap updated in r38826.
> geos updated to 3.0.0 in r38827.
> matplotlib-basemap port revisions bumped in r38828 to en
On Jul 31, 2008, at 9:38 PM, Adam Mercer wrote:
On Thu, Jul 31, 2008 at 11:23 PM, Landon Fuller
<[EMAIL PROTECTED]> wrote:
On Jul 31, 2008, at 9:05 PM, Adam Mercer wrote:
On Thu, Jul 31, 2008 at 7:07 PM, <[EMAIL PROTECTED]> wrote:
3.0 's C-API is both API and binary compatible with the 2
On Thu, Jul 31, 2008 at 11:23 PM, Landon Fuller <[EMAIL PROTECTED]> wrote:
>
> On Jul 31, 2008, at 9:05 PM, Adam Mercer wrote:
>
>> On Thu, Jul 31, 2008 at 7:07 PM, <[EMAIL PROTECTED]> wrote:
>>
>>> 3.0 's C-API is both API and binary compatible with the 2.x release, and
>>> I
>>> tested building
On Jul 31, 2008, at 9:05 PM, Adam Mercer wrote:
On Thu, Jul 31, 2008 at 7:07 PM, <[EMAIL PROTECTED]> wrote:
3.0 's C-API is both API and binary compatible with the 2.x
release, and I
tested building / running PostGIS.
No it is not, py25-matplotlib-basemap is now broken, it does not build
On Thu, Jul 31, 2008 at 11:05 PM, Adam Mercer <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 31, 2008 at 7:07 PM, <[EMAIL PROTECTED]> wrote:
>
>> 3.0 's C-API is both API and binary compatible with the 2.x release, and I
>> tested building / running PostGIS.
>
> No it is not, py25-matplotlib-basemap is
On Thu, Jul 31, 2008 at 7:07 PM, <[EMAIL PROTECTED]> wrote:
> 3.0 's C-API is both API and binary compatible with the 2.x release, and I
> tested building / running PostGIS.
No it is not, py25-matplotlib-basemap is now broken, it does not build
against 3.0.x!
