On Fri, Apr 24, 2020 at 08:47:07PM +0300, Niko Tyni wrote: > Package: perl > Version: 5.28.1-6 > Severity: normal > Tags: buster fixed-upstream > Forwarded: https://github.com/Perl/perl5/issues/17197 > Control: found -1 5.30.0-10 > > The upstream tool to submit bug reports, /usr/bin/perlbug, does not > currently work as advertised since upstream has moved from rt.perl.org > to github.com/Perl/perl5 . It send the report to the old bug submission > address perl...@perl.org, which (I believe) nowadays gives an autoresponse > suggesting to file a GitHub issue instead. > > Upstream has recently addressed this: 5.30.2 has > > https://github.com/Perl/perl5/commit/b9e2183386fadc0979b46e024365ceab56a369aa > > removing references to perlbug,
I don't think this is addressing it at all. As jidanni points out in the issue you reference below, the manpage for perlbug should point out that it's doing the wrong thing at the very least. I would probably have used perlbug myself the next time I needed to file a report with diagnostics, even though I know that upstream has moved to github. > and upcoming 5.31.11 will have > > https://github.com/Perl/perl5/commit/31fa749cfc50ff7f2bde2237bf6da5547efd53d4 > > which modifies the perlbug tool to save its output to a file and direct > users to the GitHub issue tracker. I think we should backport this to all supported versions of perl in Debian. Then again, we should probably also teach that tool that in many cases we prefer to receive reports at the BTS... > The upstream issue at > > https://github.com/Perl/perl5/issues/17197 > > has the full discussion. > > While I expect this will be fixed in Debian bullseye by upgrading to 5.32, > we should probably do something about stable too. Indeed. Had I remembered about this bug earlier I would have probably tried to do something for the 5.30.2-1 upload. Dominic
