Update perl to 5.30.2

https://metacpan.org/pod/release/SHAY/perl-5.30.2/pod/perldelta.pod

Incompatible Changes
    There are no changes intentionally incompatible with 5.30.0.

Updated Modules and Pragmata
  * Compress::Raw::Bzip2 has been upgraded from version 2.084 to 2.089.
  * Module::CoreList has been upgraded from version 5.20191110 to 5.20200314.

Selected Bug Fixes
  * printf() or sprintf() with the %n format no longer cause a panic
    on debugging builds, or report an incorrectly cached length value
    when producing SVfUTF8 flagged strings.
  * A memory leak in regular expression patterns has been fixed.
  * A read beyond buffer in grok_infnan has been fixed.
  * An assertion failure in the regular expression engine has been fixed.
  * (?{...}) eval groups in regular expressions no longer unintentionally
    trigger "EVAL without pos change exceeded limit in regex".


Proceed when you feel comfortable. deraadt@

16 files changed, 281 insertions, 102 deletions

diff --git a/gnu/usr.bin/perl/pod/perl.pod b/gnu/usr.bin/perl/pod/perl.pod
index f9ff1640936..ed5ba54281c 100644
--- a/gnu/usr.bin/perl/pod/perl.pod
+++ b/gnu/usr.bin/perl/pod/perl.pod
@@ -181,6 +181,7 @@ aux h2ph h2xs perlbug pl2pm pod2html pod2man splain xsubpp
 
     perlhist		Perl history records
     perldelta		Perl changes since previous version
+    perl5301delta	Perl changes in version 5.30.1
     perl5300delta	Perl changes in version 5.30.0
     perl5282delta	Perl changes in version 5.28.2
     perl5281delta	Perl changes in version 5.28.1
@@ -420,11 +421,9 @@ displayed by diagnostics are internally stored as short integers,
 so they are limited to a maximum of 65535 (higher numbers usually being
 affected by wraparound).
 
-You may mail your bug reports (be sure to include full configuration
+You may submit your bug reports (be sure to include full configuration
 information as output by the myconfig program in the perl source
-tree, or by C<perl -V>) to perlbug@perl.org .  If you've succeeded
-in compiling perl, the L<perlbug> script in the F<utils/> subdirectory
-can be used to help mail in a bug report.
+tree, or by C<perl -V>) to L<https://github.com/Perl/perl5/issues>.
 
 Perl actually stands for Pathologically Eclectic Rubbish Lister, but
 don't tell anyone I said that.
