4 use File::Basename qw(&basename &dirname);
6 # List explicitly here the variables you want Configure to
7 # generate. Metaconfig only looks for shell variables, so you
8 # have to mention them as if they were shell variables, not
9 # %Config entries. Thus you write
11 # to ensure Configure will look for $Config{startperl}.
13 # This forces PL files to create target in same directory as PL file.
14 # This is so that make depend always knows where to find PL derivatives.
16 $file = basename($0, '.PL');
17 $file .= '.com' if $^O eq 'VMS';
19 open OUT,">$file" or die "Can't create $file: $!";
21 print "Extracting $file (with variable substitutions)\n";
23 # In this section, perl variables will be expanded during extraction.
24 # You can use $Config{...} to use Configure variables.
26 print OUT <<"!GROK!THIS!";
28 eval 'exec $Config{perlpath} -S \$0 \${1+"\$@"}'
29 if \$running_under_some_shell;
32 # In the following, perl variables are not expanded during extraction.
34 print OUT <<'!NO!SUBS!';
40 eval "use Mail::Send;";
41 $::HaveSend = ($@ eq "");
42 eval "use Mail::Util;";
43 $::HaveUtil = ($@ eq "");
52 my($Version) = "1.18";
54 # Changed in 1.06 to skip Mail::Send and Mail::Util if not available.
55 # Changed in 1.07 to see more sendmail execs, and added pipe output.
56 # Changed in 1.08 to use correct address for sendmail.
57 # Changed in 1.09 to close the REP file before calling it up in the editor.
58 # Also removed some old comments duplicated elsewhere.
59 # Changed in 1.10 to run under VMS without Mail::Send; also fixed
60 # temp filename generation.
61 # Changed in 1.11 to clean up some text and removed Mail::Send deactivator.
62 # Changed in 1.12 to check for editor errors, make save/send distinction
63 # clearer and add $ENV{REPLYTO}.
64 # Changed in 1.13 to hopefully make it more difficult to accidentally
66 # Changed in 1.14 to make the prompts a little more clear on providing
67 # helpful information. Also let file read fail gracefully.
68 # Changed in 1.15 to add warnings to stop people using perlbug for non-bugs.
69 # Also report selected environment variables.
70 # Changed in 1.16 to include @INC, and allow user to re-edit if no changes.
71 # Changed in 1.17 Win32 support added. GSAR 97-04-12
72 # Changed in 1.18 add '-ok' option for reporting build success. CFR 97-06-18
74 # TODO: - Allow the user to re-name the file on mail failure, and
75 # make sure failure (transmission-wise) of Mail::Send is
79 my( $file, $usefile, $cc, $address, $perlbug, $testaddress, $filename,
80 $subject, $from, $verbose, $ed,
81 $fh, $me, $Is_MSWin32, $Is_VMS, $msg, $body, $andcc, %REP, $ok);
85 if($::opt_h) { Help(); exit; }
89 Please use perlbug interactively. If you want to
90 include a file, you can use the -f switch.
95 if($::opt_d or !-t STDOUT) { Dump(*STDOUT); exit; }
98 Edit() unless $usefile;
106 # -------- Setup --------
108 $Is_MSWin32 = $^O eq 'MSWin32';
109 $Is_VMS = $^O eq 'VMS';
111 getopts("dhva:s:b:f:r:e:SCc:to:");
114 # This comment is needed to notify metaconfig that we are
115 # using the $perladmin, $cf_by, and $cf_time definitions.
118 # -------- Configuration ---------
121 $perlbug = 'perlbug@perl.com';
125 $testaddress = 'perlbug-test@perl.com';
128 $address = $::opt_a || ($::opt_t ? $testaddress : $perlbug);
130 # Users address, used in message and in Reply-To header
131 $from = $::opt_r || "";
133 # Include verbose configuration information
134 $verbose = $::opt_v || 0;
136 # Subject of bug-report message
137 $subject = $::opt_s || "";
140 $usefile = ($::opt_f || 0);
142 # File to send as report
143 $file = $::opt_f || "";
146 $body = $::opt_b || "";
149 $ed = ( $::opt_e || $ENV{VISUAL} || $ENV{EDITOR} || $ENV{EDIT} ||
150 ($Is_VMS ? "edit/tpu" : $Is_MSWin32 ? "notepad" : "vi")
153 # OK - send "OK" report for build on this system
156 if ( $::opt_o eq 'k' ) {
157 # force these options
158 $::opt_S = 1; # don't prompt for send
159 $::opt_C = 1; # don't send a copy to the local admin
160 $::opt_v = 1; $verbose = 1;
161 $::opt_s = 1; $subject = "OK: perl $] on "
162 . $::Config{'osname'} . ' '
163 . $::Config{'osvers'};
164 $::opt_b = 1; $body = "Perl reported to build OK on this system\n";
173 # Possible administrator addresses, in order of confidence
174 # (Note that cf_email is not mentioned to metaconfig, since
175 # we don't really want it. We'll just take it if we have to.)
177 # This has to be after the $ok stuff above because of the way
178 # that $::opt_C is forced.
179 $cc = ($::opt_C ? "" : (
180 $::opt_c || $::Config{perladmin} || $::Config{cf_email} || $::Config{cf_by}
187 ? $ENV{'USER'} || $ENV{'LOGNAME'}
188 : eval { getpwuid($<) }) ); # May be missing
195 # Explain what perlbug is
198 This program provides an easy way to create a message reporting a bug
199 in perl, and e-mail it to $address. It is *NOT* intended for
200 sending test messages or simply verifying that perl works, *NOR* is it
201 intended for reporting bugs in third-party perl modules. It is *ONLY*
202 a means of reporting verifiable problems with the core perl distribution,
203 and any solutions to such problems, to the people who maintain perl.
205 If you're just looking for help with perl, try posting to the Usenet
206 newsgroup comp.lang.perl.misc. If you're looking for help with using
207 perl with CGI, try posting to comp.infosystems.www.programming.cgi.
213 # Prompt for subject of message, if needed
216 First of all, please provide a subject for the
217 message. It should be a concise description of
218 the bug or problem. "perl bug" or "perl problem"
219 is not a concise description.
228 while( $subject =~ /^\s*$/ ) {
229 print "\nPlease enter a subject: ";
239 # Prompt for return address, if needed
242 # Try and guess return address
246 $domain = Mail::Util::maildomain();
247 } elsif ($Is_MSWin32) {
248 $domain = $ENV{'USERDOMAIN'};
250 require Sys::Hostname;
251 $domain = Sys::Hostname::hostname();
253 $domain = `hostname`.".".`domainname`;
254 $domain =~ s/[\r\n]+//g;
261 } elsif ($Is_VMS && !$::Config{'d_socket'}) {
262 $guess = "$domain\:\:$me";
264 $guess = "$me\@$domain" if $domain;
265 $guess = "$me\@unknown.addresss" unless $domain;
268 $guess = $ENV{'REPLYTO'} if defined($ENV{'REPLYTO'});
269 $guess = $ENV{"REPLY-TO"} if defined($ENV{'REPLY-TO'});
276 Your e-mail address will be useful if you need to be contacted. If the
277 default shown is not your full internet e-mail address, please correct it.
284 So that you may be contacted if necessary, please enter
285 your full internet e-mail address here.
290 if ( $ok && $guess ne '' ) {
296 print "Your address [$guess]: ";
301 if($from eq "") { $from = $guess }
306 #if( $from =~ /^(.*)\@(.*)$/ ) {
311 if( $from eq $cc or $me eq $cc ) {
312 # Try not to copy ourselves
317 # Prompt for administrator address, unless an override was given
318 if( !$::opt_C and !$::opt_c ) {
322 A copy of this report can be sent to your local
323 perl administrator. If the address is wrong, please
324 correct it, or enter 'none' or 'yourself' to not send
329 print "Local perl administrator [$cc]: ";
331 my($entry) = scalar(<>);
336 if($me eq $cc) { $cc = "" }
341 if($cc =~ /^(none|yourself|me|myself|ourselves)$/i) { $cc = "" }
343 $andcc = " and $cc" if $cc;
347 # Prompt for editor, if no override is given
348 if(! $::opt_e and ! $::opt_f and ! $::opt_b) {
352 Now you need to supply the bug report. Try to make
353 the report concise but descriptive. Include any
354 relevant detail. If you are reporting something
355 that does not work as you think it should, please
356 try to include example of both the actual
357 result, and what you expected.
359 Some information about your local
360 perl configuration will automatically be included
361 at the end of the report. If you are using any
362 unusual version of perl, please try and confirm
363 exactly which versions are relevant.
365 You will probably want to use an editor to enter
366 the report. If "$ed" is the editor you want
367 to use, then just press Enter, otherwise type in
368 the name of the editor you would like to use.
370 If you would like to use a prepared file, type
371 "file", and you will be asked for the filename.
375 print "Editor [$ed]: ";
377 my($entry) =scalar(<>);
381 if($entry eq "file") {
383 } elsif($entry ne "") {
389 # Generate scratch file to edit report in
392 my($dir) = ($Is_VMS ? 'sys$scratch:' :
393 ($Is_MSWin32 && $ENV{'TEMP'} ? $ENV{'TEMP'} : '/tmp/'));
394 $filename = "bugrep0$$";
395 $dir .= "\\" if $Is_MSWin32 and $dir !~ m|[\\/]$|;
396 $filename++ while -e "$dir$filename";
397 $filename = "$dir$filename";
401 # Prompt for file to read report from, if needed
403 if( $usefile and ! $file) {
407 What is the name of the file that contains your report?
413 my($entry) = scalar(<>);
419 No filename? I'll let you go back and choose an editor again.
425 if(!-f $entry or !-r $entry) {
428 I'm sorry, but I can't read from `$entry'. Maybe you mistyped the name of
429 the file? If you don't want to send a file, just enter a blank line and you
430 can get back to the editor selection.
442 open(REP,">$filename");
445 This is a bug report for perl from $from,
446 generated with the help of perlbug $Version running under perl $].
453 open(F,"<$file") or die "Unable to read report file from `$file': $!\n";
461 -----------------------------------------------------------------
462 [Please enter your report here]
466 [Please do not change anything below this line]
467 -----------------------------------------------------------------
474 # read in the report template once so that
475 # we can track whether the user does any editing.
476 # yes, *all* whitespace is ignored.
477 open(REP, "<$filename");
492 Site configuration information for perl $]:
496 if( $::Config{cf_by} and $::Config{cf_time}) {
497 print OUT "Configured by $::Config{cf_by} at $::Config{cf_time}.\n\n";
500 print OUT Config::myconfig;
503 print OUT "\nComplete configuration data for perl $]:\n\n";
505 foreach (sort keys %::Config) {
506 $value = $::Config{$_};
508 print OUT "$_='$value'\n";
523 Environment for perl $]:
526 (qw(PATH LD_LIBRARY_PATH
529 grep { /^(?:PERL|LC_)/ } keys %ENV)) {
531 exists $ENV{$env} ? "=$ENV{$env}" : ' (unset)',
543 Please make sure that the name of the editor you want to use is correct.
546 print "Editor [$ed]: ";
548 my($entry) =scalar(<>);
557 if(!$usefile and !$body) {
558 my $sts = system("$ed $filename");
560 #print "\nUnable to run editor!\n";
563 The editor you chose (`$ed') could apparently not be run!
564 Did you mistype the name of your editor? If so, please
565 correct it here, otherwise just press Enter.
568 print "Editor [$ed]: ";
570 my($entry) =scalar(<>);
580 You may want to save your report to a file, so you can edit and mail it
588 # Check that we have a report that has some, eh, report in it.
592 open(REP, "<$filename");
593 # a strange way to check whether any significant editing
594 # have been done: check whether any new non-empty lines
595 # have been added. Yes, the below code ignores *any* space
599 $unseen++ if ($_ ne '' and not exists $REP{$_});
602 while ($unseen == 0) {
605 I am sorry but it looks like you did not report anything.
608 print "Action (Retry Edit/Cancel) ";
609 my ($action) = scalar(<>);
610 if ($action =~ /^[re]/i) { # <R>etry <E>dit
612 } elsif ($action =~ /^[cq]/i) { # <C>ancel, <Q>uit
620 1 while unlink($filename); # remove all versions under VMS
621 print "\nCancelling.\n";
627 # Report is done, prompt for further action
634 Now that you have completed your report, would you like to send
635 the message to $address$andcc, display the message on
636 the screen, re-edit it, or cancel without sending anything?
637 You may also save the message as a file to mail at another time.
641 print "Action (Send/Display/Edit/Cancel/Save to File): ";
642 my($action) = scalar(<>);
645 if( $action =~ /^(f|sa)/i ) { # <F>ile/<Sa>ve
646 print "\n\nName of file to save message in [perlbug.rep]: ";
647 my($file) = scalar(<>);
649 if($file eq "") { $file = "perlbug.rep" }
652 open(REP,"<$filename");
653 print FILE "To: $address\nSubject: $subject\n";
654 print FILE "Cc: $cc\n" if $cc;
655 print FILE "Reply-To: $from\n" if $from;
657 while(<REP>) { print FILE }
661 print "\nMessage saved in `$file'.\n";
664 } elsif( $action =~ /^(d|l|sh)/i ) { # <D>isplay, <L>ist, <Sh>ow
665 # Display the message
666 open(REP,"<$filename");
667 while(<REP>) { print $_ }
669 } elsif( $action =~ /^se/i ) { # <S>end
672 Are you certain you want to send this message?
673 Please type \"yes\" if you are: ";
674 my($reply) = scalar(<STDIN>);
676 if( $reply eq "yes" ) {
681 That wasn't a clear "yes", so I won't send your message. If you are sure
682 your message should be sent, type in "yes" (without the quotes) at the
688 } elsif( $action =~ /^[er]/i ) { # <E>dit, <R>e-edit
691 #system("$ed $filename");
692 } elsif( $action =~ /^[qc]/i ) { # <C>ancel, <Q>uit
694 } elsif( $action =~ /^s/ ) {
697 I'm sorry, but I didn't understand that. Please type "send" or "save".
708 # Message has been accepted for transmission -- Send the message
712 $msg = new Mail::Send Subject => $subject, To => $address;
714 $msg->cc($cc) if $cc;
715 $msg->add("Reply-To",$from) if $from;
719 open(REP,"<$filename");
720 while(<REP>) { print $fh $_ }
725 print "\nMessage sent.\n";
728 if ( ($address =~ /@/ and $address !~ /^\w+%"/) or
729 ($cc =~ /@/ and $cc !~ /^\w+%"/) ){
731 foreach (qw[ IN MX SMTP UCX PONY WINS ],'') {
732 $prefix = "$_%",last if $ENV{"MAIL\$PROTOCOL_$_"};
734 $address = qq[${prefix}"$address"] unless $address =~ /^\w+%"/;
735 $cc = qq[${prefix}"$cc"] unless !$cc || $cc =~ /^\w+%"/;
737 $subject =~ s/"/""/g; $address =~ s/"/""/g; $cc =~ s/"/""/g;
738 my($sts) = system(qq[mail/Subject="$subject" $filename. "$address","$cc"]);
739 if ($sts) { die "Can't spawn off mail\n\t(leaving bug report in $filename): $sts\n;" }
743 foreach (qw(/usr/lib/sendmail /usr/sbin/sendmail /usr/ucblib/sendmail))
745 $sendmail = $_, last if -e $_;
748 if ($^O eq 'os2' and $sendmail eq "") {
749 my $path = $ENV{PATH};
751 my @path = split /$Config{path_sep}/, $path;
753 $sendmail = "$_/sendmail", last
755 $sendmail = "$_/sendmail.exe", last
756 if -e "$_/sendmail.exe";
760 paraprint <<"EOF", die "\n" if $sendmail eq "";
762 I am terribly sorry, but I cannot find sendmail, or a close equivalent, and
763 the perl package Mail::Send has not been installed, so I can't send your bug
764 report. We apologize for the inconvenience.
766 So you may attempt to find some way of sending your message, it has
767 been left in the file `$filename'.
771 open(SENDMAIL,"|$sendmail -t");
772 print SENDMAIL "To: $address\n";
773 print SENDMAIL "Subject: $subject\n";
774 print SENDMAIL "Cc: $cc\n" if $cc;
775 print SENDMAIL "Reply-To: $from\n" if $from;
776 print SENDMAIL "\n\n";
777 open(REP,"<$filename");
778 while(<REP>) { print SENDMAIL $_ }
781 if (close(SENDMAIL)) {
782 print "\nMessage sent.\n";
784 warn "\nSendmail returned status '",$?>>8,"'\n";
790 1 while unlink($filename); # remove all versions under VMS
797 A program to help generate bug reports about perl5, and mail them.
798 It is designed to be used interactively. Normally no arguments will
802 $0 [-v] [-a address] [-s subject] [-b body | -f file ]
803 [-r returnaddress] [-e editor] [-c adminaddress | -C] [-S] [-t] [-h]
805 Simplest usage: run "$0", and follow the prompts.
809 -v Include Verbose configuration data in the report
810 -f File containing the body of the report. Use this to
811 quickly send a prepared message.
812 -S Send without asking for confirmation.
813 -a Address to send the report to. Defaults to `$address'.
814 -c Address to send copy of report to. Defaults to `$cc'.
815 -C Don't send copy to administrator.
816 -s Subject to include with the message. You will be prompted
817 if you don't supply one on the command line.
818 -b Body of the report. If not included on the command line, or
819 in a file with -f, you will get a chance to edit the message.
820 -r Your return address. The program will ask you to confirm
821 this if you don't give it here.
823 -t Test mode. The target address defaults to `$testaddress'.
824 -d Data mode (the default if you redirect or pipe output.)
825 This prints out your configuration data, without mailing
826 anything. You can use this with -v to get more complete data.
827 -ok Report successful build on this sytem to perl porters (use alone).
828 -h Print this help message.
834 my @paragraphs = split /\n{2,}/, "@_";
836 for (@paragraphs) { # implicit local $_
846 ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ~~
854 perlbug - how to submit bug reports on Perl
858 B<perlbug> S<[ B<-v> ]> S<[ B<-a> I<address> ]> S<[ B<-s> I<subject> ]>
859 S<[ B<-b> I<body> | B<-f> I<file> ]> S<[ B<-r> I<returnaddress> ]>
860 S<[ B<-e> I<editor> ]> S<[ B<-c> I<adminaddress> | B<-C> ]>
861 S<[ B<-S> ]> S<[ B<-t> ]> S<[ B<-d> ]> S<[ B<-h> ]>
863 B<perlbug> S<[ B<-r> I<returnaddress> ]> B<-ok>
867 A program to help generate bug reports about perl or the modules that
868 come with it, and mail them.
870 If you have found a bug with a non-standard port (one that was not part
871 of the I<standard distribution>), a binary distribution, or a
872 non-standard module (such as Tk, CGI, etc), then please see the
873 documentation that came with that distribution to determine the correct
874 place to report bugs.
876 C<perlbug> is designed to be used interactively. Normally no arguments
877 will be needed. Simply run it, and follow the prompts.
879 If you are unable to run B<perlbug> (most likely because you don't have
880 a working setup to send mail that perlbug recognizes), you may have to
881 compose your own report, and email it to B<perlbug@perl.com>. You might
882 find the B<-d> option useful to get summary information in that case.
884 In any case, when reporting a bug, please make sure you have run through
889 =item What version of perl you are running?
891 Type C<perl -v> at the command line to find out.
893 =item Are you running the latest released version of perl?
895 Look at http://www.perl.com/ to find out. If it is not the latest
896 released version, get that one and see whether your bug has been
897 fixed. Note that bug reports about old versions of perl, especially
898 those prior to the 5.0 release, are likely to fall upon deaf ears.
899 You are on your own if you continue to use perl1 .. perl4.
901 =item Are you sure what you have is a bug?
903 A significant number of the bug reports we get turn out to be documented
904 features in perl. Make sure the behavior you are witnessing doesn't fall
905 under that category, by glancing through the documentation that comes
906 with perl (we'll admit this is no mean task, given the sheer volume of
907 it all, but at least have a look at the sections that I<seem> relevant).
909 Be aware of the familiar traps that perl programmers of various hues
910 fall into. See L<perltrap>.
912 Try to study the problem under the perl debugger, if necessary.
915 =item Do you have a proper test case?
917 The easier it is to reproduce your bug, the more likely it will be
918 fixed, because if no one can duplicate the problem, no one can fix it.
919 A good test case has most of these attributes: fewest possible number
920 of lines; few dependencies on external commands, modules, or
921 libraries; runs on most platforms unimpeded; and is self-documenting.
923 A good test case is almost always a good candidate to be on the perl
924 test suite. If you have the time, consider making your test case so
925 that it will readily fit into the standard test suite.
927 =item Can you describe the bug in plain English?
929 The easier it is to understand a reproducible bug, the more likely it
930 will be fixed. Anything you can provide by way of insight into the
931 problem helps a great deal. In other words, try to analyse the
932 problem to the extent you feel qualified and report your discoveries.
934 =item Can you fix the bug yourself?
936 A bug report which I<includes a patch to fix it> will almost
937 definitely be fixed. Use the C<diff> program to generate your patches
938 (C<diff> is being maintained by the GNU folks as part of the B<diffutils>
939 package, so you should be able to get it from any of the GNU software
940 repositories). If you do submit a patch, the cool-dude counter at
941 perlbug@perl.com will register you as a savior of the world. Your
942 patch may be returned with requests for changes, or requests for more
943 detailed explanations about your fix.
945 Here are some clues for creating quality patches: Use the B<-c> or
946 B<-u> switches to the diff program (to create a so-called context or
947 unified diff). Make sure the patch is not reversed (the first
948 argument to diff is typically the original file, the second argument
949 your changed file). Make sure you test your patch by applying it with
950 the C<patch> program before you send it on its way. Try to follow the
951 same style as the code you are trying to patch. Make sure your patch
952 really does work (C<make test>, if the thing you're patching supports
955 =item Can you use C<perlbug> to submit the report?
957 B<perlbug> will, amongst other things, ensure your report includes
958 crucial information about your version of perl. If C<perlbug> is unable
959 to mail your report after you have typed it in, you may have to compose
960 the message yourself, add the output produced by C<perlbug -d> and email
961 it to B<perlbug@perl.com>. If, for some reason, you cannot run
962 C<perlbug> at all on your system, be sure to include the entire output
963 produced by running C<perl -V> (note the uppercase V).
967 Having done your bit, please be prepared to wait, to be told the bug
968 is in your code, or even to get no reply at all. The perl maintainers
969 are busy folks, so if your problem is a small one or if it is
970 difficult to understand, they may not respond with a personal reply.
971 If it is important to you that your bug be fixed, do monitor the
972 C<Changes> file in any development releases since the time you submitted
973 the bug, and encourage the maintainers with kind words (but never any
974 flames!). Feel free to resend your bug report if the next released
975 version of perl comes out and your bug is still present.
983 Address to send the report to. Defaults to `perlbug@perl.com'.
987 Body of the report. If not included on the command line, or
988 in a file with B<-f>, you will get a chance to edit the message.
992 Don't send copy to administrator.
996 Address to send copy of report to. Defaults to the address of the
997 local perl administrator (recorded when perl was built).
1001 Data mode (the default if you redirect or pipe output). This prints out
1002 your configuration data, without mailing anything. You can use this
1003 with B<-v> to get more complete data.
1011 File containing the body of the report. Use this to quickly send a
1016 Prints a brief summary of the options.
1020 Report successful build on this system to perl porters. Forces B<-S>,
1021 B<-C>, and B<-v>. Forces and supplies values for B<-s> and B<-b>. Only
1022 prompts for a return address if it cannot guess it (for use with
1023 B<make>). Honors return address specified with B<-r>.
1027 Your return address. The program will ask you to confirm its default
1028 if you don't use this option.
1032 Send without asking for confirmation.
1036 Subject to include with the message. You will be prompted if you don't
1037 supply one on the command line.
1041 Test mode. The target address defaults to `perlbug-test@perl.com'.
1045 Include verbose configuration data in the report.
1051 Kenneth Albanowski (E<lt>kjahds@kjahds.comE<gt>), subsequently I<doc>tored
1052 by Gurusamy Sarathy (E<lt>gsar@umich.eduE<gt>), Tom Christiansen
1053 (E<lt>tchrist@perl.comE<gt>), Nathan Torkington (E<lt>gnat@frii.comE<gt>),
1054 and Charles F. Randall (E<lt>cfr@pobox.comE<gt>).
1058 perl(1), perldebug(1), perltrap(1), diff(1), patch(1)
1062 None known (guess what must have been used to report them?)
1068 close OUT or die "Can't close $file: $!";
1069 chmod 0755, $file or die "Can't reset permissions for $file: $!\n";
1070 exec("$Config{'eunicefix'} $file") if $Config{'eunicefix'} ne ':';