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

Bug#756867: transition: gdal



On 19-06-15 14:40, Sebastiaan Couwenberg wrote:
> On 06/19/2015 01:21 PM, Emilio Pozuelo Monfort wrote:
>> On 17/06/15 01:22, Sebastiaan Couwenberg wrote:
>>> OK, I'll keep the alternative dependency template for the C++ symbols
>>> and change the package name. libgdal1i seems an obvious choice to
>>> succeed libgdal1h.
>>
>> ACK. I have updated the transition tracker for that.
> 
> Thanks for the tracker update.
> 
> The updated gdal package was uploaded yesterday and is currently in NEW
> because of the library package rename:
> 
> https://ftp-master.debian.org/new/gdal_1.11.2+dfsg-1~exp4.html

To unblock the various transitions as mentioned in the geos transition
bugreport (#791045) that are waiting for a new gdal build in unstable,

I've prepared a new upload of gdal for experimental. It updates the C++
symbols for all architectures with GCC 5.

Because of an issue in the gdal configure checks, libkml support is
disabled due to the removed third party libraries in the new libkml.

I'll patch the gdal build to properly support the new libkml builds too,
after we get the transition moving to not have to update the symbols
again. Although these additions should be fine, as they won't require a
package rename.

As also mentioned in the geos issue, since geos is a build dependency of
gdal, I think it's better to update geos in unstable first and start the
gdal transition as part of that. We can probably limit the dependency
dance to untangle the spatialite->postgis->gdal->spatialite circular
dependency to a single pass. With that in mind I propose the following:

 * Upload geos (3.5.0-1) to unstable to start its transition (#791045)

 * Upload spatialite (4.3.0-2) to unstable, drops liblwgeom dependency

 * File RC bug on spatialite (4.3.0-2) about liblwgeom regression to
   prevent testing migration, and have the RC bug block the geos & gdal
   transition bugs (#791045, #756867).

 * Upload gdal (1.11.2+dfsg-1) to unstable to start its transition
    - built with spatialite (4.3.0-2) via versioned build dependency

 * BinNMU postgis with rebuilt gdal & spatialite in unstable

 * Upload spatialite (4.3.0-3) to unstable, reinstates liblwgeom
   dependency

 * BinNMU gdal with spatialite (4.3.0-3) in unstable

 * BinNMU postgis with rebuilt gdal & spatialite in unstable

The BinNMUs can also be substituted with an upload in which the
versioned build dependencies get bumped.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1


Reply to: