1MASS-BUG(1) MASS-BUG(1)
2
6 mass-bug - mass-file a bug report against a list of packages
7
9 mass-bug [options] --subject="bug subject" template package-list
10
12 mass-bug assists in filing a mass bug report in the Debian BTS on a set
13 of packages. For each package in the package-list file (which should
14 list one package per line together with an optional version number
15 separated from the package name by an underscore), it fills out the
16 template, adds BTS pseudo-headers, and either displays or sends the bug
17 report.
18 Warning: Some care has been taken to avoid unpleasant and common
20 mistakes, but this is still a power tool that can generate massive
21 amounts of bug report mails. Use it with care, and read the
22 documentation in the Developer's Reference about mass filing of bug
23 reports first.
24
26 The template file is the body of the message that will be sent for each
27 bug report, excluding the BTS pseudo-headers. In the template,
28 #PACKAGE# is replaced with the name of the package. If a version was
29 specified for the package, #VERSION# will be replaced by that version.
30 The components of the version number may be specified using #EPOCH#,
32 #UPSTREAM_VERSION# and #REVISION#. #EPOCH# includes the trailing colon
33 and #REVISION# the leading dash so that
34 #EPOCH#UPSTREAM_VERSION##REVISION# is always the same as #VERSION#.
35 Note that text in the template will be automatically word-wrapped to 70
37 columns, up to the start of a signature (indicated by '-- ' at the
38 start of a line on its own). This is another reason to avoid including
39 BTS pseudo-headers in your template.
40
42 mass-bug examines the devscripts configuration files as described
43 below. Command line options override the configuration file settings,
44 though.
45 --severity=(wishlist|minor|normal|important|serious|grave|critical)
47 Specify the severity with which bugs should be filed. Default is
48 normal.
49 --display
51 Fill out the templates for each package and display them all for
52 verification. This is the default behavior.
53 --send
55 Actually send the bug reports.
56 --subject="bug subject"
58 Specify the subject of the bug report. The subject will be
59 automatically prefixed with the name of the package that the bug is
60 filed against.
61 --tags
63 Set the BTS pseudo-header for tags.
64 --user
66 Set the BTS pseudo-header for a usertags' user.
67 --usertags
69 Set the BTS pseudo-header for usertags.
70 --source
72 Specify that package names refer to source packages rather than
73 binary packages.
74 --sendmail=SENDMAILCMD
76 Specify the sendmail command. The command will be split on white
77 space and will not be passed to a shell. Default is
78 /usr/sbin/sendmail.
79 --no-wrap
81 Do not wrap the template to lines of 70 characters.
82 --no-conf, --noconf
84 Do not read any configuration files. This can only be used as the
85 first option given on the command-line.
86 --help
88 Provide a usage message.
89 --version
91 Display version information.
92
94 DEBEMAIL and EMAIL can be set in the environment to control the email
95 address that the bugs are sent from.
96
98 The two configuration files /etc/devscripts.conf and ~/.devscripts are
99 sourced by a shell in that order to set configuration variables.
100 Command line options can be used to override configuration file
101 settings. Environment variable settings are ignored for this purpose.
102 The currently recognised variables are:
103 BTS_SENDMAIL_COMMAND
105 If this is set, specifies a sendmail command to use instead of
106 /usr/sbin/sendmail. Same as the --sendmail command line option.
107
109 This program is Copyright (C) 2006 by Joey Hess <joeyh@debian.org>.
110 It is licensed under the terms of the GPL, either version 2 of the
112 License, or (at your option) any later version.
113
115 Joey Hess <joeyh@debian.org>
116Debian Utilities 2018-12-10 MASS-BUG(1)