Package: release.debian.org User: release.debian....@packages.debian.org Usertags: transition
Hello, I want to transition libidn to a newer upstream version, and they API/ABI bumped. This is my first transition in many years, so I'm looking for guidance here. I have uploaded 1.38-1 to experimental, and it builds everywhere. The binary package libidn11 is replaced with libidn12; libidn11-dev renamed to libidn-dev (adding a dummy package with the old name); and libidn11-java is removed (not setup for java usage properly and <10 popcon). Speaking as upstream of the package, I expect everything to build with the new version, doing the API/ABI bump was a mistake but it is several years old by now. Reverse dependencies have been built here: https://salsa.debian.org/debian/libidn/-/pipelines/273580 Some comments: - clamav: libclamav-dev depends on libidn11-dev needessly: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991976 - echoping: ftbfs otherwise too, not related to this - clickhouse: ftbfs due to 2h build timeout on salsa, otherwise should be okay. Is there anything more I should do now? Let me know when I can upload to unstable. Ben file (based on auto-generated output on the webpage -- not sure this is correct -- why doesn't it output something in the right format?): title = "libidn"; is_affected = .depends ~ "/\b(libidn\-dev|libidn12|libidn11|libidn11\-java)\b/"; is_good = .depends ~ "/\b(libidn\-dev|libidn12)\b/"; is_bad = .depends ~ "/\b(libidn11|libidn11\-java)\b/"; /Simon
signature.asc
Description: PGP signature
