Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: transition X-Debbugs-Cc: lib...@packages.debian.org, Ondřej Surý <ond...@debian.org> Control: affects -1 + src:libzip
Dear Release Team, please grant a transition slot for the libzip transition. Upstream has changed the soname from 4 to 5 quite a while ago, but until now that had been reverted in the Debian packaging, cf. https://sources.debian.org/src/libzip/1.7.3-1.1/debian/patches/0001-Reintroduce-dummy-zip_archive_set_tempdir-function-t.patch/ https://tracker.debian.org/news/1023453/accepted-libzip-151-2-source-into-experimental/ https://tracker.debian.org/news/1122959/accepted-libzip-161-3-source-into-unstable/ However, the libzip packaging has now been adjusted to reflect this. For reference, according to upstream the dropped symbol was never fully implemented or documented, and they are not aware of any software ever using it. (They had private software where they thought it might be useful, but then never needed it.) In Debian, that symbol is only referenced in code copies of libzip, cf. https://codesearch.debian.net/search?q=zip_archive_set_tempdir&literal=1 libzip itself has successfully built on all release architectures in experimental, and I have successfully tested a rebuild of all build-rdeps on amd64 against that version. Well, except for two which currently FTBFS anyway and are not in testing: mysql-workbench #1074563 and xtrkcad #1074722. (Well, and qgis, but that was due to my build environment having too limited resources.) So on that side things are looking safe. The information on https://release.debian.org/transitions/html/auto-libzip.html looks correct to me. Ben file: title = "libzip"; is_affected = .depends ~ "libzip4t64" | .depends ~ "libzip5"; is_good = .depends ~ "libzip5"; is_bad = .depends ~ "libzip4t64"; Cheers, Flo
signature.asc
Description: PGP signature