diff --git a/gnu/usr.bin/perl/pod/perl5301delta.pod b/gnu/usr.bin/perl/pod/perl5301delta.pod
new file mode 100644
index 00000000000..01a2725076c
--- /dev/null
+++ b/gnu/usr.bin/perl/pod/perl5301delta.pod
@@ -0,0 +1,188 @@
+=encoding utf8
+
+=head1 NAME
+
+perl5301delta - what is new for perl v5.30.1
+
+=head1 DESCRIPTION
+
+This document describes differences between the 5.30.0 release and the 5.30.1
+release.
+
+If you are upgrading from an earlier release such as 5.29.0, first read
+L<perl5300delta>, which describes differences between 5.29.0 and 5.30.0.
+
+=head1 Incompatible Changes
+
+There are no changes intentionally incompatible with 5.30.1.  If any exist,
+they are bugs, and we request that you submit a report.  See
+L</Reporting Bugs> below.
+
+=head1 Modules and Pragmata
+
+=head2 Updated Modules and Pragmata
+
+=over 4
+
+=item *
+
+L<Module::CoreList> has been upgraded from version 5.20190522 to 5.20191110.
+
+=back
+
+=head1 Documentation
+
+=head2 Changes to Existing Documentation
+
+We have attempted to update the documentation to reflect the changes listed in
+this document.  If you find any we have missed, send email to
+L<perlbug@perl.org|mailto:perlbug@perl.org>.
+
+Additionally, documentation has been updated to reference GitHub as the new
+canonical repository and to describe the new GitHub pull request workflow.
+
+=head1 Configuration and Compilation
+
+=over 4
+
+=item *
+
+The C<ECHO> macro is now defined.  This is used in a C<dtrace> rule that was
+originally changed for FreeBSD, and the FreeBSD make apparently predefines it.
+The Solaris make does not predefine C<ECHO> which broke this rule on Solaris.
+L<[perl #17057]|https://github.com/perl/perl5/issues/17057>
+
+=back
+
+=head1 Testing
+
+Tests were added and changed to reflect the other additions and changes in this
+release.
+
+=head1 Platform Support
+
+=head2 Platform-Specific Notes
+
+=over 4
+
+=item Win32
+
+The locale tests could crash on Win32 due to a Windows bug, and separately due
+to the CRT throwing an exception if the locale name wasn't validly encoded in
+the current code page.
+
+For the second we now decode the locale name ourselves, and always decode it as
+UTF-8.
+
+L<[perl #16922]|https://github.com/perl/perl5/issues/16922>
+
+=back
+
+=head1 Selected Bug Fixes
+
+=over 4
+
+=item *
+
+Setting C<$)> now properly sets supplementary group ids, if you have the
+necessary privileges.
+L<[perl #17031]|https://github.com/perl/perl5/issues/17031>
+
+=item *
+
+C<readline @foo> now evaluates C<@foo> in scalar context.  Previously, it would
+be evaluated in list context, and since readline() pops only one argument from
+the stack, the stack could underflow, or be left with unexpected values on it.
+L<[perl #16929]|https://github.com/perl/perl5/issues/16929>
+
+=item *
+
+sv_gets() now recovers better if the target SV is modified by a signal handler.
+L<[perl #16960]|https://github.com/perl/perl5/issues/16960>
+
+=item *
+
+Matching a non-C<SVf_UTF8> string against a regular expression containing
+Unicode literals could leak an SV on each match attempt.
+L<[perl #17140]|https://github.com/perl/perl5/issues/17140>
+
+=item *
+
+C<< sprintf("%.*a", -10000, $x) >> would cause a buffer overflow due to
+mishandling of the negative precision value.
+L<[perl #16942]|https://github.com/perl/perl5/issues/16942>
+
+=item *
+
+C<scalar()> on a reference could cause an erroneous assertion failure during
+compilation.
+L<[perl #16969]|https://github.com/perl/perl5/issues/16969>
+
+=back
+
+=head1 Acknowledgements
+
+Perl 5.30.1 represents approximately 6 months of development since Perl 5.30.0
+and contains approximately 4,700 lines of changes across 67 files from 14
+authors.
+
+Excluding auto-generated files, documentation and release tools, there were
+approximately 910 lines of changes to 20 .pm, .t, .c and .h files.
+
+Perl continues to flourish into its fourth decade thanks to a vibrant community
+of users and developers.  The following people are known to have contributed
+the improvements that became Perl 5.30.1:
+
+Chris 'BinGOs' Williams, Dan Book, David Mitchell, Hugo van der Sanden, James E
+Keenan, Karen Etheridge, Karl Williamson, Manuel Mausz, Max Maischein, Nicolas
+R., Sawyer X, Steve Hay, Tom Hukins, Tony Cook.
+
+The list above is almost certainly incomplete as it is automatically generated
+from version control history.  In particular, it does not include the names of
+the (very much appreciated) contributors who reported issues to the Perl bug
+tracker.
+
+Many of the changes included in this version originated in the CPAN modules
+included in Perl's core.  We're grateful to the entire CPAN community for
+helping Perl to flourish.
+
+For a more complete list of all of Perl's historical contributors, please see
+the F<AUTHORS> file in the Perl source distribution.
+
+=head1 Reporting Bugs
+
+If you find what you think is a bug, you might check the perl bug database at
+L<https://rt.perl.org/>.  There may also be information at
+L<http://www.perl.org/>, the Perl Home Page.
+
+If you believe you have an unreported bug, please run the L<perlbug> program
+included with your release.  Be sure to trim your bug down to a tiny but
+sufficient test case.  Your bug report, along with the output of C<perl -V>,
+will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
+
+If the bug you are reporting has security implications which make it
+inappropriate to send to a publicly archived mailing list, then see
+L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION> for details of how to
+report the issue.
+
+=head1 Give Thanks
+
+If you wish to thank the Perl 5 Porters for the work we had done in Perl 5, you
+can do so by running the C<perlthanks> program:
+
+    perlthanks
+
+This will send an email to the Perl 5 Porters list with your show of thanks.
+
+=head1 SEE ALSO
+
+The F<Changes> file for an explanation of how to view exhaustive details on
+what changed.
+
+The F<INSTALL> file for how to build Perl.
+
+The F<README> file for general stuff.
+
+The F<Artistic> and F<Copying> files for copyright information.
+
+=cut
diff --git a/gnu/usr.bin/perl/pod/perldelta.pod b/gnu/usr.bin/perl/pod/perldelta.pod
index cea8d7a0df2..4c31cf0e8ac 100644
--- a/gnu/usr.bin/perl/pod/perldelta.pod
+++ b/gnu/usr.bin/perl/pod/perldelta.pod
@@ -2,21 +2,21 @@
 
 =head1 NAME
 
-perldelta - what is new for perl v5.30.1
+perldelta - what is new for perl v5.30.2
 
 =head1 DESCRIPTION
 
-This document describes differences between the 5.30.0 release and the 5.30.1
+This document describes differences between the 5.30.1 release and the 5.30.2
 release.
 
-If you are upgrading from an earlier release such as 5.29.0, first read
-L<perl5300delta>, which describes differences between 5.29.0 and 5.30.0.
+If you are upgrading from an earlier release such as 5.30.0, first read
+L<perl5301delta>, which describes differences between 5.30.0 and 5.30.1.
 
 =head1 Incompatible Changes
 
-There are no changes intentionally incompatible with 5.30.1.  If any exist,
-they are bugs, and we request that you submit a report.  See
-L</Reporting Bugs> below.
+There are no changes intentionally incompatible with 5.30.0.  If any exist,
+they are bugs, and we request that you submit a report.  See L</Reporting Bugs>
+below.
 
 =head1 Modules and Pragmata
 
@@ -26,7 +26,11 @@ L</Reporting Bugs> below.
 
 =item *
 
-L<Module::CoreList> has been upgraded from version 5.20190522 to 5.20191110.
+L<Compress::Raw::Bzip2> has been upgraded from version 2.084 to 2.089.
+
+=item *
+
+L<Module::CoreList> has been upgraded from version 5.20191110 to 5.20200314.
 
 =back
 
@@ -34,12 +38,9 @@ L<Module::CoreList> has been upgraded from version 5.20190522 to 5.20191110.
 
 =head2 Changes to Existing Documentation
 
-We have attempted to update the documentation to reflect the changes listed in
-this document.  If you find any we have missed, send email to
-L<perlbug@perl.org|mailto:perlbug@perl.org>.
-
-Additionally, documentation has been updated to reference GitHub as the new
-canonical repository and to describe the new GitHub pull request workflow.
+We have attempted to update the documentation to reflect the changes
+listed in this document.  If you find any we have missed, send email
+to L<https://github.com/Perl/perl5/issues>.
 
 =head1 Configuration and Compilation
 
@@ -47,10 +48,7 @@ canonical repository and to describe the new GitHub pull request workflow.
 
 =item *
 
-The C<ECHO> macro is now defined.  This is used in a C<dtrace> rule that was
-originally changed for FreeBSD, and the FreeBSD make apparently predefines it.
-The Solaris make does not predefine C<ECHO> which broke this rule on Solaris.
-L<[perl #17057]|https://github.com/perl/perl5/issues/17057>
+GCC 10 is now supported by F<Configure>.
 
 =back
 
@@ -65,16 +63,9 @@ release.
 
 =over 4
 
-=item Win32
-
-The locale tests could crash on Win32 due to a Windows bug, and separately due
-to the CRT throwing an exception if the locale name wasn't validly encoded in
-the current code page.
-
-For the second we now decode the locale name ourselves, and always decode it as
-UTF-8.
+=item Windows
 
-L<[perl #16922]|https://github.com/perl/perl5/issues/16922>
+The MYMALLOC (PERL_MALLOC) build on Windows has been fixed.
 
 =back
 
@@ -84,58 +75,55 @@ L<[perl #16922]|https://github.com/perl/perl5/issues/16922>
 
 =item *
 
-Setting C<$)> now properly sets supplementary group ids, if you have the
-necessary privileges.
-L<[perl #17031]|https://github.com/perl/perl5/issues/17031>
+printf() or sprintf() with the C<%n> format no longer cause a panic on
+debugging builds, or report an incorrectly cached length value when producing
+C<SVfUTF8> flagged strings.
 
-=item *
-
-C<readline @foo> now evaluates C<@foo> in scalar context.  Previously, it would
-be evaluated in list context, and since readline() pops only one argument from
-the stack, the stack could underflow, or be left with unexpected values on it.
-L<[perl #16929]|https://github.com/perl/perl5/issues/16929>
+[L<GH #17221|https://github.com/Perl/perl5/issues/17221>]
 
 =item *
 
-sv_gets() now recovers better if the target SV is modified by a signal handler.
-L<[perl #16960]|https://github.com/perl/perl5/issues/16960>
+A memory leak in regular expression patterns has been fixed.
+
+[L<GH #17218|https://github.com/Perl/perl5/issues/17218>]
 
 =item *
 
-Matching a non-C<SVf_UTF8> string against a regular expression containing
-Unicode literals could leak an SV on each match attempt.
-L<[perl #17140]|https://github.com/perl/perl5/issues/17140>
+A read beyond buffer in grok_infnan has been fixed.
+
+[L<GH #17370|https://github.com/Perl/perl5/issues/17370>]
 
 =item *
 
-C<< sprintf("%.*a", -10000, $x) >> would cause a buffer overflow due to
-mishandling of the negative precision value.
-L<[perl #16942]|https://github.com/perl/perl5/issues/16942>
+An assertion failure in the regular expression engine has been fixed.
+
+[L<GH #17372|https://github.com/Perl/perl5/issues/17372>]
 
 =item *
 
-C<scalar()> on a reference could cause an erroneous assertion failure during
-compilation.
-L<[perl #16969]|https://github.com/perl/perl5/issues/16969>
+C<(?{...})> eval groups in regular expressions no longer unintentionally
+trigger "EVAL without pos change exceeded limit in regex".
+
+[L<GH #17490|https://github.com/Perl/perl5/issues/17490>]
 
 =back
 
 =head1 Acknowledgements
 
-Perl 5.30.1 represents approximately 6 months of development since Perl 5.30.0
-and contains approximately 4,700 lines of changes across 67 files from 14
+Perl 5.30.2 represents approximately 4 months of development since Perl 5.30.1
+and contains approximately 2,100 lines of changes across 110 files from 15
 authors.
 
 Excluding auto-generated files, documentation and release tools, there were
-approximately 910 lines of changes to 20 .pm, .t, .c and .h files.
+approximately 920 lines of changes to 30 .pm, .t, .c and .h files.
 
 Perl continues to flourish into its fourth decade thanks to a vibrant community
 of users and developers.  The following people are known to have contributed
-the improvements that became Perl 5.30.1:
+the improvements that became Perl 5.30.2:
 
-Chris 'BinGOs' Williams, Dan Book, David Mitchell, Hugo van der Sanden, James E
-Keenan, Karen Etheridge, Karl Williamson, Manuel Mausz, Max Maischein, Nicolas
-R., Sawyer X, Steve Hay, Tom Hukins, Tony Cook.
+Chris 'BinGOs' Williams, Dan Book, David Mitchell, Hugo van der Sanden, Karen
+Etheridge, Karl Williamson, Matthew Horsfall, Nicolas R., Petr Písař, Renee
+Baecker, Sawyer X, Steve Hay, Tomasz Konojacki, Tony Cook, Yves Orton.
 
 The list above is almost certainly incomplete as it is automatically generated
 from version control history.  In particular, it does not include the names of
@@ -155,20 +143,18 @@ If you find what you think is a bug, you might check the perl bug database at
 L<https://rt.perl.org/>.  There may also be information at
 L<http://www.perl.org/>, the Perl Home Page.
 
-If you believe you have an unreported bug, please run the L<perlbug> program
-included with your release.  Be sure to trim your bug down to a tiny but
-sufficient test case.  Your bug report, along with the output of C<perl -V>,
-will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
+If you believe you have an unreported bug, please open an issue at
+L<https://github.com/Perl/perl5/issues>.  Be sure to trim your bug down to a
+tiny but sufficient test case.
 
 If the bug you are reporting has security implications which make it
-inappropriate to send to a publicly archived mailing list, then see
-L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION> for details of how to
-report the issue.
+inappropriate to send to a public issue tracker, then see L<perlsec/SECURITY
+VULNERABILITY CONTACT INFORMATION> for details of how to report the issue.
 
 =head1 Give Thanks
 
-If you wish to thank the Perl 5 Porters for the work we had done in Perl 5, you
-can do so by running the C<perlthanks> program:
+If you wish to thank the Perl 5 Porters for the work we had done in Perl 5,
+you can do so by running the C<perlthanks> program:
 
     perlthanks
 
diff --git a/gnu/usr.bin/perl/pod/perldiag.pod b/gnu/usr.bin/perl/pod/perldiag.pod
index f69b1b8367d..709dd44b4e4 100644
--- a/gnu/usr.bin/perl/pod/perldiag.pod
+++ b/gnu/usr.bin/perl/pod/perldiag.pod
@@ -1924,7 +1924,7 @@ called as barewords.  Something like this will work:
 
 (P) This is either an error in Perl, or, if you're using
 one, your L<custom regular expression engine|perlreapi>.  If not the
-latter, report the problem through the L<perlbug> utility.
+latter, report the problem to L<https://github.com/Perl/perl5/issues>.
 
 =item corrupted regexp pointers
 
@@ -4845,7 +4845,7 @@ utility to report; in regex; marked by S<<-- HERE> in m/%s/
 (S regexp) You used a regular expression with case-insensitive matching,
 and there is a bug in Perl in which the built-in regular expression
 folding rules are not accurate.  This may lead to incorrect results.
-Please report this as a bug using the L<perlbug> utility.
+Please report this as a bug to L<https://github.com/Perl/perl5/issues>.
 
 =item PerlIO layer ':win32' is experimental
 
diff --git a/gnu/usr.bin/perl/pod/perlebcdic.pod b/gnu/usr.bin/perl/pod/perlebcdic.pod
index d2e2d4e8ae5..3f5fc2cf91c 100644
--- a/gnu/usr.bin/perl/pod/perlebcdic.pod
+++ b/gnu/usr.bin/perl/pod/perlebcdic.pod
@@ -19,7 +19,7 @@ not all
 the modules found on CPAN but shipped with core Perl work on z/OS.
 
 If you want to use Perl on a non-z/OS EBCDIC machine, please let us know
-by sending mail to perlbug@perl.org
+at L<https://github.com/Perl/perl5/issues>.
 
 Writing Perl on an EBCDIC platform is really no different than writing
 on an L</ASCII> one, but with different underlying numbers, as we'll see
diff --git a/gnu/usr.bin/perl/pod/perlguts.pod b/gnu/usr.bin/perl/pod/perlguts.pod
index 34d92a42094..9a87c17f344 100644
--- a/gnu/usr.bin/perl/pod/perlguts.pod
+++ b/gnu/usr.bin/perl/pod/perlguts.pod
@@ -2339,8 +2339,8 @@ part of the API.  (See L</Internal
 Functions>.)  The easiest way to be B<sure> a
 function is part of the API is to find its entry in L<perlapi>.
 If it exists in L<perlapi>, it's part of the API.  If it doesn't, and you
-think it should be (i.e., you need it for your extension), send mail via
-L<perlbug> explaining why you think it should be.
+think it should be (i.e., you need it for your extension), submit an issue at
+L<https://github.com/Perl/perl5/issues> explaining why you think it should be.
 
 Second problem: there must be a syntax so that the same subroutine
 declarations and calls can pass a structure as their first argument,
diff --git a/gnu/usr.bin/perl/pod/perlhack.pod b/gnu/usr.bin/perl/pod/perlhack.pod
index b9f2b5ffd27..5c6695c82c9 100644
--- a/gnu/usr.bin/perl/pod/perlhack.pod
+++ b/gnu/usr.bin/perl/pod/perlhack.pod
@@ -117,12 +117,9 @@ these commands:
 
 =head1 BUG REPORTING
 
-If you want to report a bug in Perl, you must use the F<perlbug>
-command line tool.  This tool will ensure that your bug report includes
-all the relevant system and configuration information.
-
-To browse existing Perl bugs and patches, you can use the web interface
-at L<http://rt.perl.org/>.
+If you want to report a bug in Perl, or browse existing Perl bugs and
+patches, use the GitHub issue tracker at
+L<https://github.com/perl/perl5/issues>.
 
 Please check the archive of the perl5-porters list (see below) and/or
 the bug tracking system before submitting a bug report.  Often, you'll
@@ -1172,11 +1169,11 @@ configurations.
 
 Both efforts welcome volunteers.  In order to get involved in smoke
 testing of the perl itself visit
-L<http://search.cpan.org/dist/Test-Smoke/>.  In order to start smoke
+L<https://metacpan.org/release/Test-Smoke>.  In order to start smoke
 testing CPAN modules visit
-L<http://search.cpan.org/dist/CPANPLUS-YACSmoke/> or
-L<http://search.cpan.org/dist/minismokebox/> or
-L<http://search.cpan.org/dist/CPAN-Reporter/>.
+L<https://metacpan.org/release/CPANPLUS-YACSmoke> or
+L<https://metacpan.org/release/minismokebox> or
+L<https://metacpan.org/release/CPAN-Reporter>.
 
 =head1 WHAT NEXT?
 
diff --git a/gnu/usr.bin/perl/pod/perlhist.pod b/gnu/usr.bin/perl/pod/perlhist.pod
index 66e9d472bfa..a002d488220 100644
--- a/gnu/usr.bin/perl/pod/perlhist.pod
+++ b/gnu/usr.bin/perl/pod/perlhist.pod
@@ -671,13 +671,19 @@ the strings?).
  Sawyer X  5.30.0       2019-May-22
  Steve     5.30.1-RC1   2019-Oct-27
  Steve     5.30.1       2019-Nov-10
+ Steve     5.30.2-RC1   2020-Feb-29
+ Steve     5.30.2       2020-Mar-14
 
- Sawyer X  5.31.0       2018-May-24     The 5.31 development track
+ Sawyer X  5.31.0       2019-May-24     The 5.31 development track
  Ether     5.31.1       2019-Jun-20
  Steve     5.31.2       2019-Jul-20
  Tom H     5.31.3       2019-Aug-20
  Max M     5.31.4       2019-Sep-20
  Steve     5.31.5       2019-Oct-20
+ BinGOs    5.31.6       2019-Nov-20
+ Nicolas R 5.31.7       2019-Dec-20
+ Matthew H 5.31.8       2020-Jan-20
+ Renee     5.31.9       2020-Feb-20
 
 =head2 SELECTED RELEASE SIZES
 
diff --git a/gnu/usr.bin/perl/pod/perllocale.pod b/gnu/usr.bin/perl/pod/perllocale.pod
index df2db5c474b..ec1af276034 100644
--- a/gnu/usr.bin/perl/pod/perllocale.pod
+++ b/gnu/usr.bin/perl/pod/perllocale.pod
@@ -1693,7 +1693,8 @@ effect.  See L<perlembed/Using embedded Perl with POSIX locales>.
 It becomes more important for perl to know about all the possible
 locale categories on the platform, even if they aren't apparently used
 in your program.  Perl knows all of the Linux ones.  If your platform
-has others, you can send email to L<mailto:perlbug@perl.org> for
+has others, you can submit an issue at
+L<https://github.com/Perl/perl5/issues> for
 inclusion of it in the next release.  In the meantime, it is possible to
 edit the Perl source to teach it about the category, and then recompile.
 Search for instances of, say, C<LC_PAPER> in the source, and use that as
@@ -1714,11 +1715,12 @@ In certain systems, the operating system's locale support
 is broken and cannot be fixed or used by Perl.  Such deficiencies can
 and will result in mysterious hangs and/or Perl core dumps when
 C<use locale> is in effect.  When confronted with such a system,
-please report in excruciating detail to <F<perlbug@perl.org>>, and
+please report in excruciating detail to
+<L<https://github.com/Perl/perl5/issues>>, and
 also contact your vendor: bug fixes may exist for these problems
 in your operating system.  Sometimes such bug fixes are called an
 operating system upgrade.  If you have the source for Perl, include in
-the perlbug email the output of the test described above in L</Testing
+the bug report the output of the test described above in L</Testing
 for broken locales>.
 
 =head1 SEE ALSO
diff --git a/gnu/usr.bin/perl/pod/perlmodinstall.pod b/gnu/usr.bin/perl/pod/perlmodinstall.pod
index 6ce5c84d7e5..8cd44fd125a 100644
--- a/gnu/usr.bin/perl/pod/perlmodinstall.pod
+++ b/gnu/usr.bin/perl/pod/perlmodinstall.pod
@@ -140,7 +140,7 @@ If you used WinZip, this was already done for you.
 You'll need the C<nmake> utility, available at
 L<http://download.microsoft.com/download/vc15/Patch/1.52/W95/EN-US/nmake15.exe>
 or dmake, available on CPAN.
-L<http://search.cpan.org/dist/dmake/>
+L<https://metacpan.org/release/dmake>
 
 Does the module require compilation (i.e. does it have files that end
 in .xs, .c, .h, .y, .cc, .cxx, or .C)?  If it does, life is now
diff --git a/gnu/usr.bin/perl/pod/perlmodlib.PL b/gnu/usr.bin/perl/pod/perlmodlib.PL
index 9571b58f022..aed957ae516 100644
--- a/gnu/usr.bin/perl/pod/perlmodlib.PL
+++ b/gnu/usr.bin/perl/pod/perlmodlib.PL
@@ -119,7 +119,7 @@ push @mod, "=item Config\n\nAccess Perl configuration information\n\n";
 # parse as (reasonably) sane Pod as-is to anything that attempts to
 # brute-force treat it as such. The content is already useful - this just
 # makes it tidier, by stopping anything doing this mistaking the rest of the
-# Perl code for Pod. eg http://search.cpan.org/dist/perl/pod/perlmodlib.PL
+# Perl code for Pod. eg https://metacpan.org/pod/perlmodlib
 
 print $out <<'=cut';
 =head1 NAME
diff --git a/gnu/usr.bin/perl/pod/perlootut.pod b/gnu/usr.bin/perl/pod/perlootut.pod
index b340dc6ea70..d7474b4b4da 100644
--- a/gnu/usr.bin/perl/pod/perlootut.pod
+++ b/gnu/usr.bin/perl/pod/perlootut.pod
@@ -23,7 +23,7 @@ version.
 This document provides an introduction to object-oriented programming
 in Perl. It begins with a brief overview of the concepts behind object
 oriented design. Then it introduces several different OO systems from
-L<CPAN|http://search.cpan.org> which build on top of what Perl
+L<CPAN|https://www.cpan.org> which build on top of what Perl
 provides.
 
 By default, Perl's built-in OO system is very minimal, leaving you to
@@ -547,7 +547,7 @@ C<Moose> itself.
 =item * Rich ecosystem
 
 There is a rich ecosystem of C<Moose> extensions on CPAN under the
-L<MooseX|http://search.cpan.org/search?query=MooseX&mode=dist>
+L<MooseX|https://metacpan.org/search?q=MooseX>
 namespace. In addition, many modules on CPAN already use C<Moose>,
 providing you with lots of examples to learn from.
 
@@ -556,7 +556,7 @@ providing you with lots of examples to learn from.
 C<Moose> is a very powerful tool, and we can't cover all of its
 features here. We encourage you to learn more by reading the C<Moose>
 documentation, starting with
-L<Moose::Manual|http://search.cpan.org/perldoc?Moose::Manual>.
+L<Moose::Manual|https://metacpan.org/pod/Moose::Manual>.
 
 =back
 
diff --git a/gnu/usr.bin/perl/pod/perlport.pod b/gnu/usr.bin/perl/pod/perlport.pod
index b870c2334aa..b3ef9b5219a 100644
--- a/gnu/usr.bin/perl/pod/perlport.pod
+++ b/gnu/usr.bin/perl/pod/perlport.pod
@@ -1234,8 +1234,8 @@ character sets internally (usually Character Code Set ID 0037 for OS/400
 and either 1047 or POSIX-BC for S/390 systems).
 
 The rest of this section may need updating, but we don't know what it
-should say.  Please email comments to
-L<perlbug@perl.org|mailto:perlbug@perl.org>.
+should say.  Please submit comments to
+L<https://github.com/Perl/perl5/issues>.
 
 On the mainframe Perl currently works under the "Unix system
 services for OS/390" (formerly known as OpenEdition), VM/ESA OpenEdition, or
@@ -2475,7 +2475,8 @@ the past (5.005_03 and earlier), but we haven't been able to verify
 their status for the current release, either because the
 hardware/software platforms are rare or because we don't have an
 active champion on these platforms--or both.  They used to work,
-though, so go ahead and try compiling them, and let perlbug@perl.org
+though, so go ahead and try compiling them, and let
+L<https://github.com/Perl/perl5/issues> know
 of any trouble.
 
         3b1
diff --git a/gnu/usr.bin/perl/pod/perlrecharclass.pod b/gnu/usr.bin/perl/pod/perlrecharclass.pod
index bda60cd49e7..2e09c4bac59 100644
--- a/gnu/usr.bin/perl/pod/perlrecharclass.pod
+++ b/gnu/usr.bin/perl/pod/perlrecharclass.pod
@@ -1214,8 +1214,8 @@ illustrated above.
 
 Due to the way that Perl parses things, your parentheses and brackets
 may need to be balanced, even including comments.  If you run into any
-examples, please send them to C<perlbug@perl.org>, so that we can have a
-concrete example for this man page.
+examples, please submit them to L<https://github.com/Perl/perl5/issues>,
+so that we can have a concrete example for this man page.
 
 We may change it so that things that remain legal uses in normal bracketed
 character classes might become illegal within this experimental
diff --git a/gnu/usr.bin/perl/pod/perlthrtut.pod b/gnu/usr.bin/perl/pod/perlthrtut.pod
index fa56f811229..5a7ae7f68d3 100644
--- a/gnu/usr.bin/perl/pod/perlthrtut.pod
+++ b/gnu/usr.bin/perl/pod/perlthrtut.pod
@@ -1084,13 +1084,13 @@ Annotated POD for L<threads>:
 L<http://annocpan.org/?mode=search&field=Module&name=threads>
 
 Latest version of L<threads> on CPAN:
-L<http://search.cpan.org/search?module=threads>
+L<https://metacpan.org/pod/threads>
 
 Annotated POD for L<threads::shared>:
 L<http://annocpan.org/?mode=search&field=Module&name=threads%3A%3Ashared>
 
 Latest version of L<threads::shared> on CPAN:
-L<http://search.cpan.org/search?module=threads%3A%3Ashared>
+L<https://metacpan.org/pod/threads::shared>
 
 Perl threads mailing list:
 L<http://lists.perl.org/list/ithreads.html>
diff --git a/gnu/usr.bin/perl/pod/perlutil.pod b/gnu/usr.bin/perl/pod/perlutil.pod
index b41a6118305..0051f68b175 100644
--- a/gnu/usr.bin/perl/pod/perlutil.pod
+++ b/gnu/usr.bin/perl/pod/perlutil.pod
@@ -106,10 +106,10 @@ and in particular, extending Perl with C.
 
 =item L<perlbug|perlbug>
 
-F<perlbug> is the recommended way to report bugs in the perl interpreter
-itself or any of the standard library modules back to the developers;
-please read through the documentation for F<perlbug> thoroughly before
-using it to submit a bug report.
+F<perlbug> used to be the recommended way to report bugs in the perl
+interpreter itself or any of the standard library modules back to the
+developers; bug reports and patches should now be submitted to
+L<https://github.com/Perl/perl5/issues>.
 
 =item L<perlthanks|perlbug>