Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: transition
Dear Release Team, I'm filing this bug for a new transition of libraw package. On June 29, 2018 the 0.19.0 stable version has been released by upstream. On July 23 and 26, 2018 a couple of testing-purpose packages has been uploaded to experimental, the first as first 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_1.2.23-1 => OK * efl_1.20.7-6 => OK * entangle_0.7.2-1 => OK * fotoxx_18.01.1-2 => OK * freeimage_3.17.0+ds1-5 => OK * gegl_0.4.2-1 => OK * gthumb_3:3.6.1-1 => OK * krita_1:4.1.1+dfsg-1 => FTBFS * kstars_5:2.9.6-1 => FTBFS * libkf5kdcraw_17.08.3-1 => FTBFS * luminance-hdr_2.5.1+dfsg-3 => OK * nomacs_3.10.2+dfsg-1 => OK * openimageio_1.8.12~dfsg0-1 => OK * shotwell_0.28.3-1 => OK * siril_0.9.9-1 => OK All the FTBFS (3) are caused by some changes in libraw 0.19.0 compared to older 0.18.xx version. Thanks for your time and patience. [1] https://release.debian.org/transitions/html/auto-libraw.html Ben file: title = "libraw"; is_affected = .depends ~ "libraw16" | .depends ~ "libraw19"; is_good = .depends ~ "libraw19"; is_bad = .depends ~ "libraw16"; -- System Information: Debian Release: buster/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
signature.asc
Description: PGP signature
