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

Bug#968378: marked as done (transition: libraw)

Your message dated Thu, 15 Oct 2020 22:30:28 +0200
with message-id <20201015203028.GD1708055@ramacher.at>
and subject line Re: Bug#968378: transition: libraw
has caused the Debian Bug report #968378,
regarding transition: libraw
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.)


-- 
968378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968378
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

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.

Thanks for your time and patience.

mfv


[1] https://release.debian.org/transitions/html/auto-libraw.html


Ben file:

title = "libraw";
is_affected = .depends ~ "libraw19" | .depends ~ "libraw20";
is_good = .depends ~ "libraw20";
is_bad = .depends ~ "libraw19";


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On 2020-08-14 00:12:56 +0200, 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.

This transition finished a while ago.

Cheers

> 
> 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.
> 
> Thanks for your time and patience.
> 
> mfv
> 
> 
> [1] https://release.debian.org/transitions/html/auto-libraw.html
> 
> 
> Ben file:
> 
> title = "libraw";
> is_affected = .depends ~ "libraw19" | .depends ~ "libraw20";
> is_good = .depends ~ "libraw20";
> is_bad = .depends ~ "libraw19";
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads)
> Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> -- 
> Matteo F. Vescovi || Debian Developer
> GnuPG KeyID: 4096R/0x8062398983B2CF7A



-- 
Sebastian Ramacher

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: