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

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

Your message dated Sun, 04 Dec 2022 12:54:25 -0500
with message-id <23c93d5552b84b2c4f9f5c586b677c7283fa0afe.camel@debian.org>
and subject line Re: Bug#1022064: transition: libavif
has caused the Debian Bug report #1022064,
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.)


-- 
1022064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022064
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: transition
X-Debbugs-CC: byang@debian.org
Severity: normal

I plan to start yet another libavif transition as shown in the following
transition tracker:

https://release.debian.org/transitions/html/auto-libavif.html

The new version of libavif library has bumped SONAME and needs a transition.
The only reverse build-dependencies are kimageformats and jpeg-xl, and I have
verified that the build would still pass with the new libavif currently in
experimental.

Example Ben file (the one currently on auto-libavif page should be ok):

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

This would be a really tiny transition, and I expect that we can finish it
very soon once there are no transition entanglements (gcc-12, perl-5.26).

Thanks,
Boyuan Yang

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


--- End Message ---
--- Begin Message --- 
X-Debbugs-CC: sramacher@debian.org

Hi,

I believe this transition is finished already so closing the bug. Let me
know if there are any other issues.

Thanks,
Boyuan Yang


On Wed, 19 Oct 2022 18:34:30 +0200 Sebastian Ramacher <sramacher@debian.org>
wrote:
> Control: tags -1 confirmed
> 
> On 2022-10-19 12:06:24 -0400, Boyuan Yang wrote:
> > Package: release.debian.org
> > User: release.debian.org@packages.debian.org
> > Usertags: transition
> > X-Debbugs-CC: byang@debian.org
> > Severity: normal
> > 
> > I plan to start yet another libavif transition as shown in the following
> > transition tracker:
> > 
> > https://release.debian.org/transitions/html/auto-libavif.html
> > 
> > The new version of libavif library has bumped SONAME and needs a
transition.
> > The only reverse build-dependencies are kimageformats and jpeg-xl, and I
have
> > verified that the build would still pass with the new libavif currently
in
> > experimental.
> > 
> > Example Ben file (the one currently on auto-libavif page should be ok):
> > 
> > title = "libavif";
> > is_affected = .depends ~ "libavif14" | .depends ~ "libavif15";
> > is_good = .depends ~ "libavif15";
> > is_bad = .depends ~ "libavif14";
> > 
> > This would be a really tiny transition, and I expect that we can finish
it
> > very soon once there are no transition entanglements (gcc-12, perl-
5.26).
> 
> While binNMUs might take a bit longer to be done, neither of those two
> should be entangled. So please go ahead.
> 
> Cheers
> -- 
> Sebastian Ramacher
> 
>

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


--- End Message ---
Reply to: