.\" Automatically generated by Pod::Man 4.10 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" Set up some character translations and predefined strings. \*(-- will .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left .\" double quote, and \*(R" will give a right double quote. \*(C+ will .\" give a nicer C++. Capital omega is used to do unbreakable dashes and .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff, .\" nothing in troff, for use with C<>. .tr \(*W- .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' .ie n \{\ . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} .el\{\ . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' . ds C` . ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .\" .\" Avoid warning from groff about undefined register 'F'. .de IX .. .nr rF 0 .if \n(.g .if rF .nr rF 1 .if (\n(rF:(\n(.g==0)) \{\ . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF .\" ======================================================================== .\" .IX Title "MASS-BUG 1" .TH MASS-BUG 1 "2019-08-04" "Debian Utilities" " " .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH "NAME" mass\-bug \- mass\-file a bug report against a list of packages .SH "SYNOPSIS" .IX Header "SYNOPSIS" \&\fBmass-bug\fR [\fIoptions\fR] \fB\-\-subject="\fR\fIbug subject\fR\fB"\fR \fItemplate package-list\fR .SH "DESCRIPTION" .IX Header "DESCRIPTION" mass-bug assists in filing a mass bug report in the Debian \s-1BTS\s0 on a set of packages. For each package in the package-list file (which should list one package per line together with an optional version number separated from the package name by an underscore), it fills out the template, adds \&\s-1BTS\s0 pseudo-headers, and either displays or sends the bug report. .PP Warning: Some care has been taken to avoid unpleasant and common mistakes, but this is still a power tool that can generate massive amounts of bug report mails. Use it with care, and read the documentation in the Developer's Reference about mass filing of bug reports first. .SH "TEMPLATE" .IX Header "TEMPLATE" The template file is the body of the message that will be sent for each bug report, excluding the \s-1BTS\s0 pseudo-headers. In the template, #PACKAGE# is replaced with the name of the package. If a version was specified for the package, #VERSION# will be replaced by that version. .PP The components of the version number may be specified using #EPOCH#, #UPSTREAM_VERSION# and #REVISION#. #EPOCH# includes the trailing colon and #REVISION# the leading dash so that #EPOCH#UPSTREAM_VERSION##REVISION# is always the same as #VERSION#. .PP Note that text in the template will be automatically word-wrapped to 70 columns, up to the start of a signature (indicated by '\-\- ' at the start of a line on its own). This is another reason to avoid including \&\s-1BTS\s0 pseudo-headers in your template. .SH "OPTIONS" .IX Header "OPTIONS" \&\fBmass-bug\fR examines the \fBdevscripts\fR configuration files as described below. Command line options override the configuration file settings, though. .IP "\fB\-\-severity=\fR(\fBwishlist\fR|\fBminor\fR|\fBnormal\fR|\fBimportant\fR|\fBserious\fR|\fBgrave\fR|\fBcritical\fR)" 4 .IX Item "--severity=(wishlist|minor|normal|important|serious|grave|critical)" Specify the severity with which bugs should be filed. Default is \fBnormal\fR. .IP "\fB\-\-display\fR" 4 .IX Item "--display" Fill out the templates for each package and display them all for verification. This is the default behavior. .IP "\fB\-\-send\fR" 4 .IX Item "--send" Actually send the bug reports. .ie n .IP "\fB\-\-subject=""\fR\fIbug subject\fR\fB""\fR" 4 .el .IP "\fB\-\-subject=``\fR\fIbug subject\fR\fB''\fR" 4 .IX Item "--subject=""bug subject""" Specify the subject of the bug report. The subject will be automatically prefixed with the name of the package that the bug is filed against. .IP "\fB\-\-tags\fR" 4 .IX Item "--tags" Set the \s-1BTS\s0 pseudo-header for tags. .IP "\fB\-\-user\fR" 4 .IX Item "--user" Set the \s-1BTS\s0 pseudo-header for a usertags' user. .IP "\fB\-\-usertags\fR" 4 .IX Item "--usertags" Set the \s-1BTS\s0 pseudo-header for usertags. .IP "\fB\-\-source\fR" 4 .IX Item "--source" Specify that package names refer to source packages rather than binary packages. .IP "\fB\-\-sendmail=\fR\fI\s-1SENDMAILCMD\s0\fR" 4 .IX Item "--sendmail=SENDMAILCMD" Specify the \fBsendmail\fR command. The command will be split on white space and will not be passed to a shell. Default is \fI/usr/sbin/sendmail\fR. .IP "\fB\-\-no\-wrap\fR" 4 .IX Item "--no-wrap" Do not wrap the template to lines of 70 characters. .IP "\fB\-\-no\-conf\fR, \fB\-\-noconf\fR" 4 .IX Item "--no-conf, --noconf" Do not read any configuration files. This can only be used as the first option given on the command-line. .IP "\fB\-\-help\fR" 4 .IX Item "--help" Provide a usage message. .IP "\fB\-\-version\fR" 4 .IX Item "--version" Display version information. .SH "ENVIRONMENT" .IX Header "ENVIRONMENT" \&\fB\s-1DEBEMAIL\s0\fR and \fB\s-1EMAIL\s0\fR can be set in the environment to control the email address that the bugs are sent from. .SH "CONFIGURATION VARIABLES" .IX Header "CONFIGURATION VARIABLES" The two configuration files \fI/etc/devscripts.conf\fR and \&\fI~/.devscripts\fR are sourced by a shell in that order to set configuration variables. Command line options can be used to override configuration file settings. Environment variable settings are ignored for this purpose. The currently recognised variables are: .IP "\fB\s-1BTS_SENDMAIL_COMMAND\s0\fR" 4 .IX Item "BTS_SENDMAIL_COMMAND" If this is set, specifies a \fBsendmail\fR command to use instead of \&\fI/usr/sbin/sendmail\fR. Same as the \fB\-\-sendmail\fR command line option. .SH "COPYRIGHT" .IX Header "COPYRIGHT" This program is Copyright (C) 2006 by Joey Hess . .PP It is licensed under the terms of the \s-1GPL,\s0 either version 2 of the License, or (at your option) any later version. .SH "AUTHOR" .IX Header "AUTHOR" Joey Hess