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

Bug#898566: marked as done (transition: gdal)



Your message dated Mon, 28 May 2018 13:07:20 +0200
with message-id <05485c70-40ec-0a4c-6745-299aff5f04f4@debian.org>
and subject line Re: Bug#898566: transition: gdal
has caused the Debian Bug report #898566,
regarding transition: gdal
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
898566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898566
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
Control: block -1 by 896577

For the Debian GIS team I'd like to transition to GDAL 2.3.0.

Like the previous transition to GDAL 2.2.3 (#884504), 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.3.0 from
experimental as summarized below, except mysql-workbench. It does build
successfully with the patch from #896577.

libgdal-grass doesn't need a binNMU as the 2.3.0 version will be
uploaded to unstable instead. liblas likewise doesn't need a binNMU,
the version is experimental will be moved to unstable instead.


Ben file:

title = "gdal";
is_affected = .depends ~ "gdal-abi-2-2-3" | .depends ~ "gdal-abi-2-3-0";
is_good = .depends ~ "gdal-abi-2-3-0";
is_bad = .depends ~ "gdal-abi-2-2-3";


Transition: gdal

 libgdal20 (2.2.4+dfsg-1) -> libgdal20 (2.3.0+dfsg-1~exp1)
 gdal-abi-2-2-3           -> gdal-abi-2-3-0

The status of the most recent rebuilds is as follows.

 dans-gdal-scripts       (0.24-1)                       OK
 fiona                   (1.7.11-2)                     OK
 gazebo                  (9.0.0+dfsg5-4)                OK
 gmt                     (5.4.3+dfsg-1)                 SKIP (no C++)
 imposm                  (2.6.0+ds-4)                   SKIP (no C++)
 libcitygml              (2.0.9-1)                      OK
 liblas                  (1.8.1-6 / 1.8.1-7~exp2)       FTBFS / OK
 libosmium               (2.14.0-1)                     SKIP (no C++)
 mapcache                (1.6.1-1)                      SKIP (no C++)
 mapnik                  (3.0.20+ds-1)                  OK
 mapproxy                (1.11.0-1)                     SKIP (no C++)
 mapserver               (7.0.7-1)                      SKIP (no C++)
 merkaartor              (0.18.3+ds-3)                  OK
 mysql-workbench         (6.3.10+dfsg-2)                OK [+] (#896577)
 ncl                     (6.4.0-9)                      SKIP (no C++)
 node-srs                (0.4.8+dfsg-3)                 OK
 octave-mapping          (1.2.1-3)                      OK
 openorienteering-mapper (0.8.1.1-1)                    SKIP (no C++)
 openscenegraph          (3.2.3+dfsg1-2)                OK
 pdal                    (1.7.1-1)                      OK
 pgsql-ogr-fdw           (1.0.5-2)                      SKIP (no C++)
 postgis                 (2.4.4+dfsg-1)                 SKIP (no C++)
 pprepair                (0.0~20170614-dd91a21-1)       OK
 prepair                 (0.7.1-1)                      OK
 python-django           (1:1.11.13-1)                  SKIP (no C++)
 qlandkartegt            (1.8.1+ds-8)                   OK
 qmapshack               (1.11.1-1)                     OK
 rasterio                (0.36.0-2)                     OK
 sumo                    (0.32.0+dfsg1-1)               OK
 thuban                  (1.2.2-12)                     OK
 vtk6                    (6.3.0+dfsg2-2)                OK
 vtk7                    (7.1.1+dfsg1-4)                OK
 xastir                  (2.1.0-1)                      SKIP (no C++)

 cloudcompare            (2.9.1+git20180223-1)          SKIP (no C++)
 grass                   (7.4.0-1)                      SKIP (no C++)
 opencv                  (3.2.0+dfsg-4)                 OK
 openscenegraph-3.4      (3.4.1+dfsg1-3)                OK
 osmcoastline            (2.1.4-2)                      OK
 pktools                 (2.6.7.3+ds-2)                 OK
 pyosmium                (2.14.1-1)                     SKIP (no C++)

 libgdal-grass           (2.2.4-1 / 2.3.0-1~exp1)       FTBFS / OK
 osgearth                (2.9.0+dfsg-1)                 OK
 otb                     (6.4.0+dfsg-2)                 OK
 qgis                    (2.18.19+dfsg-1)               OK
 saga                    (2.3.1+dfsg-3)                 OK


Kind Regards,

Bas

--- End Message ---
--- Begin Message ---
On 27/05/18 09:09, Sebastiaan Couwenberg wrote:
> On 05/26/2018 10:24 AM, Sebastiaan Couwenberg wrote:
>> On 05/25/2018 07:37 AM, Sebastiaan Couwenberg wrote:
>>> On 05/24/2018 09:44 PM, Sebastiaan Couwenberg wrote:
>>>> On 05/24/2018 06:26 PM, Emilio Pozuelo Monfort wrote:
>>>>> On 23/05/18 07:15, Sebastiaan Couwenberg wrote:
>>>>>> On 05/22/2018 10:19 PM, Emilio Pozuelo Monfort wrote:
>>>>>>> On 22/05/18 18:10, Sebastiaan Couwenberg wrote:
>>>>>>>> On 05/18/2018 02:49 PM, Emilio Pozuelo Monfort wrote:
>>>>>>>>> On 13/05/18 18:48, Bas Couwenberg wrote:
>>>>>>>>>> Package: release.debian.org
>>>>>>>>>> Severity: normal
>>>>>>>>>> User: release.debian.org@packages.debian.org
>>>>>>>>>> Usertags: transition
>>>>>>>>>> Control: block -1 by 896577
>>>>>>>>>>
>>>>>>>>>> For the Debian GIS team I'd like to transition to GDAL 2.3.0.
>>>>>>>>>>
>>>>>>>>>> Like the previous transition to GDAL 2.2.3 (#884504), 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.3.0 from
>>>>>>>>>> experimental as summarized below, except mysql-workbench. It does build
>>>>>>>>>> successfully with the patch from #896577.
>>>>>>>>>>
>>>>>>>>>> libgdal-grass doesn't need a binNMU as the 2.3.0 version will be
>>>>>>>>>> uploaded to unstable instead. liblas likewise doesn't need a binNMU,
>>>>>>>>>> the version is experimental will be moved to unstable instead.
>>>>>>>>>
>>>>>>>>> Let's wait for icu to migrate to testing, at the very least.
>>>>>>>>
>>>>>>>> The new icu is now in testing. Can we start the gdal transition soonish,
>>>>>>>> or if not, can you binNMU mapnik to build with the new boost? People are
>>>>>>>> complaining about the inability to install libmapnik3.0.
>>>>>>>
>>>>>>> binNMU scheduled now. I will check that it migrates to testing.
>>>>>>>
>>>>>>> As for the transition, I may schedule curl first now if it's ready. I need to
>>>>>>> look at that.
>>>>>>
>>>>>> Thanks, that should alleviate the problems with mapnik in the mean time.
>>>>>
>>>>> Actually go ahead with the transition. The only conflict between this and curl
>>>>> is gazebo, and worst case if the transitions get entangled we can temporarily
>>>>> remove that from testing (though I'll try to avoid that).
>>>>
>>>> Thanks for the go ahead.
>>>>
>>>> gdal (2.3.0+dfsg-1), liblas (1.8.1-7) & libgdal-grass (2.3.0-1) have all
>>>> been uploaded to unstable.
>>>
>>> And they're now also built & installed on all release architectures.
>>
>> The binNMUs in unstable are looking good so far. As usual the vtk
>> packages haven't finished building on all architectures yet.
> 
> Everything that can be built, has been built.
> 
> Now we only need a fix for #898776 to allow the new python-numpy and its
> reverse dependencies to migrate to testing.
> 
> Perhaps the porters can be of help there.

Since you lowered the severity, gdal was able to migrate to testing, finishing
the transition.

Cheers,
Emilio

--- End Message ---

Reply to: