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

Bug#917323: transition: gdal



On 02/01/2019 21:10, Sebastiaan Couwenberg wrote:
> On 1/2/19 12:55 PM, Emilio Pozuelo Monfort wrote:
>> On 26/12/2018 08:46, Bas Couwenberg wrote:
>>> Package: release.debian.org
>>> Severity: normal
>>> User: release.debian.org@packages.debian.org
>>> Usertags: transition
>>>
>>> For the Debian GIS team I'd like to transition to GDAL 2.4.0.
>>>
>>> Like the previous transition to GDAL 2.3.0 (#898566), 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.4.0 from
>>> experimental as summarized below, except mysql-workbench due to an
>>> unrelated issue (#914761).
>>>
>>> libgdal-grass doesn't need a binNMU as the 2.4.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.
>>
>> Go ahead.
> 
> Thanks.
> 
> gdal (2.4.0+dfsg-1), liblas (1.8.1-9) & libgdal-grass (2.4.0-1) have
> been uploaded to unstable, and gdal (2.4.0+dfsg-1) is now installed on
> all release architectures.

Looks like the rebuilt gazebo fails its autopkgtest due to a broken gazebo.pc,
see #918121. That causes migration delays for gdal. No idea where the broken
flag is coming from, I haven't investigated that deep.

Cheers,
Emilio


Reply to: