Changeset 5036:c01a36ebe339

Show
Ignore:
Timestamp:
2007-04-01 14:59:25 (22 months ago)
Author:
Brendan Cully <brendan@…>
Parents:
5035:d0da811c593e (diff), 5034:f467353f5657 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Branch:
HEAD
Message:

Merge flea restore

Files:
18 removed
4 modified

Legend:

Unmodified
Added
Removed
  • doc/muttbug.man

    r4343 r5036  
    1818.\"     Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA. 
    1919.\" 
    20 .TH flea 1 "January 2005" Unix "User Manuals" 
     20.TH flea 1 "July 2000" Unix "User Manuals" 
    2121.SH NAME 
    22 flea \- Report a bug (or rather a flea) in mutt. (OBSOLETE) 
     22flea \- Report a bug (or rather a flea) in mutt. 
     23.SH SYNOPSIS 
     24.PP 
     25.B flea 
    2326.SH DESCRIPTION 
    2427.PP 
    2528.B flea 
    26 used to be a shell script which helped you to submit a bug report against the  
     29is a shell script which helps you to submit a bug report against the  
    2730.BR mutt (1) 
    2831mail user agent. 
    2932.PP 
    30 The mutt bug tracking system broke down under the spam thrown at it and 
    31 was shut down in January 2005.  To report a bug in mutt, please use 
    32 your system's bug reporting system if mutt came as part of your 
    33 system, or refer to the mutt web site at 
    34 .I http://www.mutt.org 
    35 for more information. 
     33If you invoke  
     34.BR flea ,  
     35you'll first be prompted for a short 
     36description of the problem you experience.  This will be used as the 
     37bug report's subject line, so it should be concise, but informative. 
     38.PP 
     39You are then asked to assign an initial severity level to the 
     40problem you observe;  
     41.B flea 
     42will give you a description which severity level is appropriate or 
     43not. 
     44.PP 
     45Then, you are asked for the location of a core dump (normally named 
     46.BR core ) 
     47which may have been left over by a crash of your  
     48.BR mutt (1). 
     49You can just type \(lqno\(rq here, or you can enter the path leading  
     50to a core dump. 
     51.B flea 
     52will try to use either 
     53.BR sdb (1), 
     54.BR dbx (1), 
     55or 
     56.BR gdb (1) 
     57to extract some information from this core dump which may be helpful 
     58to developers in order to determine the reason for the crash. 
     59.PP 
     60Finally, you are asked whether or not you want to include personal 
     61and system  
     62.BR mutt (1) 
     63configuration files with the bug report.  If at all possible, we 
     64urge you to answer these questions with \(lqyes\(rq, since a 
     65reference configuration makes it incredibly easier to track down a 
     66problem. 
     67.PP 
     68If you are using Debian GNU/Linux, 
     69.B flea 
     70will now check whether or not  
     71.B mutt 
     72has been installed as a Debian 
     73package on your system, and suggest to file the bug against the 
     74.BR mutt (1) 
     75and Debian bug tracking systems.  This option was added since the  
     76.BR mutt (1) 
     77project uses another instantiation of the Debian bug tracking 
     78system, so submitting bugs against both systems in one pass is 
     79simple. 
     80.PP 
     81You are then dropped into your favorite editor as determined by the  
     82.B EDITOR 
     83and 
     84.B VISUAL 
     85environment variables.   
     86.PP 
     87Please give us details about the problem in the empty space below 
     88the line reading \(lqPlease type your report below this line\(rq. 
     89We are most interested in precise information on what symptoms you 
     90observe and what steps may be used to reproduce the bug.  Chances 
     91are that problems which can easily be reproduced will be fixed 
     92quickly.  So please take some time when filling out this part of the 
     93template. 
     94.PP 
     95The remainder of the template contains various kinds of information 
     96gathered from your system, including output of the 
     97.BR uname (1) 
     98command, output from 
     99.BR mutt (1) 
     100itself, and your system's  
     101.BR mutt (1) 
     102configuration files.  You may wish to browse through this part of 
     103the bug report form in order to avoid leaking confidential 
     104information to the public. 
     105.PP 
     106If you leave the editor,  
     107.B flea 
     108will give you the option to review, re-edit, submit, or abandon your 
     109bug report.  If you decide to submit it, a mail message containing 
     110your report will be sent to <submit@bugs.guug.de>.  You'll receive a 
     111copy of this message. 
     112.PP 
     113While your bug report is being processed by the bug tracking system, 
     114you will receive various e-mail messages from the bug tracking 
     115system informing you about what's going on: Once your bug report has 
     116been entered into the bug tracking system, it will be assigned a 
     117unique serial number about which you are informed via e-mail.  If 
     118you wish to submit additional information about the bug, you can 
     119just send it to the address 
     120.BR \fIserial\fP@bugs.guug.de . 
     121.PP 
     122Later, you will most likely receive questions from the developers 
     123about the problem you observed, and you will eventually be informed 
     124that your bug report has been closed.  This means that the bug has 
     125been fixed at least in the 
     126.BR cvs (1) 
     127repository.  If the answers you receive don't satisfy you, don't 
     128hesitate to contact the developers directly under 
     129.BR mutt-dev@mutt.org. 
     130.PP 
     131You can also browse your bug report and all additional information 
     132and replies connected to it using the bug tracking system's Web 
     133interface under the following URL: 
     134http://bugs.guug.de/ 
     135.SH 
     136ENVIRONMENT 
    36137.PP 
    37138.B flea 
    38 is now a shell script that prints a short error message and exits. 
     139will use the following environment variables: 
     140.IP "EMAIL" 
     141Your electronic mail address.  Will be used to set the bug report's 
     142From header, and to send you a copy of the report. 
     143.IP "LOGNAME" 
     144Your login name.  If the 
     145.B EMAIL 
     146environment variable isn't set, this will be used instead to send 
     147you a copy of the report.  Setting the sender will be left to  
     148.BR sendmail (1) 
     149on your system. 
     150.IP "REPLYTO" 
     151If set, the bug report will contain a Reply-To header with the 
     152e-mail address contained in this environment variable. 
     153.IP "ORGANIZATION" 
     154If set, the bug report will contain an Organization header with the 
     155contents of this environment variable. 
     156.IP "PAGER" 
     157If set, this environment variable will be expected to contain the 
     158path to your favorite pager for viewing the bug report.  If unset,  
     159.BR more (1) 
     160will be used. 
     161.IP "VISUAL" 
     162If set, this environment variable will be expected to contain the 
     163path to your favorite visual editor. 
     164.IP "EDITOR" 
     165If set, this environment variable will be expected to contain the 
     166path to your favorite editor.  This variable is examined if and only 
     167if the  
     168.B VISUAL 
     169environment variable is unset.  If 
     170.B EDITOR 
     171is unset,  
     172.BR vi (1) 
     173will be used to edit the bug report. 
     174.SH 
     175FILES 
     176.PP 
     177.IP "core" 
     178If present, this file may contain a post-mortem memory dump of mutt. 
     179It will be inspected using the debugger installed on your system. 
     180.SH  
     181SEE ALSO 
     182.PP 
     183.BR dbx (1), 
     184.BR gdb (1), 
     185.BR lynx (1), 
     186.BR mutt (1), 
     187.BR muttrc (5), 
     188.BR sdb (1), 
     189.BR sendmail (1), 
     190.BR uname (1), 
     191.BR vi (1) 
     192.PP 
     193The mutt bug tracking system: http://bugs.guug.de/ 
    39194.SH 
    40195AUTHOR 
  • doc/muttbug.man

    r5035 r5036  
    1616.\"     You should have received a copy of the GNU General Public License 
    1717.\"     along with this program; if not, write to the Free Software 
    18 .\"     Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA  02111, USA. 
     18.\"     Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA. 
    1919.\" 
    2020.TH flea 1 "July 2000" Unix "User Manuals" 
  • muttbug.sh.in

    r4969 r5036  
    2828# 
    2929 
    30 exec >&2 
    31  
    32 echo "$0: No bug tracking system." 
    33  
    34 cat << EOF 
    35  
    36 The mutt bug tracking system has broken down under the spam sent to 
    37 it, and has been shut down.  While we are working on a new bug 
    38 database, please use your system's default bug submission mechanism 
    39 if mutt came as part of your system, or submit your bug reports 
    40 directly to one of the mailing lists linked from http://www.mutt.org/. 
    41  
    42 Please pardon our dust. 
     30SUBMIT="submit@bugs.guug.de" 
     31DEBIAN_SUBMIT="submit@bugs.debian.org" 
     32 
     33prefix=@prefix@ 
     34 
     35DEBUGGER=@DEBUGGER@ 
     36SENDMAIL=@SENDMAIL@ 
     37sysconfdir=@sysconfdir@ 
     38pkgdatadir=@pkgdatadir@ 
     39 
     40include_file () 
     41{ 
     42        echo 
     43        echo "--- Begin $1" 
     44        sed -e 's/^-/- -/' $1 | egrep -v '^[    ]*(#|$)' 
     45        echo "--- End $1" 
     46        echo 
     47} 
     48 
     49debug_gdb () 
     50{ 
     51        cat << EOF > $SCRATCH/gdb.rc 
     52bt 
     53list 
     54quit 
    4355EOF 
    44  
    45 exit 1 
     56        $DEBUGGER -n -x $SCRATCH/gdb.rc -c $CORE mutt 
     57} 
     58 
     59debug_dbx () 
     60{ 
     61        cat << EOF > $SCRATCH/dbx.rc 
     62where 
     63list 
     64quit 
     65EOF 
     66        $DEBUGGER -s $SCRATCH/dbx.rc mutt $CORE 
     67} 
     68 
     69debug_sdb () 
     70{ 
     71        cat << EOF > $SCRATCH/sdb.rc 
     72t 
     73w 
     74q 
     75EOF 
     76        $DEBUGGER mutt $CORE < $SCRATCH/sdb.rc 
     77} 
     78 
     79case `echo -n` in 
     80"") n=-n; c=   ;; 
     81 *) n=; c='\c' ;; 
     82esac 
     83  
     84 
     85exec > /dev/tty 
     86exec < /dev/tty 
     87 
     88SCRATCH=${TMPDIR-/tmp}/`basename $0`.`hostname`.$$ 
     89 
     90mkdir ${SCRATCH} || \ 
     91{  
     92        echo "`basename $0`: Can't create temporary directory." >& 2 ;  
     93        exit 1 ;  
     94} 
     95 
     96trap "rm -r -f ${SCRATCH} ; trap '' 0 ; exit" 0 1 2 
     97 
     98TEMPLATE=${SCRATCH}/template.txt 
     99 
     100if test -z "$EMAIL" ; then 
     101        EMAIL="`mutt -Q from 2> /dev/null | sed -e 's/^from=.\(.*\).$/\1/'`" 
     102fi 
     103 
     104echo "Please enter your e-mail address [$EMAIL]:" 
     105echo $n "> $c" 
     106read EMAILTMP 
     107 
     108if test -n "$EMAILTMP" ; then 
     109        EMAIL="$EMAILTMP" 
     110fi 
     111 
     112echo "Please enter a one-line description of the problem you experience:" 
     113echo $n "> $c" 
     114read SUBJECT 
     115 
     116cat <<EOF   
     117What should the severity for this bug report be? 
     118 
     119       0) Feature request, or maybe a bug which is very difficult to 
     120       fix due to major design considerations. 
     121 
     122       1) The package fails to perform correctly in some conditions, 
     123       or on some systems, or fails to comply with current policy 
     124       documents. Most bugs are in this category. 
     125 
     126       2) This bug makes this version of the package unsuitable for 
     127       a stable release. 
     128 
     129       3) Dangerous bug. Makes the package in question unusable by 
     130       anyone or mostly so, or causes data loss, or introduces a 
     131       security hole allowing access to the accounts of users who 
     132       use the package. 
     133 
     134       4) Critical bug. Makes unrelated software on the system (or 
     135       the whole system) break, or causes serious data loss, or 
     136       introduces a security hole on systems where you install the 
     137       package. 
     138 
     139EOF 
     140echo $n "Severity? [01234] $c" 
     141read severity 
     142case "$severity" in 
     1430|[Ww]) severity=wishlist  ;; 
     1442|[Ii]) severity=important ;; 
     1453|[Gg]) severity=grave     ;; 
     1464|[Cc]) severity=critical  ;; 
     147     *) severity=normal    ;; 
     148esac 
     149 
     150if test -x $DEBUGGER ; then 
     151        test -f core && CORE=core 
     152        echo "If mutt has crashed, it may have saved some program state in" 
     153        echo "a file named core.  We can include this information with the bug" 
     154        echo "report if you wish so." 
     155        echo "Do you want to include information gathered from a core file?" 
     156        echo "If yes, please enter the path - otherwise just say no: [$CORE]" 
     157        echo $n "> $c" 
     158        read _CORE 
     159        test "$_CORE" && CORE="$_CORE" 
     160fi 
     161 
     162echo $n "Do you want to include your personal mutt configuration files? [Y|n] $c" 
     163read personal 
     164case "$personal" in 
     165[nN]*)  personal=no  ;; 
     166    *)  personal=yes ;; 
     167esac 
     168 
     169echo $n "Do you want to include your system's global mutt configuration file? [Y|n] $c" 
     170read global 
     171case "$global" in 
     172[nN]*)  global=no  ;; 
     173    *)  global=yes ;; 
     174esac 
     175 
     176if test -f /etc/debian_version ; then 
     177        DEBIAN=yes 
     178        echo $n "Checking whether mutt has been installed as a package... $c" 
     179        DEBIANVERSION="`dpkg -l mutt | grep '^[ih]' | awk '{print $3}'`" 2> /dev/null 
     180        if test "$DEBIANVERSION" ; then 
     181                DPKG=yes 
     182        else 
     183                DPKG=no 
     184                unset DEBIANVERSION 
     185        fi 
     186        echo "$DPKG" 
     187        echo $n "File this bug with Debian? [Y|n] $c" 
     188        read DPKG 
     189        case "$DPKG" in 
     190        [nN])   DPKG=no ;; 
     191        *)      DPKG=yes ;; 
     192        esac 
     193else 
     194        DEBIAN=no 
     195        DPKG=no 
     196fi 
     197 
     198if rpm -q mutt > /dev/null 2> /dev/null ; then 
     199        echo "Mutt seems to come from an RPM package." 
     200        RPMVERSION="`rpm -q mutt`" 
     201        RPMPACKAGER="`rpm -q -i mutt | sed -n -e 's/^Packager *: *//p'`" 
     202fi 
     203 
     204MUTTVERSION="`mutt -v | awk '{print $2; exit; }'`" 
     205test "$DPKG" = "yes" && SUBMIT="$SUBMIT, $DEBIAN_SUBMIT" 
     206 
     207exec > ${TEMPLATE} 
     208 
     209test "$EMAIL"        && echo "From: $EMAIL" 
     210test "$REPLYTO"      && echo "Reply-To: $REPLYTO" 
     211test "$ORGANIZATION" && echo "Organization: $ORGANIZATION" 
     212 
     213echo "Subject: mutt-$MUTTVERSION: $SUBJECT" 
     214echo "To: $SUBMIT" 
     215test "$EMAIL"        && echo "Bcc: ${EMAIL}" 
     216echo 
     217echo "Package: mutt" 
     218echo "Version: ${DEBIANVERSION-${RPMVERSION-$MUTTVERSION}}" 
     219echo "Severity: $severity" 
     220echo  
     221echo "-- Please type your report below this line" 
     222echo 
     223echo 
     224echo 
     225 
     226if test "$DEBIAN" = "yes" ; then 
     227        echo "Obtaining Debian-specific information..." > /dev/tty 
     228        bug -p -s dummy mutt < /dev/null 2> /dev/null |        \ 
     229                sed -n -e "/^-- System Information/,/^---/p" | \ 
     230                grep -v '^---' 
     231else 
     232        echo "-- System Information" 
     233        echo "System Version: `uname -a`" 
     234        test -z "$RPMPACKAGER" || echo "RPM Packager: $RPMPACKAGER"; 
     235        test -f /etc/redhat-release && echo "RedHat Release: `cat /etc/redhat-release`" 
     236        test -f /etc/SuSE-release && echo "SuSE Release: `sed 1q /etc/SuSE-release`" 
     237        # Please provide more of these if you have any. 
     238fi 
     239 
     240echo  
     241echo "-- Build environment information" 
     242echo 
     243echo "(Note: This is the build environment installed on the system" 
     244echo "muttbug is run on.  Information may or may not match the environment" 
     245echo "used to build mutt.)" 
     246echo 
     247echo "- gcc version information" 
     248echo "@CC@" 
     249@CC@ -v 2>&1 
     250echo 
     251echo "- CFLAGS" 
     252echo @CFLAGS@ 
     253 
     254 
     255echo 
     256echo "-- Mutt Version Information" 
     257echo 
     258mutt -v 
     259 
     260if test "$CORE" && test -f "$CORE" ; then 
     261        echo  
     262        echo "-- Core Dump Analysis Output" 
     263        echo 
     264 
     265        case "$DEBUGGER" in 
     266                *sdb) debug_sdb $CORE ;; 
     267                *dbx) debug_dbx $CORE ;; 
     268                *gdb) debug_gdb $CORE ;; 
     269        esac 
     270         
     271        echo 
     272fi 
     273 
     274if test "$personal" = "yes" ; then 
     275        CANDIDATES=".muttrc-${MUTTVERSION} .muttrc .mutt/muttrc-${MUTTVERSION} .mutt/muttrc" 
     276        MATCHED="none" 
     277        for f in $CANDIDATES; do 
     278                if test -f "${HOME}/$f" ; then 
     279                        MATCHED="${HOME}/$f" 
     280                        break 
     281                fi 
     282        done 
     283         
     284        if test "$MATCHED" = "none" ; then 
     285                echo "Warning: Can't find your personal .muttrc." >&2 
     286        else 
     287                include_file $MATCHED 
     288        fi 
     289fi 
     290 
     291 
     292if test "$global" = "yes" ; then 
     293        CANDIDATES="Muttrc-${MUTTVERSION} Muttrc" 
     294        DIRECTORIES="$sysconfdir $pkgdatadir" 
     295        MATCHED="none" 
     296        for d in $DIRECTORIES ; do 
     297                for f in $CANDIDATES; do 
     298                        if test -f $d/$f ; then 
     299                                MATCHED="$d/$f" 
     300                                break 
     301                        fi 
     302                done 
     303                test "$MATCHED" = "none" || break 
     304        done 
     305         
     306        if test "$MATCHED" = "none" ; then 
     307                echo "Warning: Can't find global Muttrc." >&2 
     308        else 
     309                include_file $MATCHED 
     310        fi 
     311fi 
     312 
     313exec > /dev/tty 
     314 
     315cp $TEMPLATE $SCRATCH/mutt-bug.txt 
     316 
     317input="e" 
     318while : ; do 
     319        if test "$input" = "e" ; then 
     320                ${VISUAL-${EDITOR-vi}} $SCRATCH/mutt-bug.txt 
     321                if cmp $SCRATCH/mutt-bug.txt ${TEMPLATE} > /dev/null ; then 
     322                        echo "Warning: Bug report was not modified!" 
     323                fi 
     324        fi 
     325         
     326        echo $n "Submit, Edit, View, Quit? [S|e|v|q] $c" 
     327        read _input 
     328        input="`echo $_input | tr EVSQ evsq`" 
     329        case $input in 
     330        e*)     ;; 
     331        v*)     ${PAGER-more} $SCRATCH/mutt-bug.txt ;; 
     332        s*|"")  $SENDMAIL -t < $SCRATCH/mutt-bug.txt ; exit ;; 
     333        q*)     exit 
     334        esac 
     335done 
     336 
  • muttbug.sh.in

    r5035 r5036  
    1010 
    1111# 
    12 #     Copyright (c) 2000 Thomas Roessler <roessler@guug.de> 
     12#     Copyright (c) 2000 Thomas Roessler <roessler@does-not-exist.org> 
    1313# 
    1414# 
     
    2525#     You should have received a copy of the GNU General Public License 
    2626#     along with this program; if not, write to the Free Software 
    27 #     Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA  02111, USA. 
     27#     Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA. 
    2828# 
    2929