Package: release.debian.org User: release.debian....@packages.debian.org Usertags: transition X-Debbugs-Cc: debian-p...@lists.debian.org, p...@packages.debian.org Control: block -1 with 1002093 997267 997189
Hi, we'd like a transition slot for Perl 5.34. Should have done this months ago, but real life has interfered. Sorry about that. Perl 5.36 is scheluded for May or so, and I expect that will be our target for bookworm. Nevertheless, it's probably best to do this incrementally and have a 5.34 transition now in case 5.36 turns out to be difficult for some reason. The changes in 5.34 are quite small, as upstream spent most of that release cycle planning Perl 7 (which did not quite work out.) This reflects in the very low number regressions we found in our test rebuilds, visible at https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.34-transition;users=debian-p...@lists.debian.org with just one bug open (openscap, not in testing). I did a full archive test rebuild back in May, and partial test rebuilds in August. Coming back to this now, I've done another round of test rebuilds for those packages that will need binNMUs. I don't think another full round is necessary: it seems unlikely that the other packages might have introduced any Perl 5.34 related regressions in the meantime. There's a few packages that have unrelated build failures in current sid. I'm marking the ones in testing as blockers for this. Not sure if this Ben file is correct but hope it helps a bit: title = "perl"; is_affected = .depends ~ "libperl5.32|perlapi-5.32" | .pre-depends ~ "libperl5.32|perlapi-5.32"; is_good = .depends ~ "libperl5.34|perlapi-5.34" | .pre-depends ~ "libperl5.34|perlapi-5.34"; is_bad = .depends ~ "libperl5.32|perlapi-5.32" | .pre-depends ~ "libperl5.32|perlapi-5.32"; Thanks for your work, -- Niko Tyni nt...@debian.org
