The perlbug utility and perlbug@perl.org should no longer be used to submit bug reports or patches.
# (hopefully) current and preferred email addresses from the commits.
# These people have either submitted patches or suggestions, or their bug
# reports or comments have inspired the appropriate patches. Corrections,
-# additions, deletions welcome; send them to perlbug@perl.org, preferably
+# additions, deletions welcome; send them as a pull request to
+# https://github.com/Perl/perl5, or to perl5-porters@perl.org, preferably
# as the output of diff(1), diff -u or diff -c between the original and a
# corrected version of this file.
#
$me: Fatal Error: I can't find a Bourne Shell anywhere.
Usually it's in /bin/sh. How did you even get this far?
-Please contact me (Perl Maintainers) at perlbug@perl.org and
-we'll try to straighten this all out.
+Please contact me (Perl Maintainers) at https://github.com/Perl/perl5/issues
+and we'll try to straighten this all out.
EOM
exit 1
;;
You have the option of continuing the configuration process, despite the
distinct possibility that your kit is damaged, by typing 'y'es. If you
do, don't blame me if something goes wrong. I advise you to type 'n'o
-and contact the author (perlbug@perl.org).
+and contact the author (https://github.com/Perl/perl5/issues).
EOM
echo $n "Continue? [n] $c" >&4
Unix system. If despite that it blows up on yours, your best bet is to edit
Configure and run it again. If you can't run Configure for some reason,
you'll have to generate a config.sh file by hand. Whatever problems you
-have, let me (perlbug@perl.org) know how I blew it.
+have, let me (https://github.com/Perl/perl5/issues) know how I blew it.
This installation script affects things in two ways:
(cd $src/hints; ls -C *.sh) | $sed 's/\.sh/ /g' >&4
dflt=''
: Half the following guesses are probably wrong... If you have better
- : tests or hints, please send them to perlbug@perl.org
+ : tests or hints, please send them to https://github.com/Perl/perl5/issues
: The metaconfig authors would also appreciate a copy...
$test -f /irix && osname=irix
$test -f /xenix && osname=sco_xenix
mc_file=$1;
shift;
case "$usedevel" in $define|true|[yY]*) if $test ! -f "${mc_file}.c"; then
-echo "Internal Configure script bug - compiler test file ${mc_file}.c is missing. Please report this to perlbug@perl.org" >&4;
+echo "Internal Configure script bug - compiler test file ${mc_file}.c is missing. Please report this to https://github.com/Perl/perl5/issues" >&4;
exit 1;
fi;
esac;
*) $cat >&4 <<EOM
WARNING: Use of the shrpdir variable for the installation location of
the shared $libperl is not supported. It was never documented and
-will not work in this version. Let me (perlbug@perl.org)
+will not work in this version. Let me (https://github.com/Perl/perl5/issues)
know of any problems this may cause.
EOM
=head1 Reporting Problems
-Wherever possible please use the perlbug tool supplied with this Perl
-to report problems, as it automatically includes summary configuration
-information about your perl, which may help us track down problems far
-more quickly. But first you should read the advice in this file,
-carefully re-read the error message and check the relevant manual pages
-on your system, as these may help you find an immediate solution.
-Once you've exhausted the documentation, please report bugs to us using
-the 'perlbug' tool.
-
-The perlbug tool is installed along with perl, so after you have
-completed C<make install> it should be possible to run it with plain
-C<perlbug>. If the install fails, or you want to report problems with
-C<make test> without installing perl, then you can use C<make nok> to
-run perlbug to report the problem, or run it by hand from this source
-directory with C<./perl -Ilib utils/perlbug>
-
-If the build fails too early to run perlbug uninstalled, then please
-B<run> the C<./myconfig> shell script, and mail its output along with
-an accurate description of your problem to perlbug@perl.org
+Please report problems to the GitHub issue tracker at
+https://github.com/Perl/perl5/issues, which will ask for the
+appropriate summary configuration information about your perl, which
+may help us track down problems far more quickly. But first you should
+read the advice in this file, carefully re-read the error message and
+check the relevant manual pages on your system, as these may help you
+find an immediate solution. Once you've exhausted the documentation,
+please report bugs to us using the GitHub tracker.
+
+The summary configuration information can be printed with C<perl -V>.
+If the install fails, or you want to report problems with C<make test>
+without installing perl, then you can run it by hand from this source
+directory with C<./perl -V>.
+
+If the build fails too early to run perl, then please
+B<run> the C<./myconfig> shell script, and include its output along
+with an accurate description of your problem.
If Configure itself fails, and does not generate a config.sh file
-(needed to run C<./myconfig>), then please mail perlbug@perl.org the
+(needed to run C<./myconfig>), then please open an issue with the
description of how Configure fails along with details of your system
--- for example the output from running C<uname -a>
+-- for example the output from running C<uname -a>.
Please try to make your message brief but clear. Brief, clear bug
reports tend to get answered more quickly. Please don't worry if your
necessary. Do not include a complete transcript of your build
session. Just include the failing commands, the relevant error
messages, and whatever preceding commands are necessary to give the
-appropriate context. Plain text should usually be sufficient -- fancy
-attachments or encodings may actually reduce the number of people who
-read your message. Your message will get relayed to over 400
-subscribers around the world so please try to keep it brief but clear.
+appropriate context.
If the bug you are reporting has security implications which make it
-inappropriate to send to a publicly archived mailing list, then see
+inappropriate to send to a public issue tracker, then see
L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
for details of how to report the issue.
=item Utility Changes
-Changes to installed programs such as F<perlbug> and F<xsubpp> go here. Most
+Changes to installed programs such as F<perldoc> and F<xsubpp> go here. Most
of these are built within the directory F<utils>.
=item New 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>.
+listed in this document. If you find any we have missed, open an issue
+at L<https://github.com/Perl/perl5/issues>.
XXX Changes which significantly change existing files in F<pod/> go here.
However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
=head1 Utility Changes
-XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
+XXX Changes to installed programs such as F<perldoc> and F<xsubpp> go here.
Most of these are built within the directory F<utils>.
[ List utility changes as a =head2 entry for each utility and =item
at L<https://github.com/Perl/perl5/issues>. 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
+inappropriate to send to a public issue tracker, then see
L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
for details of how to report the issue.
information about various types of POD files.
'aux' => [ # utility programs like
- 'h2xs' and 'perlbug' ]
+ 'h2xs' and 'perldoc' ]
'generated' => { # lookup table for generated POD files
like 'perlapi.pod' }
'ignore' => { # lookup table for files to be ignored }
Action (Send/Display/Edit/Subject/Save to File): Q
and carefully examine the output (in F<perlbug.rep]>), especially
-the "Locally applied patches" section. If everything appears okay, then
-delete the file, and try it again, this time actually submitting the bug
-report. Check that it shows up, then remember to close it!
+the "Locally applied patches" section.
=for checklist skip BLEAD-POINT
knitting to rocket science. If you run into trouble, it's quite
likely that someone else has already solved the problem you're
facing. Once you've exhausted the documentation, please report bugs to us
-using the 'perlbug' tool. For more information about perlbug, either type
-'perldoc perlbug' or just 'perlbug' on a line by itself.
+at the GitHub issue tracker at https://github.com/Perl/perl5/issues
While it was current when we made it available, Perl is constantly evolving
and there may be a more recent version that fixes bugs you've run into or
perlbs2000 - building and installing Perl for BS2000.
B<This document needs to be updated, but we don't know what it should say.
-Please email comments to L<perlbug@perl.org|mailto:perlbug@perl.org>.>
+Please submit comments to L<https://github.com/Perl/perl5/issues>.>
=head1 SYNOPSIS
Nicholas Clark <nick@ccl4.org>, collating wisdom supplied by Slaven Rezic
and Tim Bunce.
-Please report any errors, updates, or suggestions to L<mailto:perlbug@perl.org>.
+Please report any errors, updates, or suggestions to
+L<https://github.com/Perl/perl5/issues>.
Jarkko Hietaniemi <jhi@iki.fi>
-Please report any errors, updates, or suggestions to F<perlbug@perl.org>.
+Please report any errors, updates, or suggestions to
+L<https://github.com/Perl/perl5/issues>.
Steve Peters <steve@fisharerojo.org>
-Please report any errors, updates, or suggestions to F<perlbug@perl.org>.
+Please report any errors, updates, or suggestions to
+L<https://github.com/Perl/perl5/issues>.
Support for 64-bit addressing is experimental: some aspects of Perl may be
omitted or buggy. Note the messages output by F<Configure> for further
-information. Please use C<perlbug> to submit a problem report in the
-event that you encounter difficulties.
+information. Please use L<https://github.com/Perl/perl5/issues> to submit a
+problem report in the event that you encounter difficulties.
When building 64-bit modules, it is your responsibility to ensure that linked
external libraries and frameworks provide 64-bit support: if they do not,
Steve Peters <steve@fisharerojo.org>
-Please report any errors, updates, or suggestions to F<perlbug@perl.org>.
+Please report any errors, updates, or suggestions to
+L<https://github.com/Perl/perl5/issues>.
on OS/390 (aka z/OS) Unix System Services.
B<This document needs to be updated, but we don't know what it should say.
-Please email comments to L<perlbug@perl.org|mailto:perlbug@perl.org>.>
+Please submit comments to L<https://github.com/Perl/perl5/issues>.>
=head1 DESCRIPTION
perlos400 - Perl version 5 on OS/400
B<This document needs to be updated, but we don't know what it should say.
-Please email comments to L<perlbug@perl.org|mailto:perlbug@perl.org>.>
+Please submit comments to L<https://github.com/Perl/perl5/issues>.>
=head1 DESCRIPTION
drawing heavily on advice from Alan Burlison, Nick Ing-Simmons, Tim Bunce,
and many other Solaris users over the years.
-Please report any errors, updates, or suggestions to F<perlbug@perl.org>.
+Please report any errors, updates, or suggestions to
+L<https://github.com/Perl/perl5/issues>.
=head1 Reporting Bugs
If you come across what you think might be a bug in Perl, please report
-it. There's a script in PERL_ROOT:[UTILS], perlbug, that walks you through
-the process of creating a bug report. This script includes details of your
-installation, and is very handy. Completed bug reports should go to
-perlbug@perl.org.
+it. The issue tracker at L<https://github.com/Perl/perl5/issues> walks you
+through the process of creating a bug report and including details of your
+installation.
=head1 CAVEATS
If a module does not build for some reason, look carefully for
why it failed, and report problems to the module author. If
it looks like the extension building support is at fault, report
-that with full details of how the build failed using the perlbug
-utility.
+that with full details of how the build failed using the GitHub
+issue tracker at L<https://github.com/Perl/perl5/issues>.
=item Command-line Wildcard Expansion
the same as normal C<perl> on Windows, except that options like C<-h>
don't work (since they need a command-line window to print to).
-If you find bugs in perl, you can run C<perlbug> to create a
-bug report (you may have to send it manually if C<perlbug> cannot
-find a mailer on your system).
+If you find bugs in perl, you can report them to
+L<https://github.com/Perl/perl5/issues>.
=head1 BUGS AND CAVEATS
currently be considered unsupported.
Please send detailed descriptions of any problems and solutions that
-you may find to E<lt>F<perlbug@perl.org>E<gt>, along with the output
-produced by C<perl -V>.
+you may find to E<lt>L<https://github.com/Perl/perl5/issues>E<gt>,
+
along with the output produced by C<perl -V>.
=head1 ACKNOWLEDGEMENTS
tested with at least some version of perl5, but some are still left
over from perl4.
-Please send any problems or suggested changes to perlbug@perl.org.
+Please send any problems or suggested changes to
+L<https://github.com/Perl/perl5/issues>.
=head1 Hint file naming convention.
*) cat <<EOM >&4
I did not know that BSD/OS $osvers supports POSIX threads.
-Feel free to tell perlbug@perl.org otherwise.
+Feel free to tell https://github.com/Perl/perl5/issues otherwise.
EOM
exit 1
;;
0.*|1.*|2.0*|2.1*) cat <<EOM >&4
I did not know that FreeBSD $osvers supports POSIX threads.
-Feel free to tell perlbug@perl.org otherwise.
+Feel free to tell https://github.com/Perl/perl5/issues otherwise.
EOM
exit 1
;;
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.
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>.
+to L<https://github.com/Perl/perl5/issues>.
XXX Changes which significantly change existing files in F<pod/> go here.
However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
=head1 Utility Changes
-XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
+XXX Changes to installed programs such as F<perldoc> and F<xsubpp> go here.
Most of these are built within the directory F<utils>.
[ List utility changes as a =head2 entry for each utility and =item
at L<https://github.com/Perl/perl5/issues>. 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
+inappropriate to send to a public issue tracker, then see
L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
for details of how to report the issue.
(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
(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
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
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,
=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<https://github.com/perl/perl5/issues>.
+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
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
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
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
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
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
=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>
./perl harness
This method pinpoints failed tests automatically.
-If you come up with new tests, please send them to perlbug@perl.org.
+If you come up with new tests, please submit them to
+https://github.com/Perl/perl5/issues.
Tests in the t/base/ directory ought to be runnable with plain miniperl.
That is, they should not require Config.pm nor should they require any
#
# If these tests fail, report the particular incantation you use
# on this platform to find *all* the groups that an arbitrary
-# user may belong to, using the 'perlbug' program.
+# user may belong to, using the issue tracker.
EOM
}
return ( $cmd, $str );
__END__
gave unexpected error $@
Please report the circumstances of this bug in h2xs version $H2XS_VERSION
-using the perlbug script.
+using the issue tracker at https://github.com/Perl/perl5/issues.
EOM
} else {
my $fail;
correctly.
Please report the circumstances of this bug in h2xs version $H2XS_VERSION
-using the perlbug script.
+using the issue tracker at https://github.com/Perl/perl5/issues.
EOM
} else {
unlink $constscfname, $constsxsfname;
=head1 DESCRIPTION
-This program is designed to help you generate and send bug reports
+This program is designed to help you generate bug reports
(and thank-you notes) about perl5 and the modules which ship with it.
In most cases, you can just run it interactively from a command
documentation that came with that distribution to determine the
correct place to report bugs.
-If you are unable to send your report using B<perlbug> (most likely
-because your system doesn't have a way to send mail that perlbug
-recognizes), you may be able to use this tool to compose your report
-and save it to a file which you can then send to B<perlbug@perl.org>
-using your regular mail client.
+Bug reports should be submitted to the GitHub issue tracker at
+L<https://github.com/Perl/perl5/issues>. The B<perlbug@perl.org>
+address no longer automatically opens tickets. You can use this tool
+to compose your report and save it to a file which you can then submit
+to the issue tracker.
In extreme cases, B<perlbug> may not work well enough on your system
to guide you through composing a bug report. In those cases, you
-may be able to use B<perlbug -d> to get system configuration
-information to include in a manually composed bug report to
-B<perlbug@perl.org>.
+may be able to use B<perlbug -d> or B<perl -V> to get system
+configuration information to include in your issue report.
When reporting a bug, please run through this checklist:
If you get a core dump (or equivalent), you may use a debugger
(B<dbx>, B<gdb>, etc) to produce a stack trace to include in the bug
-report.
+report.
NOTE: unless your Perl has been compiled with debug info
(often B<-g>), the stack trace is likely to be somewhat hard to use
If so, that's great news; bug reports with patches are likely to
receive significantly more attention and interest than those without
-patches. Please attach your patch to the report using the C<-p> option.
-When sending a patch, create it using C<git format-patch> if possible,
-though a unified diff created with C<diff -pu> will do nearly as well.
+patches. Please submit your patch via the GitHub Pull Request workflow
+as described in B<perldoc> L<perlhack>. You may also send patches to
+B<perl5-porters@perl.org>. When sending a patch, create it using
+C<git format-patch> if possible, though a unified diff created with
+C<diff -pu> will do nearly as well.
Your patch may be returned with requests for changes, or requests for more
detailed explanations about your fix.
really does work (C<make test>, if the thing you're patching is covered
by Perl's test suite).
-=item Can you use C<perlbug> to submit the report?
-
-B<perlbug> will, amongst other things, ensure your report includes
-crucial information about your version of perl. If C<perlbug> is
-unable to mail your report after you have typed it in, you may have
-to compose the message yourself, add the output produced by C<perlbug
--d> and email it to B<perlbug@perl.org>. If, for some reason, you
-cannot run C<perlbug> at all on your system, be sure to include the
-entire output produced by running C<perl -V> (note the uppercase V).
-
-Whether you use C<perlbug> or send the email manually, please make
-your Subject line informative. "a bug" is not informative. Neither
-is "perl crashes" nor is "HELP!!!". These don't help. A compact
-description of what's wrong is fine.
-
=item Can you use C<perlbug> to submit a thank-you note?
Yes, you can do this by either using the C<-T> option, or by invoking
=back
+Please make your issue title informative. "a bug" is not informative.
+Neither is "perl crashes" nor is "HELP!!!". These don't help. A compact
+description of what's wrong is fine.
+
Having done your bit, please be prepared to wait, to be told the
bug is in your code, or possibly to get no reply at all. The
volunteers who maintain Perl are busy folks, so if your problem is
reply.
If it is important to you that your bug be fixed, do monitor the
-perl5-porters@perl.org mailing list (mailing lists are moderated, your
-message may take a while to show up) and the commit logs to development
+issue tracker (you will be subscribed to notifications for issues you
+submit or comment on) and the commit logs to development
versions of Perl, and encourage the maintainers with kind words or
offers of frosty beverages. (Please do be kind to the maintainers.
Harassing or flaming them is likely to have the opposite effect of the
https://perl5.git.perl.org / perl5.git / commitdiff