Your message dated Fri, 3 Dec 2021 08:55:21 +0100
with message-id <yannaa2bbrj4p...@ramacher.at>
and subject line Re: Bug#997917: transition: aom
has caused the Debian Bug report #997917,
regarding transition: aom
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 ow...@bugs.debian.org
immediately.)
--
997917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian....@packages.debian.org
Usertags: transition
X-Debbugs-CC: by...@debian.org debian-multime...@lists.debian.org
Severity: normal
Dear Debian Release Team,
I plan to start libaom transition as shown on the following transition
tracker:
https://release.debian.org/transitions/html/auto-aom.html
The new version of libaom library has bumped SONAME (libaom0 -> libaom3) and
needs a transition.
There are 3 reverse build-dependencies, and I have verified that
the build would still pass with the new libaom currently in experimental:
* ffmpeg (ok)
* libheif (ok)
* gst-plugins-bad1.0 (ok)
Example Ben file (the one currently on auto-aom page should be ok):
title = "aom";
is_affected = .depends ~ "libaom3" | .depends ~ "libaom0";
is_good = .depends ~ "libaom3";
is_bad = .depends ~ "libaom0";
I expect it to be a smooth transition that only involves binNMUs. Please let
me know if there are any concerns.
Thanks,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
On 2021-11-01 23:06:55 +0100, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> Control: forwarded -1
> https://release.debian.org/transitions/html/auto-aom.html
>
> On 2021-10-27 01:54:28 -0400, Boyuan Yang wrote:
> > Package: release.debian.org
> > User: release.debian....@packages.debian.org
> > Usertags: transition
> > X-Debbugs-CC: by...@debian.org debian-multime...@lists.debian.org
> > Severity: normal
> >
> > Dear Debian Release Team,
> >
> > I plan to start libaom transition as shown on the following transition
> > tracker:
> >
> >
> > https://release.debian.org/transitions/html/auto-aom.html
> >
> > The new version of libaom library has bumped SONAME (libaom0 -> libaom3) and
> > needs a transition.
> >
> > There are 3 reverse build-dependencies, and I have verified that
> > the build would still pass with the new libaom currently in experimental:
> >
> > * ffmpeg (ok)
> > * libheif (ok)
> > * gst-plugins-bad1.0 (ok)
> >
> > Example Ben file (the one currently on auto-aom page should be ok):
> >
> > title = "aom";
> > is_affected = .depends ~ "libaom3" | .depends ~ "libaom0";
> > is_good = .depends ~ "libaom3";
> > is_bad = .depends ~ "libaom0";
> >
> > I expect it to be a smooth transition that only involves binNMUs. Please let
> > me know if there are any concerns.
>
> Please go ahead
libaom0 got removed from testing.
Cheers
>
> Cheers
>
> >
> > Thanks,
> > Boyuan Yang
>
>
>
> --
> Sebastian Ramacher
--
Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
