Your message dated Sun, 4 Oct 2026 21:56:00 +0200
with message-id <[email protected]>
and subject line Re: Bug#1140175: transition: perl
has caused the Debian Bug report #1140175,
regarding transition: perl
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1140175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1140175
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected], [email protected]
Control: affects -1 + src:perl
User: [email protected]
Usertags: transition

Hi,

I'd like to get Perl 5.42 from experimental to unstable + testing. 

Apologies that I'm so terribly late with this. I'll skip my excuses,
but I'm copying the debian-perl list with a request for help.  Please
contact me if you want to help with maintaining Perl in Debian. Clearly
the current setup is not sustainable anymore.

Perl 5.42 was released last summer and has been in experimental since
August. As usual, I've run rebuild testing and a couple of debci test
rounds with it. Bugs are at

  
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.42-transition;[email protected]

I'm not aware of any showstoppers. but I note that #1140169 in perl-tk
was causing CI regressions in libconfig-model-itself-perl for some time
with Perl 5.42.2-1. The real bug is in perl-tk, but it may well bite
again with any Perl binary changes.

Perl 5.44 was expected to be released already, but I understand there's
been some delay and nobody knows how long it will take. I think it still
makes sense for us to get 5.42 into forky at this point, and then consider
5.44 separately.

I'll run one more round of test rebuilds with the packages that will
need a binNMU in the next few days, but I don't expect any related
regressions. Of course, general flux in unstable could still cause
unforeseen issues.

Please let me know when you have a transition window available, or if
you have any concerns about the transition.  Many thanks for your work
on the release.

Ben file:

title = "perl";
is_affected = .depends ~ "libperl5.40" | .depends ~ "perl-modules-5.40" | 
.depends ~ "libperl5.42" | .depends ~ "perl-modules-5.42";
is_good = .depends ~ "libperl5.42" | .depends ~ "perl-modules-5.42";
is_bad = .depends ~ "libperl5.40" | .depends ~ "perl-modules-5.40";

--- End Message ---
--- Begin Message ---
On 2026-07-31 21:12:20 +0200, Emilio Pozuelo Monfort wrote:
> Control: tags -1 pending
> 
> On 23/07/2026 00:28, Niko Tyni wrote:
> > On Sat, Jul 18, 2026 at 10:47:06AM +0200, Emilio Pozuelo Monfort wrote:
> > > Control: tags -1 confirmed
> > > 
> > > On 16/06/2026 20:58, Niko Tyni wrote:
> > > > Package: release.debian.org
> > > > Severity: normal
> > > > X-Debbugs-Cc: [email protected], [email protected]
> > > > Control: affects -1 + src:perl
> > > > User: [email protected]
> > > > Usertags: transition
> > 
> > > > I'd like to get Perl 5.42 from experimental to unstable + testing.
> > 
> > > Please go ahead.
> > 
> > Thanks, perl_5.42.2-3 uploaded and accepted.
> > 
> > I believe the binNMUs will need something like
> > 
> >    --extra-depends 'perl-base (>= 5.42.2)'
> > 
> > but I'm sure you already knew that :)
> 
> binNMU's autopkgtest were having issues because they are not installed with
> all needed packages from unstable, so there were a lot of bd-uninst, and we
> had to disable that.
> 
> After removing a few (somewhat-)leaf packages, perl has migrated to testing.
> There's still a handful of rdeps of libperl5.40 which need to migrate in
> order to completely finish this, but perl{,-base} 5.42 are now in testing
> and this is mostly done.

libperl5.40 is also gone from testing. Closing.

Cheers
-- 
Sebastian Ramacher

--- End Message ---

Reply via email to