Hi,
On Sat, Oct 7, 2023 at 9:36 PM Boyuan Yang <[email protected]> wrote: > > X-Debbugs-CC: [email protected] > > 在 2023-10-07星期六的 20:32 +0200，Sebastian Ramacher写道： > > Control: tags -1 confirmed > > > > On 2023-10-07 14:06:44 -0400, Boyuan Yang wrote: > > > 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)). > > > > > > * jpeg-xl (Current version FTBFS unconditionally due to a different reason > > > in Testing/Sid; my NMU fix just accepted in Sid) > > > > > > Do we need to wait till my NMU-ed jpeg-xl to migrate to Testing before > > > starting the libavif transition? > > > > No, that's not necessary. Please go ahead. > > Alright, here comes the tricky part. > > In the test build of reverse build-dependencies, only amd64 builds are > examined. > Now, the rebuilt jpeg-xl has some new FTBFS on other architectures; and while > some > issues are easy to solve (e.g., missing <cmath> header for arm64), some > issues are > not (like the new test failures for i386 and s390x) [1]. > > Probably I uploaded the libavif/1.0.1-1 to Sid too soon; and while I tried to > cancel > the upload with "dcut rm" and "dcut cancel", these commands never successfully > intercept the upload ("no such upload found", "no file to delete", etc), and > we are > having the new libavif in Sid now to trigger the transition. This is the worst > condition we could have, though I consciously tried to avoid it :-( > > I am now wondering what would be the best way to get this transition done in > a sane > way. A few choices in my mind: > > (1) Make a sloppy upload to jpeg-xl in Sid to ignore post-build testing > errors (and > possibly newly-emerged autopkgtest errors, if any?) so that the libavif > transition can > finish, and count on the upcoming jpeg-xl (0.7 -> 0.8) transition to correct > these > ignored errors; > > (2) Fix current jpeg-xl in Sid properly. That won't be too trivial since the > new > testing error is likely triggered by some unclear changes in > build-dependencies over > the past several months. > > (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. Thanks, > It would be great if you have any suggestion, or even better, some good > patches > on it. > > Thanks, > Boyuan Yang > > > [1] https://buildd.debian.org/status/package.php?p=jpeg-xl
