[Qgis-developer] 2.10 segfaults on startup

[Radim Blazek]

On Tue, Jun 30, 2015 at 4:42 PM, Sebastiaan Couwenberg
<sebastic at xs4all.nl> wrote:
>> On Tue, Jun 30, 2015 at 1:41 PM, Sebastiaan Couwenberg wrote:
>>> The final SpatiaLite 4.3.0 release will be soon (see the recent thread
>>> on the spatialite-users list). [1]
>>>
>>> I hope to start the spatialite transition in Debian soon after its
>>> release
>>> to finally get rid of the problematic SpatiaLite 4.1.1 now that it's
>>> rebuild with PROJ.4 4.9.1. [2][3]
>>
>> What time horizon do you see for the new SpatiaLite to get to Debian?
>
> I expect that we can start the spatialite transition soon after its
> release, but this mostly depends on the Release Team which manages the
> transitions.
>
> The scope of the spatialite transition is quite limited, it mostly
> collides with the packages in the gdal transition that's currently blocked
> from starting by the uncoordinated mapnik 3 transition.
>
> There is also the uncoordinated libdap transition which prevents testing
> migration of the gdal package, that needs to be resolved before the
> spatialite transition can start.
>
> https://release.debian.org/transitions/html/auto-spatialite.html
>
>> Is there a chance to release 2.10.1?
>
> I expect the spatialite to happen during the 4 month life of the 2.10
> release, but with vacations and DebConf starting in the next 2 months we
> may not make it if the Release Team doesn't give the go-ahead for the
> spatialite transition soon after its final release.

Ah, sorry, the question about 2.10.1 was more for Jef, I mean if it
makes sense to do the workaround with mutex in QGIS and backport it to
2.10 branch.
Anyway, seeing the terms in Debian, we have to fix it in master.

Radim

> Kind Regards,
>
> Bas
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer