Package: release.debian.org User: release.debian....@packages.debian.org Usertags: transition Tags: moreinfo X-Debbugs-Cc: p...@packages.debian.org Control: block -1 with 1016761
We'd like to get Perl 5.36 in bookworm. Filing this to get it on the radar properly, but I'd like to do a few more checks first. So tagging 'moreinfo' for now. I'll remove that when I'm done with the checks, hopefully in a couple of weeks at the latest. The package in experimental is in good shape. We've been continuously rebuilding perl reverse dependencies (currently 4507 packages) since June or so on http://perl.debian.net/ , and tracking regressions at https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.36-transition;users=debian-p...@lists.debian.org The only remaining regression in testing that I'm aware of is #1016761 which should be easy to fix by dropping the problematic test case that uses HTTP::Tiny internals in a not forward compatible way. I ran autopkgtest checks of 3847 packages that have Testsuite-Triggers: perl or Testsuite: autopkgtest-pkg-perl locally in July and did not find any regressions from sid. I intend to recheck this on ci.debian.net soon now that we have support for external repositories there (thanks, Paul et al.!) The recent egrep deprecation (#1019335) in sid may be a blocker for this though. I also intend to test rebuild the ~500 packages in sid that will need a binNMU one more time to catch any non-perl-related new build failures. I don't have a good way to spot non-amd64 architecture specific issues or unrelated version skew between unstable and testing, so those can still yield surprises for the transition. title = "perl"; is_affected = .depends ~ "libperl5.34|perlapi-5.34" | .pre-depends ~ "libperl5.34|perlapi-5.34"; is_good = .depends ~ "libperl5.36|perlapi-5.36" | .pre-depends ~ "libperl5.36|perlapi-5.36"; is_bad = .depends ~ "libperl5.34|perlapi-5.34" | .pre-depends ~ "libperl5.34|perlapi-5.34"; Thanks for your work on the release, -- Niko Tyni nt...@debiar.org
