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

Bug#1053641: marked as done (transition: libavif)

Your message dated Fri, 15 Dec 2023 23:11:45 +0100
with message-id <ZXzPIXyQL4EVLVuU@ramacher.at>
and subject line Re: Bug#1053641: transition: libavif
has caused the Debian Bug report #1053641,
regarding transition: libavif
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.)


-- 
1053641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053641
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Control: affects -1 + src:libavif
X-Debbugs-Cc: libavif@packages.debian.org malat@debian.org
User: release.debian.org@packages.debian.org
Usertags: transition
X-Debbugs-Cc: byang@debian.org
Severity: normal

I am looking at starting the transition for package libavif,
which comes with a SONAME bump
(libavif15, v0.11.1-3 (sid) -> libavif16, v1.0.1-1 (exp)).

I tried with the rebuild of all packages on the transition page:

Level 1:

* libavif (OK)

Level 2:

* jpeg-xl (Current version FTBFS unconditionally due to a different reason
in Testing/Sid; my NMU fix just accepted in Sid)
* libgd2 (OK)
* links2 (OK)
* qt-avif-image-plugin (OK)

Level 3:

* darktable (OK)
* kimageformats (OK)
* webkit2gtk (OK)
* wpewebkit (OK)


Do we need to wait till my NMU-ed jpeg-xl to migrate to Testing before
starting the libavif transition?

(jpeg-xl package maintainer added in the CC list.)

Ben file:

(The current autogenerated transition page
https://release.debian.org/transitions/html/auto-libavif.html can
be reused.)

title = "libavif";
is_affected = .depends ~ "libavif15" | .depends ~ "libavif16";
is_good = .depends ~ "libavif16";
is_bad = .depends ~ "libavif15";

Thanks,
Boyuan Yang

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message --- 
On 2023-12-15 14:57:38 -0500, Boyuan Yang wrote:
> X-Debbugs-CC: sramacher@debian.org malat@debian.org
> 
> On Sun, 8 Oct 2023 09:57:21 +0200 Paul Gevers <elbrus@debian.org> wrote:
> > Hi Mathieu,
> > 
> > On 08-10-2023 09:46, Mathieu Malaterre wrote:
> > >> (3) Wait till a sane jpeg-xl 0.8 upload (with transition) is ready, and entangle
> > >> jpeg-xl transition with libavif transition.
> > > 
> > > #1051131 has been fixed yesterday. I'll go ahead and do the 0.8 upload
> > > this week.
> > 
> > Please wait with that until Sebastian approves. We normally don't want 
> > transitions to be entangled. An upload to experimental is fine of course 
> > to clear the NEW queue.
> 
> Just to let you know that I took the liberty to handle the blocker from src:darktable
> via NMU, and now the libavif transition should have finished and no longer being a
> blocker to other transitions. Maybe we should close bug 1053641 and handle other stalled
> transitions (like jpeg-xl).

Thanks, with the old binaries finally removed from testing, let's close
this one.

Cheers
-- 
Sebastian Ramacher

--- End Message ---
Reply to: