Package: release.debian.org Control: affects -1 + src:libavif X-Debbugs-Cc: libavif@packages.debian.org malat@debian.org User: release.debian.org@packages.debian.org Usertags: transition X-Debbugs-Cc: byang@debian.org Severity: normal 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)). I tried with the rebuild of all packages on the transition page: Level 1: * libavif (OK) Level 2: * jpeg-xl (Current version FTBFS unconditionally due to a different reason in Testing/Sid; my NMU fix just accepted in Sid) * libgd2 (OK) * links2 (OK) * qt-avif-image-plugin (OK) Level 3: * darktable (OK) * kimageformats (OK) * webkit2gtk (OK) * wpewebkit (OK) Do we need to wait till my NMU-ed jpeg-xl to migrate to Testing before starting the libavif transition? (jpeg-xl package maintainer added in the CC list.) Ben file: (The current autogenerated transition page https://release.debian.org/transitions/html/auto-libavif.html can be reused.) title = "libavif"; is_affected = .depends ~ "libavif15" | .depends ~ "libavif16"; is_good = .depends ~ "libavif16"; is_bad = .depends ~ "libavif15"; Thanks, Boyuan Yang
Attachment:
signature.asc
Description: This is a digitally signed message part