[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1082293: marked as done (transition: perl 5.40)

Your message dated Thu, 28 Nov 2024 20:56:08 +0100
with message-id <70ccea41-b7ec-42ce-9b0e-a9fcd01f06af@debian.org>
and subject line Re: Bug#1082293: transition: perl 5.40
has caused the Debian Bug report #1082293,
regarding transition: perl 5.40
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 owner@bugs.debian.org
immediately.)


-- 
1082293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082293
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: transition
X-Debbugs-Cc: perl@packages.debian.org

Hi release team,

I'd like to get Perl 5.40 into sid and trixie.

There's four known regression bugs left open. One package
(libgetopt-long-descriptive-perl, #1078075) will need an upload in
lockstep with perl. The other three have pending NMUs in the DELAYED queue
(thanks Gregor!)

  https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.40-transition;users=debian-perl@lists.debian.org

As usual we've been running continuous amd64 rebuilds on perl.debian.net
against Perl 5.40 since early June to catch build time regressions. I've
also checked for related autopkgtest regressions in all packages
declaring Testsuite: autopkgtest-pkg-perl, having Testsuite-Triggers:
perl, or depending on perl.

I don't have good tools to check for existing testing/unstable skew
with packages that will need binNMUs. The only blocker I'm currently
aware of is vim / #1082125 . 

Ben file proposal, just copy-pasting from last year:

title = "perl";
is_affected = .depends ~ "libperl5.38|perlapi-5.38" | .pre-depends ~ "libperl5.38|perlapi-5.38";
is_good = .depends ~ "libperl5.40|perlapi-5.40" | .pre-depends ~ "libperl5.40|perlapi-5.40";
is_bad = .depends ~ "libperl5.38|perlapi-5.38" | .pre-depends ~ "libperl5.38|perlapi-5.38";

I hope things will be as ready as can be in a week or so. Please let
me know when a transition slot might be available, and also if you have
any concerns of course.

Thanks for your work on Debian,
-- 
Niko

--- End Message ---
--- Begin Message --- 
On 19/09/2024 19:19, Niko Tyni wrote:

Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: transition
X-Debbugs-Cc: perl@packages.debian.org

Hi release team,

I'd like to get Perl 5.40 into sid and trixie.

There's four known regression bugs left open. One package
(libgetopt-long-descriptive-perl, #1078075) will need an upload in
lockstep with perl. The other three have pending NMUs in the DELAYED queue
(thanks Gregor!)

   https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.40-transition;users=debian-perl@lists.debian.org

As usual we've been running continuous amd64 rebuilds on perl.debian.net
against Perl 5.40 since early June to catch build time regressions. I've
also checked for related autopkgtest regressions in all packages
declaring Testsuite: autopkgtest-pkg-perl, having Testsuite-Triggers:
perl, or depending on perl.

I don't have good tools to check for existing testing/unstable skew
with packages that will need binNMUs. The only blocker I'm currently
aware of is vim / #1082125 .

Ben file proposal, just copy-pasting from last year:

title = "perl";
is_affected = .depends ~ "libperl5.38|perlapi-5.38" | .pre-depends ~ "libperl5.38|perlapi-5.38";
is_good = .depends ~ "libperl5.40|perlapi-5.40" | .pre-depends ~ "libperl5.40|perlapi-5.40";
is_bad = .depends ~ "libperl5.38|perlapi-5.38" | .pre-depends ~ "libperl5.38|perlapi-5.38";

I hope things will be as ready as can be in a week or so. Please let
me know when a transition slot might be available, and also if you have
any concerns of course.


Perl is fully migrated, let's close this.

Cheers,
Emilio

--- End Message ---
Reply to: