Bug#998148: transition: libavif

2021-11-02 Thread Sebastian Ramacher 
On 2021-11-02 21:22:35, Norbert Preining wrote:
> Hi Boyuan
> 
> 
> > I plan to start another libavif transition as shown in the following
> 
> Great, actually it would be great going straight to 0.9.3-2 with libaom v3
> support, so that writing of avif files also works.

For the future: we prefer to not entangle transitions in general and
especially when they have already been started. Please let us know
before uploading if you want to entangle them.

And the general recommendation for all packages involved in a transition
still applies: please only upload if the upload is required to finish a
transition - otherwise wait until its done.

Best
Sebastian
-- 
Sebastian Ramacher

Bug#998148: transition: libavif

2021-11-02 Thread Norbert Preining 
Hi Boyuan


> I plan to start another libavif transition as shown in the following

Great, actually it would be great going straight to 0.9.3-2 with libaom v3
support, so that writing of avif files also works.

Thanks a lot for your work on this.

All the best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#998148: transition: libavif

2021-10-31 Thread Sebastian Ramacher 
Control: tags -1 confirmed

On 2021-10-30 20:11:43, Boyuan Yang wrote:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-CC: by...@debian.org norb...@preining.info
> 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 (libavif/0.9.3) has bumped SONAME and needs
> a transition. The only reverse build-dependency is kimageformats, and I have
> verified that the build would still pass with the new libavif currently in
> experimental.

Please go ahead

Cheers

> 
> Example Ben file (the one currently on auto-libavif page should be ok):
> 
> title = "libavif";
> is_affected = .depends ~ "libavif12" | .depends ~ "libavif13";
> is_good = .depends ~ "libavif13";
> is_bad = .depends ~ "libavif12";
> 
> This would be an identical transition as https://bugs.debian.org/992316 , and
> I expect that only binNMUs would be involved, just like in last time.
> 
> Thanks,
> Boyuan Yang



-- 
Sebastian Ramacher

Processed: Re: Bug#998148: transition: libavif

2021-10-31 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 confirmed
Bug #998148 [release.debian.org] transition: libavif
Added tag(s) confirmed.

-- 
998148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#998148: transition: libavif

2021-10-30 Thread Boyuan Yang 
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-CC: by...@debian.org norb...@preining.info
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 (libavif/0.9.3) has bumped SONAME and needs
a transition. The only reverse build-dependency is kimageformats, 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 ~ "libavif12" | .depends ~ "libavif13";
is_good = .depends ~ "libavif13";
is_bad = .depends ~ "libavif12";

This would be an identical transition as https://bugs.debian.org/992316 , and
I expect that only binNMUs would be involved, just like in last time.

Thanks,
Boyuan Yang


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