Bug#968378: transition: libraw

[Emilio Pozuelo Monfort <pochu@debian.org>]

Control: tags -1 confirmed

On 14/08/2020 00:12, Matteo F. Vescovi wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: transition
> 
> Dear Release Team,
> 
> I'm filing this bug for a new transition of libraw package.
> 
> On July 23, 2020 the 0.20.0 stable version has been released by
> upstream.
> 
> On August 04, 2020, after initial upload to experimental accepted by FTP
> Masters, a couple of testing-purpose packages has been uploaded to
> experimental, the first as first-hand attempt to check the packaging on
> all architectures, the latter to fix a bunch of FTBFS due to C++
> symbols.
> 
> So, following the auto-libraw checklist[1], here is the list of source
> packages reverse-depending on libraw and the results of the builds:
> 
>  * deepin-image-viewer_5.0.0-1 => OK
>  * efl_1.24.3-5 => OK
>  * entangle_3.0-1 => OK
>  * fotoxx_20.08-1 => OK
>  * freeimage_3.18.0+ds2-5 => FTBFS (possibly LibRaw-related)
>  * gegl_0.4.24-1 => OK
>  * gthumb_3:3.8.0-2.1 => OK
>  * hdrmerge_0.5+git20200117-2 => OK
>  * krita_1:4.3.0+dfsg-1 => OK
>  * kstars_5:3.4.3-1 => OK
>  * libkf5kdcraw_20.04.3-1 => OK
>  * luminance-hdr_2.6.0+dfsg-2 => OK
>  * nomacs_3.12.0+dfsg-3 => OK
>  * openimageio_2.1.18.1~dfsg0-1 => OK
>  * shotwell_0.30.10-1 => OK
>  * siril_0.9.12-3 => OK
>  * theli_3.0.2-1.1 => FTBFS (possibly LibRaw-related)
> 
> Both FTBFS seem to be caused by some changes in libraw 0.20.0 compared
> to older 0.19.x version.

Please go ahead, and file bugs for those FTBFS.

Cheers,
Emilio