Your message dated Sun, 8 May 2022 00:12:02 +0200 with message-id <YnbushpHh0gjlEmc@ramacher.at> and subject line Re: Bug#1010460: transition: libavif has caused the Debian Bug report #1010460, 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.) -- 1010460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010460 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: transition: libavif
- From: Boyuan Yang <byang@debian.org>
- Date: Sun, 01 May 2022 21:09:30 -0400
- Message-id: <[🔎] 9e628fe6e90be46bdf7a5b68a4929c27b7ec4dd4.camel@debian.org>
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 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. Reverse dependencies include kimageformats and swayimg, 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 ~ "libavif13" | .depends ~ "libavif14"; is_good = .depends ~ "libavif14"; is_bad = .depends ~ "libavif13"; This would be a really tiny transition, and I expect that we can finish it very quickly with binNMUs. Thanks, Boyuan YangAttachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
- To: Boyuan Yang <byang@debian.org>, 1010460-done@bugs.debian.org
- Subject: Re: Bug#1010460: transition: libavif
- From: Sebastian Ramacher <sramacher@debian.org>
- Date: Sun, 8 May 2022 00:12:02 +0200
- Message-id: <YnbushpHh0gjlEmc@ramacher.at>
- In-reply-to: <[🔎] Ym+ZnAUe4NhXN8GA@ramacher.at>
- References: <[🔎] 9e628fe6e90be46bdf7a5b68a4929c27b7ec4dd4.camel@debian.org> <[🔎] 9e628fe6e90be46bdf7a5b68a4929c27b7ec4dd4.camel@debian.org> <[🔎] Ym+ZnAUe4NhXN8GA@ramacher.at>
On 2022-05-02 10:43:08 +0200, Sebastian Ramacher wrote: > Control: tags -1 confirmed > Control: forwarded -1 https://release.debian.org/transitions/html/auto-libavif.html > > On 2022-05-01 21:09:30, 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 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. > > Reverse dependencies include kimageformats and swayimg, 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 ~ "libavif13" | .depends ~ "libavif14"; > > is_good = .depends ~ "libavif14"; > > is_bad = .depends ~ "libavif13"; > > > > This would be a really tiny transition, and I expect that we can finish it > > very quickly with binNMUs. > > Please go ahead … and the old packages just got removed from testing. Closing Cheers -- Sebastian Ramacher
--- End Message ---