X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/fd49642cbd8ecdebdc55e2ae754e108e1a21efcd..8a00c8caf7ac9ccd6bd8eaa8869321108bfef1c6:/utils/perlbug.PL diff --git a/utils/perlbug.PL b/utils/perlbug.PL index c4289f8..f53a009 100644 --- a/utils/perlbug.PL +++ b/utils/perlbug.PL @@ -30,12 +30,19 @@ open PATCH_LEVEL, "<" . catfile(updir, "patchlevel.h") my $patchlevel_date = (stat PATCH_LEVEL)[9]; while () { - last if $_ =~ /^\s*static\s+char.*?local_patches\[\]\s*=\s*{\s*$/; + last if $_ =~ /^\s*static\s+(?:const\s+)?char.*?local_patches\[\]\s*=\s*{\s*$/; +} + +if (! defined($_)) { + warn "Warning: local_patches section not found in patchlevel.h\n"; } my @patches; while () { last if /^\s*}/; + next if /^\s*#/; # preprocessor stuff + next if /PERL_GIT_UNPUSHED_COMMITS/; # XXX exapand instaed + next if /PERL_GIT_UNCOMMITTED_CHANGES/; # XXX exapand instaed chomp; s/^\s+,?\s*"?//; s/"?\s*,?$//; @@ -57,7 +64,7 @@ print "Extracting $file (with variable substitutions)\n"; # In this section, perl variables will be expanded during extraction. # You can use $Config{...} to use Configure variables. -my $extract_version = sprintf("v%vd", $^V); +my $extract_version = sprintf("%vd", $^V); print OUT <<"!GROK!THIS!"; $Config{startperl} @@ -77,21 +84,29 @@ my \@patches = ( print OUT <<'!NO!SUBS!'; +use warnings; +no warnings 'once'; # Eventually, the $::opt_ stuff should get cleaned up +use strict; use Config; use File::Spec; # keep perlbug Perl 5.005 compatible use Getopt::Std; -use strict; +use File::Basename 'basename'; sub paraprint; BEGIN { - eval "use Mail::Send;"; + eval { require Mail::Send;}; $::HaveSend = ($@ eq ""); - eval "use Mail::Util;"; + eval { require Mail::Util; } ; $::HaveUtil = ($@ eq ""); + # use secure tempfiles wherever possible + eval { require File::Temp; }; + $::HaveTemp = ($@ eq ""); + eval { require Module::CoreList; }; + $::HaveCoreList = ($@ eq ""); }; -my $Version = "1.33"; +my $Version = "1.39"; # Changed in 1.06 to skip Mail::Send and Mail::Util if not available. # Changed in 1.07 to see more sendmail execs, and added pipe output. @@ -129,17 +144,36 @@ my $Version = "1.33"; # Changed in 1.31 Add checks on close().Fix my $var unless. TJENNESS 26-07-2000 # Changed in 1.32 Use File::Spec->tmpdir TJENNESS 20-08-2000 # Changed in 1.33 Don't require -t STDOUT for -ok. - -# TODO: - Allow the user to re-name the file on mail failure, and -# make sure failure (transmission-wise) of Mail::Send is -# accounted for. +# Changed in 1.34 Added Message-Id RFOLEY 18-06-2002 +# Changed in 1.35 Use File::Temp (patch from Solar Designer) NWCLARK 28-02-2004 +# Changed in 1.36 Initial Module::CoreList support Alexandr Ciornii 11-07-2007 +# Changed in 1.37 Killed some string evals, rewrote most prose JESSE 2008-06-08 +# Changed in 1.38 Actually enforce the CoreList check, +# Record the module the user enters if they do so +# Refactor prompts to use common code JESSE 2008-06-08 +# Changed in 1.39 Trap mail sending failures (simple ones) so JESSE 2008-06-08 +# users might be able to recover their bug reports +# Refactor mail sending routines +# Unify message building code +# Unify message header building +# Fix "module" prompting to not squish "category" prompting +# use warnings; (except 'once' warnings) +# Unified report fingerprint/change detection code +# Removed some labeled 'gotos' +#TODO: +# make sure failure (transmission-wise) of Mail::Send is accounted for. +# (This may work now. Unsure of the original author's issue -JESSE 2008-06-08) # - Test -b option -my( $file, $usefile, $cc, $address, $perlbug, $testaddress, $filename, - $subject, $from, $verbose, $ed, $outfile, $Is_MacOS, $category, $severity, - $fh, $me, $Is_MSWin32, $Is_VMS, $msg, $body, $andcc, %REP, $ok); +my( $file, $usefile, $cc, $address, $bugaddress, $testaddress, $thanksaddress, + $filename, $messageid, $domain, $subject, $from, $verbose, $ed, $outfile, + $fh, $me, $body, $andcc, %REP, $ok, $thanks, $progname, + $Is_MacOS, $Is_MSWin32, $Is_Linux, $Is_VMS, $Is_OpenBSD, + $report_about_module, $category, $severity, + +); -my $perl_version = $^V ? sprintf("v%vd", $^V) : $]; +my $perl_version = $^V ? sprintf("%vd", $^V) : $]; my $config_tag2 = "$perl_version - $Config{cf_time}"; @@ -148,8 +182,8 @@ Init(); if ($::opt_h) { Help(); exit; } if ($::opt_d) { Dump(*STDOUT); exit; } if (!-t STDIN && !($ok and not $::opt_n)) { - paraprint < { 'default' => 'core', 'ok' => 'install', + # Inevitably some of these will end up in RT whatever we do: + 'thanks' => 'thanks', 'opts' => [qw(core docs install library utilities)], # patch, notabug }, 'severity' => { 'default' => 'low', 'ok' => 'none', + 'thanks' => 'none', 'opts' => [qw(critical high medium low wishlist none)], # zero }, ); - die "Invalid alternative($name) requested\n" unless grep(/^$name$/, keys %alts); + die "Invalid alternative ($name) requested\n" unless grep(/^$name$/, keys %alts); my $alt = ""; - if ($ok) { - $alt = $alts{$name}{'ok'}; + my $what = $ok || $thanks; + if ($what) { + $alt = $alts{$name}{$what}; } else { my @alts = @{$alts{$name}{'opts'}}; + print "\n\n"; paraprint < 5) { die "Invalid $name: aborting.\n"; } - print "Please enter a \u$name [$alts{$name}{'default'}]: "; - $alt = <>; - chomp $alt; - if ($alt =~ /^\s*$/) { - $alt = $alts{$name}{'default'}; - } + $alt = _prompt('', "\u$name", $alts{$name}{'default'}); + $alt ||= $alts{$name}{'default'}; } while !((($alt) = grep(/^$alt/i, @alts))); } lc $alt; @@ -209,13 +252,15 @@ sub Init { $Is_MSWin32 = $^O eq 'MSWin32'; $Is_VMS = $^O eq 'VMS'; + $Is_Linux = lc($^O) eq 'linux'; + $Is_OpenBSD = lc($^O) eq 'openbsd'; $Is_MacOS = $^O eq 'MacOS'; @ARGV = split m/\s+/, - MacPerl::Ask('Provide command-line args here (-h for help):') + MacPerl::Ask('Provide command line args here (-h for help):') if $Is_MacOS && $MacPerl::Version =~ /App/; - if (!getopts("Adhva:s:b:f:F:r:e:SCc:to:n:")) { Help(); exit; }; + if (!getopts("Adhva:s:b:f:F:r:e:SCc:to:n:T")) { Help(); exit; }; # This comment is needed to notify metaconfig that we are # using the $perladmin, $cf_by, and $cf_time definitions. @@ -223,13 +268,28 @@ sub Init { # -------- Configuration --------- # perlbug address - $perlbug = 'perlbug@perl.org'; + $bugaddress = 'perlbug@perl.org'; # Test address - $testaddress = 'perlbug-test@perl.com'; + $testaddress = 'perlbug-test@perl.org'; + + # Thanks address + $thanksaddress = 'perl-thanks@perl.org'; + if (basename ($0) =~ /^perlthanks/i) { + # invoked as perlthanks + $::opt_T = 1; + $::opt_C = 1; # don't send a copy to the local admin + } + + if ($::opt_T) { + $thanks = 'thanks'; + } + + $progname = $thanks ? 'perlthanks' : 'perlbug'; # Target address - $address = $::opt_a || ($::opt_t ? $testaddress : $perlbug); + $address = $::opt_a || ($::opt_t ? $testaddress + : $thanks ? $thanksaddress : $bugaddress); # Users address, used in message and in Reply-To header $from = $::opt_r || ""; @@ -251,7 +311,7 @@ sub Init { # Body of report $body = $::opt_b || ""; - + # Editor $ed = $::opt_e || $ENV{VISUAL} || $ENV{EDITOR} || $ENV{EDIT} || ($Is_VMS && "edit/tpu") @@ -270,7 +330,7 @@ sub Init { } # OK - send "OK" report for build on this system - $ok = 0; + $ok = ''; if ($::opt_o) { if ($::opt_o eq 'k' or $::opt_o eq 'kay') { my $age = time - $patchlevel_date; @@ -295,7 +355,7 @@ EOF $subject = ($::opt_n ? 'Not ' : '') . "OK: perl $perl_version ${patch_tags}on" ." $::Config{'archname'} $::Config{'osvers'} $subject"; - $ok = 1; + $ok = 'ok'; } else { Help(); exit(); @@ -313,6 +373,18 @@ EOF || $::Config{'cf_email'} || $::Config{'cf_by'} ); + if ($::HaveUtil) { + $domain = Mail::Util::maildomain(); + } elsif ($Is_MSWin32) { + $domain = $ENV{'USERDOMAIN'}; + } else { + require Sys::Hostname; + $domain = Sys::Hostname::hostname(); + } + + # Message-Id - rjsf + $messageid = "<$::Config{'version'}_${$}_".time."\@$domain>"; + # My username $me = $Is_MSWin32 ? $ENV{'USERNAME'} : $^O eq 'os2' ? $ENV{'USER'} || $ENV{'LOGNAME'} @@ -327,40 +399,60 @@ EOF sub Query { # Explain what perlbug is unless ($ok) { - paraprint <; + } my $err = 0; - while ($subject !~ /\S/) { - print "\nPlease enter a subject: "; - $subject = <>; - if ($err++ > 5) { - die "Aborting.\n"; + do { + $subject = _prompt('','Subject'); + if ($err++ == 5) { + if ($thanks) { + $subject = 'Thanks for Perl'; + } else { + die "Aborting.\n"; + } } - } - chop $subject; + } while (TrivialSubject($subject)); } # Prompt for return address, if needed @@ -377,16 +469,8 @@ EOF } unless ($guess) { - my $domain; - if ($::HaveUtil) { - $domain = Mail::Util::maildomain(); - } elsif ($Is_MSWin32) { - $domain = $ENV{'USERDOMAIN'}; - } else { - require Sys::Hostname; - $domain = Sys::Hostname::hostname(); - } - if ($domain) { + # move $domain to where we can use it elsewhere + if ($domain) { if ($Is_VMS && !$::Config{'d_socket'}) { $guess = "$domain\:\:$me"; } else { @@ -398,14 +482,17 @@ EOF if ($guess) { unless ($ok) { paraprint <; - chop $from; + $from = _prompt('','Your address',$guess); $from = $guess if $from eq ''; } } @@ -428,15 +513,12 @@ EOF # Prompt for administrator address, unless an override was given if( !$::opt_C and !$::opt_c ) { - paraprint <; - chop $entry; + my $entry = _prompt($description, "Local perl administrator", $cc); if ($entry ne "") { $cc = $entry; @@ -445,37 +527,59 @@ EOF } $cc = '' if $cc =~ /^(none|yourself|me|myself|ourselves)$/i; - $andcc = " and $cc" if $cc; + if ($cc) { + $andcc = " and $cc" + } else { + $andcc = '' + } # Prompt for editor, if no override is given editor: unless ($::opt_e || $::opt_f || $::opt_b) { - paraprint <; - chop $entry; + if ($thanks) { + $description = <<"EOF"; +It's now time to compose your thank-you message. + +Some information about your local perl configuration will automatically +be included at the end of your message, because we're curious about +the different ways that people build and use perl. If you'd rather +not share this information, you're welcome to delete it. + +$common_end +EOF + } else { + $description = <<"EOF"; +It's now time to compose your bug report. Try to make the report +concise but descriptive. Please include any detail which you think +might be relevant or might help the volunteers working to improve +perl. If you are reporting something that does not work as you think +it should, please try to include examples of the actual result and of +what you expected. + +Some information about your local perl configuration will automatically +be included at the end of your report. If you are using an unusual +version of perl, it would be useful if you could confirm that you +can replicate the problem on a standard build of perl as well. + +$common_end +EOF + } + + my $entry = _prompt($description, "Editor", $ed); $usefile = 0; if ($entry eq "file") { $usefile = 1; @@ -483,6 +587,40 @@ EOF $ed = $entry; } } + if ($::HaveCoreList && !$ok && !$thanks) { + my $description = <first_release($entry); + if ($entry and not $first_release) { + paraprint <; - chop $entry; + my $entry = _prompt($description, "Filename"); if ($entry eq "") { paraprint <$filename") or die "Unable to create report file `$filename': $!\n"; - my $reptype = !$ok ? "bug" : $::opt_n ? "build failure" : "success"; + open(REP,">$filename") or die "Unable to create report file '$filename': $!\n"; + my $reptype = !$ok ? ($thanks ? 'thank-you' : 'bug') + : $::opt_n ? "build failure" : "success"; print REP <) { print REP $_ } - close(F) or die "Error closing `$file': $!"; + close(F) or die "Error closing '$file': $!"; } else { - print REP <) { - s/\s+//g; - $REP{$_}++; - } - close(REP) or die "Error closing report file `$filename': $!"; + # Set up an initial report fingerprint so we can compare it later + _fingerprint_lines_in_report(); + } # sub Query sub Dump { @@ -575,6 +722,12 @@ Flags: category=$category severity=$severity EFF + + if ($report_about_module ) { + print OUT <; - chop $entry; + my $description = "Please make sure that the name of the editor you want to use is correct."; + my $entry = _prompt($description, 'Editor', $ed); $ed = $entry unless $entry eq ''; } -tryagain: - my $sts; - $sts = system("$ed $filename") unless $Is_MacOS; - if ($Is_MacOS) { - require ExtUtils::MakeMaker; - ExtUtils::MM_MacOS::launch_file($filename); - paraprint <; - } - if ($sts) { - paraprint <; - chop $entry; + return; + } + } + } + return if ( $ok and not $::opt_n ) || $body; - if ($entry ne "") { - $ed = $entry; - goto tryagain; - } else { - paraprint <etry dit + next; + } elsif ( $action =~ /^[cq]/i ) { # ancel, uit + Cancel(); # cancel exits + } + } + # Ok. the user did what they needed to; + return; - return if ($ok and not $::opt_n) || $body; - # Check that we have a report that has some, eh, report in it. - my $unseen = 0; - - open(REP, "<$filename") or die "Couldn't open `$filename': $!\n"; - # a strange way to check whether any significant editing - # have been done: check whether any new non-empty lines - # have been added. Yes, the below code ignores *any* space - # in *any* line. - while () { - s/\s+//g; - $unseen++ if $_ ne '' and not exists $REP{$_}; } +} - while ($unseen == 0) { - paraprint <); - if ($action =~ /^[re]/i) { # etry dit - goto tryagain; - } elsif ($action =~ /^[cq]/i) { # ancel, uit - Cancel(); - } - } -} # sub Edit sub Cancel { 1 while unlink($filename); # remove all versions under VMS - print "\nCancelling.\n"; + print "\nQuitting without sending your message.\n"; exit(0); } @@ -719,57 +865,47 @@ sub NowWhat { # Report is done, prompt for further action if( !$::opt_S ) { while(1) { - paraprint <; - chop $action; - + print $menu; + my $action = _prompt('', "Action (Send/Display/Edit/Subject/Save to File)");; + print "\n"; if ($action =~ /^(f|sa)/i) { # ile/ve - my $file_save = $outfile || "perlbug.rep"; - print "\n\nName of file to save message in [$file_save]: "; - my $file = scalar <>; - chop $file; - $file = $file_save if $file eq ""; - - unless (open(FILE, ">$file")) { - print "\nError opening $file: $!\n\n"; - goto retry; - } - open(REP, "<$filename") or die "Couldn't open file `$filename': $!\n"; - print FILE "To: $address\nSubject: $subject\n"; - print FILE "Cc: $cc\n" if $cc; - print FILE "Reply-To: $from\n" if $from; - print FILE "\n"; - while () { print FILE } - close(REP) or die "Error closing report file `$filename': $!"; - close(FILE) or die "Error closing $file: $!"; - - print "\nMessage saved in `$file'.\n"; - exit; + if ( SaveMessage() ) { exit } } elsif ($action =~ /^(d|l|sh)/i ) { # isplay, ist, ow # Display the message - open(REP, "<$filename") or die "Couldn't open file `$filename': $!\n"; + open(REP, "<$filename") or die "Couldn't open file '$filename': $!\n"; while () { print $_ } - close(REP) or die "Error closing report file `$filename': $!"; + close(REP) or die "Error closing report file '$filename': $!"; + } elsif ($action =~ /^su/i) { # bject + my $reply = _prompt( "Subject: $subject", "If the above subject is fine, press Enter. Otherwise, type a replacement now\nSubject"); + if ($reply ne '') { + unless (TrivialSubject($reply)) { + $subject = $reply; + print "Subject: $subject\n"; + } + } } elsif ($action =~ /^se/i) { # end # Send the message - print "Are you certain you want to send this message?\n" - . 'Please type "yes" if you are: '; - my $reply = scalar ; - chop $reply; - if ($reply eq "yes") { + my $reply = _prompt( "Are you certain you want to send this message?", 'Please type "yes" if you are','no'); + if ($reply =~ /^yes$/) { last; } else { paraprint <dit, e-edit @@ -779,105 +915,82 @@ EOF Cancel(); } elsif ($action =~ /^s/i) { paraprint <$outfile" or die "Couldn't open '$outfile': $!\n"; - goto sendout; +sub TrivialSubject { + my $subject = shift; + if ($subject =~ + /^(y(es)?|no?|help|perl( (bug|problem))?|bug|problem)$/i || + length($subject) < 4 || + $subject !~ /\s/) { + print "\nThe subject you entered wasn't very descriptive. Please try again.\n\n"; + return 1; + } else { + return 0; } - if ($::HaveSend) { - $msg = new Mail::Send Subject => $subject, To => $address; - $msg->cc($cc) if $cc; - $msg->add("Reply-To",$from) if $from; - - $fh = $msg->open; - open(REP, "<$filename") or die "Couldn't open `$filename': $!\n"; - while () { print $fh $_ } - close(REP) or die "Error closing $filename: $!"; - $fh->close; - - print "\nMessage sent.\n"; - } elsif ($Is_VMS) { - if ( ($address =~ /@/ and $address !~ /^\w+%"/) or - ($cc =~ /@/ and $cc !~ /^\w+%"/) ) { - my $prefix; - foreach (qw[ IN MX SMTP UCX PONY WINS ], '') { - $prefix = "$_%", last if $ENV{"MAIL\$PROTOCOL_$_"}; - } - $address = qq[${prefix}"$address"] unless $address =~ /^\w+%"/; - $cc = qq[${prefix}"$cc"] unless !$cc || $cc =~ /^\w+%"/; - } - $subject =~ s/"/""/g; $address =~ s/"/""/g; $cc =~ s/"/""/g; - my $sts = system(qq[mail/Subject="$subject" $filename. "$address","$cc"]); - if ($sts) { - die <) { print SENDMAIL $_ } - close(REP) or die "Error closing $filename: $!"; - - if (close(SENDMAIL)) { - printf "\nMessage %s.\n", $outfile ? "saved" : "sent"; - } else { - warn "\nSendmail returned status '", $? >> 8, "'\n"; - } + SaveMessage(); + return; } - 1 while unlink($filename); # remove all versions under VMS -} # sub Send + + 1 while unlink($filename); # remove all versions under VMS +} # sub Send sub Help { print <tmpdir(); - $filename = "bugrep0$$"; - $filename++ while -e File::Spec->catfile($dir, $filename); - $filename = File::Spec->catfile($dir, $filename); + if ($::HaveTemp) { + # Good. Use a secure temp file + my ($fh, $filename) = File::Temp::tempfile(UNLINK => 1); + close($fh); + return $filename; + } else { + # Bah. Fall back to doing things less securely. + my $dir = File::Spec->tmpdir(); + $filename = "bugrep0$$"; + $filename++ while -e File::Spec->catfile($dir, $filename); + $filename = File::Spec->catfile($dir, $filename); + } } sub paraprint { my @paragraphs = split /\n{2,}/, "@_"; - print "\n\n"; for (@paragraphs) { # implicit local $_ s/(\S)\s*\n/$1 /g; write; @@ -930,6 +1051,160 @@ sub paraprint { } } +sub _prompt { + my ($explanation, $prompt, $default) = (@_); + if ($explanation) { + print "\n\n"; + paraprint $explanation; + } + print $prompt. ($default ? " [$default]" :''). ": "; + my $result = scalar(<>); + chomp($result); + $result =~ s/^\s*(.*?)\s*$/$1/s; + if ($default && $result eq '') { + return $default; + } else { + return $result; + } +} + +sub _build_header { + my %attr = (@_); + + my $head = ''; + for my $header (keys %attr) { + $head .= "$header: ".$attr{$header}."\n"; + } + return $head; +} + +sub _message_headers { + my %headers = ( To => $address, Subject => $subject ); + $headers{'Cc'} = $cc if ($cc); + $headers{'Message-Id'} = $messageid if ($messageid); + $headers{'Reply-To'} = $from if ($from); + return \%headers; +} + +sub build_complete_message { + my $content = _build_header(%{_message_headers()}) . "\n\n"; + open( REP, "<$filename" ) or die "Couldn't open file '$filename': $!\n"; + while () { $content .= $_; } + close(REP) or die "Error closing report file '$filename': $!"; + return $content; +} + +sub save_message_to_disk { + my $file = shift; + + open OUTFILE, ">$file" or do { warn "Couldn't open '$file': $!\n"; return undef}; + print OUTFILE build_complete_message(); + close(OUTFILE) or do { warn "Error closing $file: $!"; return undef }; + print "\nMessage saved.\n"; + return 1; +} + +sub _send_message_vms { + if ( ( $address =~ /@/ and $address !~ /^\w+%"/ ) + or ( $cc =~ /@/ and $cc !~ /^\w+%"/ ) ) { + my $prefix; + foreach ( qw[ IN MX SMTP UCX PONY WINS ], '' ) { + $prefix = "$_%", last if $ENV{"MAIL\$PROTOCOL_$_"}; + } + $address = qq[${prefix}"$address"] unless $address =~ /^\w+%"/; + $cc = qq[${prefix}"$cc"] unless !$cc || $cc =~ /^\w+%"/; + } + $subject =~ s/"/""/g; + $address =~ s/"/""/g; + $cc =~ s/"/""/g; + my $sts = system(qq[mail/Subject="$subject" $filename. "$address","$cc"]); + if ($sts) { + die "Can't spawn off mail (leaving bug report in $filename): $sts"; + } +} + +sub _send_message_mailsend { + my $msg = Mail::Send->new(); + my %headers = %{_message_headers()}; + for my $key ( keys %headers) { + $msg->add($key => $headers{$key}); + } + + $fh = $msg->open; + open(REP, "<$filename") or die "Couldn't open '$filename': $!\n"; + while () { print $fh $_ } + close(REP) or die "Error closing $filename: $!"; + $fh->close; + + print "\nMessage sent.\n"; +} + +sub _probe_for_sendmail { + my $sendmail = ""; + for (qw(/usr/lib/sendmail /usr/sbin/sendmail /usr/ucblib/sendmail)) { + $sendmail = $_, last if -e $_; + } + if ( $^O eq 'os2' and $sendmail eq "" ) { + my $path = $ENV{PATH}; + $path =~ s:\\:/:; + my @path = split /$Config{'path_sep'}/, $path; + for (@path) { + $sendmail = "$_/sendmail", last if -e "$_/sendmail"; + $sendmail = "$_/sendmail.exe", last if -e "$_/sendmail.exe"; + } + } + return $sendmail; +} + +sub _send_message_sendmail { + my $sendmail = _probe_for_sendmail(); + unless ($sendmail) { + paraprint(<<"EOF"), die "\n"; +It appears that there is no program which looks like "sendmail" on +your system and that the Mail::Send library from CPAN isn't available. +Because of this, there's no easy way to automatically send your +message. + +A copy of your message has been saved in '$filename' for you to +send to '$address' with your normal mail client. +EOF + } + + open( SENDMAIL, "|$sendmail -t -oi" ) + || die "'|$sendmail -t -oi' failed: $!"; + print SENDMAIL build_complete_message(); + if ( close(SENDMAIL) ) { + print "\nMessage sent\n"; + } else { + warn "\nSendmail returned status '", $? >> 8, "'\n"; + } +} + + + +# a strange way to check whether any significant editing +# has been done: check whether any new non-empty lines +# have been added. + +sub _fingerprint_lines_in_report { + my $new_lines = 0; + # read in the report template once so that + # we can track whether the user does any editing. + # yes, *all* whitespace is ignored. + + open(REP, "<$filename") or die "Unable to open report file '$filename': $!\n"; + while (my $line = ) { + $line =~ s/\s+//g; + $new_lines++ if (!$REP{$line}); + + } + close(REP) or die "Error closing report file '$filename': $!"; + # returns the number of lines with content that wasn't there when last we looked + return $new_lines; +} + + + format STDOUT = ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ~~ $_ @@ -943,36 +1218,48 @@ perlbug - how to submit bug reports on Perl =head1 SYNOPSIS +B + B S<[ B<-v> ]> S<[ B<-a> I
]> S<[ B<-s> I ]> S<[ B<-b> I | B<-f> I ]> S<[ B<-F> I ]> S<[ B<-r> I ]> S<[ B<-e> I ]> S<[ B<-c> I | B<-C> ]> -S<[ B<-S> ]> S<[ B<-t> ]> S<[ B<-d> ]> S<[ B<-A> ]> S<[ B<-h> ]> +S<[ B<-S> ]> S<[ B<-t> ]> S<[ B<-d> ]> S<[ B<-A> ]> S<[ B<-h> ]> S<[ B<-T> ]> B S<[ B<-v> ]> S<[ B<-r> I ]> S<[ B<-A> ]> S<[ B<-ok> | B<-okay> | B<-nok> | B<-nokay> ]> +B + =head1 DESCRIPTION -A program to help generate bug reports about perl or the modules that -come with it, and mail them. -If you have found a bug with a non-standard port (one that was not part -of the I), a binary distribution, or a -non-standard module (such as Tk, CGI, etc), then please see the -documentation that came with that distribution to determine the correct -place to report bugs. +This program is designed to help you generate and send 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 +line without any special arguments and follow the prompts. + +If you have found a bug with a non-standard port (one that was not +part of the I), a binary distribution, or a +non-core module (such as Tk, DBI, etc), then please see the +documentation that came with that distribution to determine the +correct place to report bugs. -C is designed to be used interactively. Normally no arguments -will be needed. Simply run it, and follow the prompts. +If you are unable to send your report using B (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 +using your regular mail client. -If you are unable to run B (most likely because you don't have -a working setup to send mail that perlbug recognizes), you may have to -compose your own report, and email it to B. You might -find the B<-d> option useful to get summary information in that case. +In extreme cases, B 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 to get system configuration +information to include in a manually composed bug report to +B. -In any case, when reporting a bug, please make sure you have run through -this checklist: + +When reporting a bug, please run through this checklist: =over 4 @@ -982,110 +1269,142 @@ Type C at the command line to find out. =item Are you running the latest released version of perl? -Look at http://www.perl.com/ to find out. If it is not the latest -released version, get that one and see whether your bug has been -fixed. Note that bug reports about old versions of Perl, especially -those prior to the 5.0 release, are likely to fall upon deaf ears. -You are on your own if you continue to use perl1 .. perl4. +Look at http://www.perl.org/ to find out. If you are not using the +latest released version, please try to replicate your bug on the +latest stable release. + +Note that reports about bugs in old versions of Perl, especially +those which indicate you haven't also tested the current stable +release of Perl, are likely to receive less attention from the +volunteers who build and maintain Perl than reports about bugs in +the current release. + +This tool isn't apropriate for reporting bugs in any version +prior to Perl 5.0. =item Are you sure what you have is a bug? -A significant number of the bug reports we get turn out to be documented -features in Perl. Make sure the behavior you are witnessing doesn't fall -under that category, by glancing through the documentation that comes -with Perl (we'll admit this is no mean task, given the sheer volume of -it all, but at least have a look at the sections that I relevant). +A significant number of the bug reports we get turn out to be +documented features in Perl. Make sure the issue you've run into +isn't intentional by glancing through the documentation that comes +with the Perl distribution. -Be aware of the familiar traps that perl programmers of various hues -fall into. See L. +Given the sheer volume of Perl documentation, this isn't a trivial +undertaking, but if you can point to documentation that suggests +the behaviour you're seeing is I, your issue is likely to +receive more attention. You may want to start with B +L for pointers to common traps that new (and experienced) +Perl programmers run into. -Check in L to see what any Perl error message(s) mean. -If message isn't in perldiag, it probably isn't generated by Perl. -Consult your operating system documentation instead. +If you're unsure of the meaning of an error message you've run +across, B L for an explanation. If the message +isn't in perldiag, it probably isn't generated by Perl. You may +have luck consulting your operating system documentation instead. -If you are on a non-UNIX platform check also L, as some +If you are on a non-UNIX platform B L, as some features may be unimplemented or work differently. -Try to study the problem under the Perl debugger, if necessary. -See L. +You may be able to figure out what's going wrong using the Perl +debugger. For information about how to use the debugger B +L. =item Do you have a proper test case? The easier it is to reproduce your bug, the more likely it will be -fixed, because if no one can duplicate the problem, no one can fix it. -A good test case has most of these attributes: fewest possible number -of lines; few dependencies on external commands, modules, or -libraries; runs on most platforms unimpeded; and is self-documenting. +fixed -- if nobody can duplicate your problem, it probably won't be +addressed. + +A good test case has most of these attributes: short, simple code; +few dependencies on external commands, modules, or libraries; no +platform-dependent code (unless it's a platform-specific bug); +clear, simple documentation. -A good test case is almost always a good candidate to be on the perl -test suite. If you have the time, consider making your test case so -that it will readily fit into the standard test suite. +A good test case is almost always a good candidate to be included in +Perl's test suite. If you have the time, consider writing your test case so +that it can be easily included into the standard test suite. -Remember also to include the B error messages, if any. -"Perl complained something" is not an exact error message. +=item Have you included all relevant information? + +Be sure to include the B error messages, if any. +"Perl gave an error" is not an exact error message. If you get a core dump (or equivalent), you may use a debugger (B, B, etc) to produce a stack trace to include in the bug -report. NOTE: unless your Perl has been compiled with debug info +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 because it will most probably contain only the function names and not their arguments. If possible, recompile your Perl with debug info and -reproduce the dump and the stack trace. +reproduce the crash and the stack trace. =item Can you describe the bug in plain English? -The easier it is to understand a reproducible bug, the more likely it -will be fixed. Anything you can provide by way of insight into the -problem helps a great deal. In other words, try to analyze the -problem (to the extent you can) and report your discoveries. +The easier it is to understand a reproducible bug, the more likely +it will be fixed. Any insight you can provide into the problem +will help a great deal. In other words, try to analyze the problem +(to the extent you can) and report your discoveries. =item Can you fix the bug yourself? A bug report which I will almost -definitely be fixed. Use the C program to generate your patches -(C is being maintained by the GNU folks as part of the B -package, so you should be able to get it from any of the GNU software -repositories). If you do submit a patch, the cool-dude counter at -perlbug@perl.org will register you as a savior of the world. Your -patch may be returned with requests for changes, or requests for more +definitely be fixed. When sending a patch, please use the C +program with the C<-u> option to generate "unified" diff files. +Bug reports with patches are likely to receive significantly more +attention and interest than those without patches. + +Your patch may be returned with requests for changes, or requests for more detailed explanations about your fix. -Here are some clues for creating quality patches: Use the B<-c> or -B<-u> switches to the diff program (to create a so-called context or -unified diff). Make sure the patch is not reversed (the first -argument to diff is typically the original file, the second argument -your changed file). Make sure you test your patch by applying it with -the C program before you send it on its way. Try to follow the -same style as the code you are trying to patch. Make sure your patch -really does work (C, if the thing you're patching supports -it). +Here are a few hints for creating high-quality patches: + +Make sure the patch is not reversed (the first argument to diff is +typically the original file, the second argument your changed file). +Make sure you test your patch by applying it with the C +program before you send it on its way. Try to follow the same style +as the code you are trying to patch. Make sure your patch really +does work (C, if the thing you're patching is covered +by Perl's test suite). =item Can you use C to submit the report? B will, amongst other things, ensure your report includes -crucial information about your version of perl. If C 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 and email -it to B. If, for some reason, you cannot run -C at all on your system, be sure to include the entire output -produced by running C (note the uppercase V). +crucial information about your version of perl. If C 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 and email it to B. If, for some reason, you +cannot run C at all on your system, be sure to include the +entire output produced by running C (note the uppercase V). Whether you use C or send the email manually, please make -your Subject line informative. "a bug" not informative. Neither is -"perl crashes" nor "HELP!!!". These don't help. -A compact description of what's wrong is fine. +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 to submit a thank-you note? + +Yes, you can do this by either using the C<-T> option, or by invoking +the program as C. Thank-you notes are good. It makes people +smile. =back -Having done your bit, please be prepared to wait, to be told the bug -is in your code, or even to get no reply at all. The Perl maintainers -are busy folks, so if your problem is a small one or if it is difficult -to understand or already known, they may not respond with a personal reply. +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 +an obvious bug in your own code, is difficult to understand or is +a duplicate of an existing report, you may not receive a personal +reply. + If it is important to you that your bug be fixed, do monitor the -C file in any development releases since the time you submitted -the bug, and encourage the maintainers with kind words (but never any -flames!). Feel free to resend your bug report if the next released -version of perl comes out and your bug is still present. +perl5-porters@perl.org mailing list 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 one you want.) + +Feel free to update the ticket about your bug on http://rt.perl.org +if a new version of Perl is released and your bug is still present. =head1 OPTIONS @@ -1093,7 +1412,7 @@ version of perl comes out and your bug is still present. =item B<-a> -Address to send the report to. Defaults to `perlbug@perl.org'. +Address to send the report to. Defaults to B. =item B<-A> @@ -1185,7 +1504,11 @@ supply one on the command line. =item B<-t> -Test mode. The target address defaults to `perlbug-test@perl.com'. +Test mode. The target address defaults to B. + +=item B<-T> + +Send a thank-you note instead of a bug report. =item B<-v> @@ -1195,15 +1518,16 @@ Include verbose configuration data in the report. =head1 AUTHORS -Kenneth Albanowski (Ekjahds@kjahds.comE), subsequently Itored -by Gurusamy Sarathy (Egsar@activestate.comE), Tom Christiansen -(Etchrist@perl.comE), Nathan Torkington (Egnat@frii.comE), -Charles F. Randall (Ecfr@pobox.comE), Mike Guy -(Emjtg@cam.a.ukE), Dominic Dunlop (Edomo@computer.orgE), -Hugo van der Sanden (Ehv@crypt0.demon.co.ukE), +Kenneth Albanowski (Ekjahds@kjahds.comE), subsequently +Itored by Gurusamy Sarathy (Egsar@activestate.comE), +Tom Christiansen (Etchrist@perl.comE), Nathan Torkington +(Egnat@frii.comE), Charles F. Randall (Ecfr@pobox.comE), +Mike Guy (Emjtg@cam.a.ukE), Dominic Dunlop +(Edomo@computer.orgE), Hugo van der Sanden (Ehv@crypt.org), Jarkko Hietaniemi (Ejhi@iki.fiE), Chris Nandor (Epudge@pobox.comE), Jon Orwant (Eorwant@media.mit.eduE, -and Richard Foley (Erichard@rfi.netE). +Richard Foley (Erichard.foley@rfi.netE), and Jesse Vincent +(Ejesse@bestpractical.com). =head1 SEE ALSO