Bug#813916: transition: gdal
On 12-02-16 19:05, Emilio Pozuelo Monfort wrote:
> On 12/02/16 18:52, Sebastiaan Couwenberg wrote:
>> On 12-02-16 18:28, Emilio Pozuelo Monfort wrote:
>>> On 06/02/16 17:43, Bas Couwenberg wrote:
>>>> Package: release.debian.org
>>>> For the Debian GIS team I'd like to transition to the recently released
>>>> GDAL 1.11.4. Only the packages using C++ symbols need to be rebuilt.
>>>>
>>>> GDAL 2.0.2 was released along with 1.11.4, but we still don't have
>>>> support for GDAL 2.0 in all reverse dependencies. Since the transition
>>>> to GDAL 1.11.3, support for GDAL 2.0 was added to all reverse
>>>> depedencies except Fiona [0]. Upstream has recently included changes for
>>>> GDAL 2.0, but these differ from the initial GDAL 2.0 changes available
>>>> as a patch in #802808. The improved GDAL 2.0 changes are entangled with
>>>> other changes for the upcoming Fiona 1.7 release, which I've not been
>>>> able to successfully backport. This will not be a blocker for the GDAL
>>>> 2.0 transition, as discussed with the maintainer on the debian-gis list
>>>> [1].
>>>>
>>>> Because the transition for GDAL 1.11.4 is ready now, I'd like to do that
>>>> first before preparing the transition to GDAL 2.0. All reverse
>>>> dependencies rebuilt successfully with GDAL 1.11.4, the summary of
>>>> rebuilds is included below.
>>>>
>>>
>>> This would get entangled with the openmpi transition, so it will have to wait.
>>> After openmpi, I'm thinking about doing libpng, but we'll see.
>>
>> Waiting for openmpi is no problem, but if the libpng transition is going
>> to happen first, I think it's better to use that time the prepare the
>> transition to GDAL 2.0 instead of 1.11.4. Last week the last blocker was
>> resolved [0], so we're also pretty much ready to transition to GDAL 2.0.
>> The 2.0 packages will have to pass the NEW queue again, because of the
>> delay that will cause I've opted to transition to 1.11.4 which is ready now.
>>
>> If you can confirm that the libpng transition is going to happen first,
>> I'll upload the packages for GDAL 2.0 to experimental, and we can switch
>> to that in unstable after the libpng transition and the new gdal has
>> passed NEW.
>
> Sure, let's do that.
The GDAL 2.0.2 packages are available in experimental and ready for
transition.
libgdal-grass (2.0.2-1) not available in experimental yet, liblas and
grass need to be rebuilt with GDAL 2.0 before it can be built too,
because the SOVERSION is included in the binary package it builds the
package will have to pass the NEW queue after upload first. To get it
passed the NEW queue, I'll rebuild liblas & grass with gdal
(2.0.2-1-1~exp2) from experimental and upload all three to experimental too.
All reverse dependencies build successfully with GDAL 2.0.
Transition: gdal
libgdal1i (1.11.3+dfsg-3) -> libgdal20 (2.0.2+dfsg-1)
libgdal.so.1-1.11.3 -> gdal-abi-2-0-2
The status of the most recent rebuilds is as follows.
dans-gdal-scripts (0.23-4) OK
fiona (1.6.3-2) OK
gazebo (6.5.0+dfsg-2) OK
gmt (5.2.1+dfsg-3) OK
imposm (2.6.0+ds-2) OK
libcitygml (2.0-1) OK
liblas (1.8.0-7) OK
libosmium (2.6.0-1) OK
mapcache (1.4.0-4) OK
mapnik (3.0.9+ds-1) OK
mapserver (7.0.0-9) OK
merkaartor (0.18.2-5) OK
mysql-workbench (6.3.4+dfsg-3) OK
ncl (6.3.0-6) OK
node-srs (0.4.8+dfsg-2) OK
openscenegraph (3.2.1-9) OK
osmium (0.0~20160124-b30afd3-1) OK
osrm (4.9.1+ds-1~exp2) OK
postgis (2.2.1+dfsg-2) OK
pprepair (0.0~20150624-82a2019-1) OK
prepair (0.7-4) OK
qlandkartegt (1.8.1+ds-4) OK
qmapshack (1.5.1-1) OK
rasterio (0.31.0-2) OK
saga (2.2.3+dfsg-1) OK
sumo (0.25.0+dfsg1-2) OK
thuban (1.2.2-9) OK
vtk6 (6.2.0+dfsg1-7) OK
xastir (2.0.6-4) OK
grass (7.0.3-1) OK
osgearth (2.5.0+dfsg-8 / 2.7.0+dfsg-1~exp5) OK / OK
osmcoastline (2.1.2-1) OK
pktools (2.6.6-1) OK
pyosmium (2.6.0-1) OK
libgdal-grass (1.11.3-3 / 2.0.2-1) FTBFS / OK
qgis (2.8.6+dfsg-1) OK
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Reply to: