On 07/10/2017 05:45 PM, Emilio Pozuelo Monfort wrote:
> On 04/07/17 21:43, Emilio Pozuelo Monfort wrote:
>> On 01/07/17 21:17, Bas Couwenberg wrote:
>>> For the Debian GIS team I'd like to transition to GDAL 2.2.1.
>>>
>>> Like the previous transition to GDAL 2.1.2 (#842288), there is no SONAME
>>> bump, only the virtual ABI package changed to account for the C++ symbol
>>> changes.
>>>
>>> All reverse dependencies rebuilt successfully with GDAL 2.2.1 from
>>> experimental as summarized below, except rasterio & vtk6.
>>>
>>> rasterio cannot be built yet because python-numpy hasn't been built with
>>> Python 3.6 yet as part of the python3-defaults transition (#866335).
>>> rasterio built successfully with Python 3.5 and GDAL 2.2.1~rc1, so this
>>> will likely be resolved with the rebuild of python-numpy.
>>>
>>> vtk6 FTBFS due to missing build dependencies: texlive-math-extra.
>>> The recent texlive-extra source packages no longer build with binary
>>> package. Dropping the build dependency was sufficient to build vtk6
>>> successfully with GDAL 2.2.1. The patch has been submitted in #866723.
>>>
>>> A new revision of qgis has been uploaded to unstable which includes the
>>> changes from 2.14.16 (currently in NEW) for GDAL 2.2 support, which
>>> allow the package the build successfully with GDAL 2.2.1 too.
>>>
>>>
>>> libgdal-grass doesn't need a binNMU as the 2.2.1 version will be
>>> uploaded to unstable instead. liblas likewise doesn't need a binNMU,
>>> the version is experimental will be moved to unstable instead.
>>>
>>> Please also binNMU mapnik in experimental as part of the transition.
>>
>> Let's wait a bit for this, I want the octave transition to finish
>> first (and to make sure the python3.6 one won't be a problem). In
>> the meantime you can get vtk6 fixed and qgis accepted.
> 
> octave is in and the python transition shouldn't be a problem anymore, so 
> please
> go ahead if you're ready to do the necessary NMUs.

Thanks, gdal (2.2.1+dfsg-1), liblas (1.8.1-4) & libgdal-grass (2.2.1-1)
have been uploaded to unstable.

Hopefully no NMUs will be necessary. vtk6 has been fixed, but has not
migrated to testing yet. None of the other packages had issues when the
rebuilds were performed, if anything has cropped up since then I'll have
a go at fixing that.

Kind Regards,

Bas

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

Reply via email to