.\" 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 "BTS 1" .TH BTS 1 "2018-12-05" "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" bts \- developers' command line interface to the BTS .SH "SYNOPSIS" .IX Header "SYNOPSIS" \&\fBbts\fR [\fIoptions\fR] \fIcommand\fR [\fIargs\fR] [\fB#\fR\fIcomment\fR] [\fB.\fR|\fB,\fR \fIcommand\fR [\fIargs\fR] [\fB#\fR\fIcomment\fR]] ... .SH "DESCRIPTION" .IX Header "DESCRIPTION" This is a command line interface to the Debian Bug Tracking System (\s-1BTS\s0), intended mainly for use by developers. It lets the \s-1BTS\s0 be manipulated using simple commands that can be run at the prompt or in a script, does various sanity checks on the input, and constructs and sends a mail to the \s-1BTS\s0 control address for you. A local cache of web pages and e\-mails from the \s-1BTS\s0 may also be created and updated. .PP In general, the command line interface is the same as what you would write in a mail to control@bugs.debian.org, just prefixed with \*(L"bts\*(R". For example: .PP .Vb 3 \& % bts severity 69042 normal \& % bts merge 69042 43233 \& % bts retitle 69042 blah blah .Ve .PP A few additional commands have been added for your convenience, and this program is less strict about what constitutes a valid bug number. For example, \&\*(L"severity Bug#85942 normal\*(R" is understood, as is \*(L"severity #85942 normal\*(R". (Of course, your shell may regard \*(L"#\*(R" as a comment character though, so you may need to quote it!) .PP Also, for your convenience, this program allows you to abbreviate commands to the shortest unique substring (similar to how cvs lets you abbreviate commands). So it understands things like \*(L"bts cl 85942\*(R". .PP It is also possible to include a comment in the mail sent to the \s-1BTS.\s0 If your shell does not strip out the comment in a command like \&\*(L"bts severity 30321 normal #inflated severity\*(R", then this program is smart enough to figure out where the comment is, and include it in the email. Note that most shells do strip out such comments before they get to the program, unless the comment is quoted. (Something like \*(L"bts severity #85942 normal\*(R" will not be treated as a comment!) .PP You can specify multiple commands by separating them with a single dot, rather like \fBupdate\-rc.d\fR; a single comma may also be used; all the commands will then be sent in a single mail. It is important the dot/comma is surrounded by whitespace so it is not mistaken for part of a command. For example (quoting where necessary so that \fBbts\fR sees the comment): .PP .Vb 1 \& % bts severity 95672 normal , merge 95672 95673 \e#they are the same! .Ve .PP The abbreviation \*(L"it\*(R" may be used to refer to the last mentioned bug number, so you could write: .PP .Vb 1 \& % bts severity 95672 wishlist , retitle it "bts: please add a \-\-foo option" .Ve .PP Please use this program responsibly, and do take our users into consideration. .SH "OPTIONS" .IX Header "OPTIONS" \&\fBbts\fR examines the \fBdevscripts\fR configuration files as described below. Command line options override the configuration file settings, though. .IP "\fB\-o\fR, \fB\-\-offline\fR" 4 .IX Item "-o, --offline" Make \fBbts\fR use cached bugs for the \fBshow\fR and \fBbugs\fR commands, if a cache is available for the requested data. See the \fBcache\fR command, below for information on setting up a cache. .IP "\fB\-\-online\fR, \fB\-\-no\-offline\fR" 4 .IX Item "--online, --no-offline" Opposite of \fB\-\-offline\fR; overrides any configuration file directive to work offline. .IP "\fB\-n\fR, \fB\-\-no\-action\fR" 4 .IX Item "-n, --no-action" Do not send emails but print them to standard output. .IP "\fB\-\-cache\fR, \fB\-\-no\-cache\fR" 4 .IX Item "--cache, --no-cache" Should we attempt to cache new versions of \s-1BTS\s0 pages when performing \fBshow\fR/\fBbugs\fR commands? Default is to cache. .IP "\fB\-\-cache\-mode=\fR{\fBmin\fR|\fBmbox\fR|\fBfull\fR}" 4 .IX Item "--cache-mode={min|mbox|full}" When running a \fBbts cache\fR command, should we only mirror the basic bug (\fBmin\fR), or should we also mirror the mbox version (\fBmbox\fR), or should we mirror the whole thing, including the mbox and the boring attachments to the \s-1BTS\s0 bug pages and the acknowledgement emails (\fBfull\fR)? Default is \fBmin\fR. .IP "\fB\-\-cache\-delay=\fR\fIseconds\fR" 4 .IX Item "--cache-delay=seconds" Time in seconds to delay between each download, to avoid hammering the \s-1BTS\s0 web server. Default is 5 seconds. .IP "\fB\-\-mbox\fR" 4 .IX Item "--mbox" Open a mail reader to read the mbox corresponding to a given bug number for \fBshow\fR and \fBbugs\fR commands. .IP "\fB\-\-mailreader=\fR\fI\s-1READER\s0\fR" 4 .IX Item "--mailreader=READER" Specify the command to read the mbox. Must contain a "\fB\f(CB%s\fB\fR" string (unquoted!), which will be replaced by the name of the mbox file. The command will be split on white space and will not be passed to a shell. Default is '\fBmutt \-f \f(CB%s\fB\fR'. (Also, \fB%%\fR will be substituted by a single \fB%\fR if this is needed.) .IP "\fB\-\-cc\-addr=\fR\fI\s-1CC_EMAIL_ADDRESS\s0\fR" 4 .IX Item "--cc-addr=CC_EMAIL_ADDRESS" Send carbon copies to a list of users. \fI\s-1CC_EMAIL_ADDRESS\s0\fR should be a comma-separated list of email addresses. .IP "\fB\-\-use\-default\-cc\fR" 4 .IX Item "--use-default-cc" Add the addresses specified in the configuration file option \&\fB\s-1BTS_DEFAULT_CC\s0\fR to the list specified using \fB\-\-cc\-addr\fR. This is the default. .IP "\fB\-\-no\-use\-default\-cc\fR" 4 .IX Item "--no-use-default-cc" Do not add addresses specified in \fB\s-1BTS_DEFAULT_CC\s0\fR to the carbon copy list. .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. The \fB\-t\fR option will be automatically added if the command is \fI/usr/sbin/sendmail\fR or \fI/usr/sbin/exim*\fR. For other mailers, if they require a \fB\-t\fR option, this must be included in the \&\fI\s-1SENDMAILCMD\s0\fR, for example: \fB\-\-sendmail=\*(L"/usr/sbin/mymailer \-t\*(R"\fR. .IP "\fB\-\-mutt\fR" 4 .IX Item "--mutt" Use \fBmutt\fR for sending of mails. Default is not to use \fBmutt\fR, except for some commands. .Sp Note that one of \fB\f(CB$DEBEMAIL\fB\fR or \fB\f(CB$EMAIL\fB\fR must be set in the environment in order to use \fBmutt\fR to send emails. .IP "\fB\-\-no\-mutt\fR" 4 .IX Item "--no-mutt" Don't use \fBmutt\fR for sending of mails. .IP "\fB\-\-soap\-timeout=\fR\fI\s-1SECONDS\s0\fR" 4 .IX Item "--soap-timeout=SECONDS" Specify a timeout for \s-1SOAP\s0 calls as used by the \fBselect\fR and \fBstatus\fR commands. .IP "\fB\-\-smtp\-host=\fR\fI\s-1SMTPHOST\s0\fR" 4 .IX Item "--smtp-host=SMTPHOST" Specify an \s-1SMTP\s0 host. If given, \fBbts\fR will send mail by talking directly to this \s-1SMTP\s0 host rather than by invoking a \fBsendmail\fR command. .Sp The host name may be followed by a colon (\*(L":\*(R") and a port number in order to use a port other than the default. It may also begin with \&\*(L"ssmtp://\*(R" or \*(L"smtps://\*(R" to indicate that \s-1SMTPS\s0 should be used. .Sp If \s-1SMTPS\s0 not specified, \fBbts\fR will still try to use \s-1STARTTLS\s0 if it's advertised by the \s-1SMTP\s0 host. .Sp Note that one of \fB\f(CB$DEBEMAIL\fB\fR or \fB\f(CB$EMAIL\fB\fR must be set in the environment in order to use direct \s-1SMTP\s0 connections to send emails. .Sp Note that when sending directly via an \s-1SMTP\s0 host, specifying addresses in \&\fB\-\-cc\-addr\fR or \fB\s-1BTS_DEFAULT_CC\s0\fR that the \s-1SMTP\s0 host will not relay will cause the \&\s-1SMTP\s0 host to reject the entire mail. .Sp Note also that the use of the \fBreassign\fR command may, when either \fB\-\-interactive\fR or \fB\-\-force\-interactive\fR mode is enabled, lead to the automatic addition of a Cc to \fI\f(CI$newpackage\fI\fR\f(CW@packages\fR.debian.org. In these cases, the note above regarding relaying applies. The submission interface (port 587) on reportbug.debian.org does not support relaying and, as such, should not be used as an \s-1SMTP\s0 server for \fBbts\fR under the circumstances described in this paragraph. .IP "\fB\-\-smtp\-username=\fR\fI\s-1USERNAME\s0\fR, \fB\-\-smtp\-password=\fR\fI\s-1PASSWORD\s0\fR" 4 .IX Item "--smtp-username=USERNAME, --smtp-password=PASSWORD" Specify the credentials to use when connecting to the \s-1SMTP\s0 server specified by \fB\-\-smtp\-host\fR. If the server does not require authentication then these options should not be used. .Sp If a username is specified but not a password, \fBbts\fR will prompt for the password before sending the mail. .IP "\fB\-\-smtp\-helo=\fR\fI\s-1HELO\s0\fR" 4 .IX Item "--smtp-helo=HELO" Specify the name to use in the \fI\s-1HELO\s0\fR command when connecting to the \s-1SMTP\s0 server; defaults to the contents of the file \fI/etc/mailname\fR, if it exists. .Sp Note that some \s-1SMTP\s0 servers may reject the use of a \fI\s-1HELO\s0\fR which either does not resolve or does not appear to belong to the host using it. .IP "\fB\-\-bts\-server\fR" 4 .IX Item "--bts-server" Use a debbugs server other than https://bugs.debian.org. .IP "\fB\-f\fR, \fB\-\-force\-refresh\fR" 4 .IX Item "-f, --force-refresh" Download a bug report again, even if it does not appear to have changed since the last \fBcache\fR command. Useful if a \fB\-\-cache\-mode=full\fR is requested for the first time (otherwise unchanged bug reports will not be downloaded again, even if the boring bits have not been downloaded). .IP "\fB\-\-no\-force\-refresh\fR" 4 .IX Item "--no-force-refresh" Suppress any configuration file \fB\-\-force\-refresh\fR option. .IP "\fB\-\-only\-new\fR" 4 .IX Item "--only-new" Download only new bugs when caching. Do not check for updates in bugs we already have. .IP "\fB\-\-include\-resolved\fR" 4 .IX Item "--include-resolved" When caching bug reports, include those that are marked as resolved. This is the default behaviour. .IP "\fB\-\-no\-include\-resolved\fR" 4 .IX Item "--no-include-resolved" Reverse the behaviour of the previous option. That is, do not cache bugs that are marked as resolved. .IP "\fB\-\-no\-ack\fR" 4 .IX Item "--no-ack" Suppress acknowledgment mails from the \s-1BTS.\s0 Note that this will only affect the copies of messages CCed to bugs, not those sent to the control bot. .IP "\fB\-\-ack\fR" 4 .IX Item "--ack" Do not suppress acknowledgement mails. This is the default behaviour. .IP "\fB\-i\fR, \fB\-\-interactive\fR" 4 .IX Item "-i, --interactive" Before sending an e\-mail to the control bot, display the content and allow it to be edited, or the sending cancelled. .IP "\fB\-\-force\-interactive\fR" 4 .IX Item "--force-interactive" Similar to \fB\-\-interactive\fR, with the exception that an editor is spawned before prompting for confirmation of the message to be sent. .IP "\fB\-\-no\-interactive\fR" 4 .IX Item "--no-interactive" Send control e\-mails without confirmation. This is the default behaviour. .IP "\fB\-q\fR, \fB\-\-quiet\fR" 4 .IX Item "-q, --quiet" When running \fBbts cache\fR, only display information about newly cached pages, not messages saying already cached. If this option is specified twice, only output error messages (to stderr). .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. .SH "COMMANDS" .IX Header "COMMANDS" For full details about the commands, see the \s-1BTS\s0 documentation. .IP "\fBshow\fR [\fIoptions\fR] [\fIbug number\fR | \fIpackage\fR | \fImaintainer\fR | \fB:\fR ] [\fIopt\fR\fB=\fR\fIval\fR ...]" 4 .IX Item "show [options] [bug number | package | maintainer | : ] [opt=val ...]" .PD 0 .IP "\fBshow\fR [\fIoptions\fR] [\fBsrc:\fR\fIpackage\fR | \fBfrom:\fR\fIsubmitter\fR] [\fIopt\fR\fB=\fR\fIval\fR ...]" 4 .IX Item "show [options] [src:package | from:submitter] [opt=val ...]" .IP "\fBshow\fR [\fIoptions\fR] [\fBtag:\fR\fItag\fR | \fBusertag:\fR\fItag\fR ] [\fIopt\fR\fB=\fR\fIval\fR ...]" 4 .IX Item "show [options] [tag:tag | usertag:tag ] [opt=val ...]" .IP "\fBshow\fR [\fBrelease-critical\fR | \fBrelease\-critical/\fR... | \fB\s-1RC\s0\fR]" 4 .IX Item "show [release-critical | release-critical/... | RC]" .PD This is a synonym for \fBbts bugs\fR. .IP "\fBbugs\fR [\fIoptions\fR] [\fIbug_number\fR | \fIpackage\fR | \fImaintainer\fR | \fB:\fR ] [\fIopt\fR\fB=\fR\fIval\fR ...]" 4 .IX Item "bugs [options] [bug_number | package | maintainer | : ] [opt=val ...]" .PD 0 .IP "\fBbugs\fR [\fIoptions\fR] [\fBsrc:\fR\fIpackage\fR | \fBfrom:\fR\fIsubmitter\fR] [\fIopt\fR\fB=\fR\fIval\fR ...]" 4 .IX Item "bugs [options] [src:package | from:submitter] [opt=val ...]" .IP "\fBbugs\fR [\fIoptions\fR] [\fBtag:\fR\fItag\fR | \fBusertag:\fR\fItag\fR ] [\fIopt\fR\fB=\fR\fIval\fR ...]" 4 .IX Item "bugs [options] [tag:tag | usertag:tag ] [opt=val ...]" .IP "\fBbugs\fR [\fBrelease-critical\fR | \fBrelease\-critical/\fR... | \fB\s-1RC\s0\fR]" 4 .IX Item "bugs [release-critical | release-critical/... | RC]" .PD Display the page listing the requested bugs in a web browser using \&\fBsensible\-browser\fR\|(1). .Sp Options may be specified after the \fBbugs\fR command in addition to or instead of options at the start of the command line: recognised options at this point are: \fB\-o\fR/\fB\-\-offline\fR/\fB\-\-online\fR, \fB\-m\fR/\fB\-\-mbox\fR, \fB\-\-mailreader\fR and \fB\-\-\fR[\fBno\-\fR]\fBcache\fR. These are described earlier in this manpage. If either the \fB\-o\fR or \fB\-\-offline\fR option is used, or there is already an up-to-date copy in the local cache, the cached version will be used. .Sp The meanings of the possible arguments are as follows: .RS 4 .IP "(none)" 8 .IX Item "(none)" If nothing is specified, \fBbts bugs\fR will display your bugs, assuming that either \fB\s-1DEBEMAIL\s0\fR or \fB\s-1EMAIL\s0\fR (examined in that order) is set to the appropriate email address. .IP "\fIbug_number\fR" 8 .IX Item "bug_number" Display bug number \fIbug_number\fR. .IP "\fIpackage\fR" 8 .IX Item "package" Display the bugs for the package \fIpackage\fR. .IP "\fBsrc:\fR\fIpackage\fR" 8 .IX Item "src:package" Display the bugs for the source package \fIpackage\fR. .IP "\fImaintainer\fR" 8 .IX Item "maintainer" Display the bugs for the maintainer email address \fImaintainer\fR. .IP "\fBfrom:\fR\fIsubmitter\fR" 8 .IX Item "from:submitter" Display the bugs for the submitter email address \fIsubmitter\fR. .IP "\fBtag:\fR\fItag\fR" 8 .IX Item "tag:tag" Display the bugs which are tagged with \fItag\fR. .IP "\fBusertag:\fR\fItag\fR" 8 .IX Item "usertag:tag" Display the bugs which are tagged with usertag \fItag\fR. See the \s-1BTS\s0 documentation for more information on usertags. This will require the use of a \fBusers=\fR\fIemail\fR option. .IP "\fB:\fR" 8 .IX Item ":" Details of the bug tracking system itself, along with a bug-request page with more options than this script, can be found on https://bugs.debian.org/. This page itself will be opened if the command 'bts bugs :' is used. .IP "\fBrelease-critical\fR, \fB\s-1RC\s0\fR" 8 .IX Item "release-critical, RC" Display the front page of the release-critical pages on the \s-1BTS.\s0 This is a synonym for https://bugs.debian.org/release\-critical/index.html. It is also possible to say release\-critical/debian/main.html and the like. \&\s-1RC\s0 is a synonym for release\-critical/other/all.html. .RE .RS 4 .Sp After the argument specifying what to display, you can optionally specify options to use to format the page or change what it displayed. These are passed to the \s-1BTS\s0 in the \s-1URL\s0 downloaded. For example, pass dist=stable to see bugs affecting the stable version of a package, version=1.0 to see bugs affecting that version of a package, or reverse=yes to display newest messages first in a bug log. .Sp If caching has been enabled (that is, \fB\-\-no\-cache\fR has not been used, and \fB\s-1BTS_CACHE\s0\fR has not been set to \fBno\fR), then any page requested by \&\fBbts show\fR will automatically be cached, and be available offline thereafter. Pages which are automatically cached in this way will be deleted on subsequent "\fBbts show\fR|\fBbugs\fR|\fBcache\fR\*(L" invocations if they have not been accessed in 30 days. Warning: on a filesystem mounted with the \*(R"noatime\*(L" option, running \*(R"\fBbts show\fR|\fBbugs\fR" does not update the cache files' access times; a cached bug will then be subject to auto-cleaning 30 days after its initial download, even if it has been accessed in the meantime. .Sp Any other \fBbts\fR commands following this on the command line will be executed after the browser has been exited. .Sp The desired browser can be specified and configured by setting the \&\fB\s-1BROWSER\s0\fR environment variable. The conventions follow those defined by Eric Raymond at http://www.catb.org/~esr/BROWSER/; we here reproduce the relevant part. .Sp The value of \fB\s-1BROWSER\s0\fR may consist of a colon-separated series of browser command parts. These should be tried in order until one succeeds. Each command part may optionally contain the string \fB\f(CB%s\fB\fR; if it does, the \s-1URL\s0 to be viewed is substituted there. If a command part does not contain \fB\f(CB%s\fB\fR, the browser is to be launched as if the \s-1URL\s0 had been supplied as its first argument. The string \fB%%\fR must be substituted as a single %. .Sp Rationale: We need to be able to specify multiple browser commands so programs obeying this convention can do the right thing in either X or console environments, trying X first. Specifying multiple commands may also be useful for people who share files like \fI.profile\fR across multiple systems. We need \fB\f(CB%s\fB\fR because some popular browsers have remote-invocation syntax that requires it. Unless \fB%%\fR reduces to %, it won't be possible to have a literal \fB\f(CB%s\fB\fR in the string. .Sp For example, on most Linux systems a good thing to do would be: .Sp BROWSER='mozilla \-raise \-remote \*(L"openURL(%s,new\-window)\*(R":links' .RE .IP "\fBselect\fR [\fIkey\fR\fB:\fR\fIvalue\fR ...]" 4 .IX Item "select [key:value ...]" Uses the \s-1SOAP\s0 interface to output a list of bugs which match the given selection requirements. .Sp The following keys are allowed, and may be given multiple times. .RS 4 .IP "\fBpackage\fR" 8 .IX Item "package" Binary package name. .IP "\fBsource\fR" 8 .IX Item "source" Source package name. .IP "\fBmaintainer\fR" 8 .IX Item "maintainer" E\-mail address of the maintainer. .IP "\fBsubmitter\fR" 8 .IX Item "submitter" E\-mail address of the submitter. .IP "\fBseverity\fR" 8 .IX Item "severity" Bug severity. .IP "\fBstatus\fR" 8 .IX Item "status" Status of the bug. One of \fBopen\fR, \fBdone\fR, or \fBforwarded\fR. .IP "\fBtag\fR" 8 .IX Item "tag" Tags applied to the bug. If \fBusers\fR is specified, may include usertags in addition to the standard tags. .IP "\fBowner\fR" 8 .IX Item "owner" Bug's owner. .IP "\fBcorrespondent\fR" 8 .IX Item "correspondent" Address of someone who sent mail to the log. .IP "\fBaffects\fR" 8 .IX Item "affects" Bugs which affect this package. .IP "\fBbugs\fR" 8 .IX Item "bugs" List of bugs to search within. .IP "\fBusers\fR" 8 .IX Item "users" Users to use when looking up usertags. .IP "\fBarchive\fR" 8 .IX Item "archive" Whether to search archived bugs or normal bugs; defaults to \fB0\fR (i.e. only search normal bugs). As a special case, if archive is \&\fBboth\fR, both archived and unarchived bugs are returned. .RE .RS 4 .Sp For example, to select the set of bugs submitted by jrandomdeveloper@example.com and tagged \fBwontfix\fR, one would use .Sp bts select submitter:jrandomdeveloper@example.com tag:wontfix .Sp If a key is used multiple times then the set of bugs selected includes those matching any of the supplied values; for example .Sp bts select package:foo severity:wishlist severity:minor .Sp returns all bugs of package foo with either wishlist or minor severity. .RE .IP "\fBstatus\fR [\fIbug\fR | \fBfile:\fR\fIfile\fR | \fBfields:\fR\fIfield\fR[\fB,\fR\fIfield\fR ...] | \fBverbose\fR] ..." 4 .IX Item "status [bug | file:file | fields:field[,field ...] | verbose] ..." Uses the \s-1SOAP\s0 interface to output status information for the given bugs (or as read from the listed files \*(-- use \fB\-\fR to indicate \s-1STDIN\s0). .Sp By default, all populated fields for a bug are displayed. .Sp If \fBverbose\fR is given, empty fields will also be displayed. .Sp If \fBfields\fR is given, only those fields will be displayed. No validity checking is performed on any specified fields. .IP "\fBclone\fR \fIbug\fR \fInew_ID\fR [\fInew_ID\fR ...]" 4 .IX Item "clone bug new_ID [new_ID ...]" The \fBclone\fR control command allows you to duplicate a \fIbug\fR report. It is useful in the case where a single report actually indicates that multiple distinct bugs have occurred. \*(L"New IDs\*(R" are negative numbers, separated by spaces, which may be used in subsequent control commands to refer to the newly duplicated bugs. A new report is generated for each new \s-1ID.\s0 .IP "\fBdone\fR \fIbug\fR [\fIversion\fR]" 4 .IX Item "done bug [version]" Mark a \fIbug\fR as Done. This forces interactive mode since done messages should include an explanation why the bug is being closed. You should specify which \&\fIversion\fR of the package closed the bug, if possible. .IP "\fBreopen\fR \fIbug\fR [\fIsubmitter\fR]" 4 .IX Item "reopen bug [submitter]" Reopen a \fIbug\fR, with optional \fIsubmitter\fR. .IP "\fBarchive\fR \fIbug\fR" 4 .IX Item "archive bug" Archive a \fIbug\fR that has previously been archived but is currently not. The \fIbug\fR must fulfill all of the requirements for archiving with the exception of those that are time-based. .IP "\fBunarchive\fR \fIbug\fR" 4 .IX Item "unarchive bug" Unarchive a \fIbug\fR that is currently archived. .IP "\fBretitle\fR \fIbug\fR \fItitle\fR" 4 .IX Item "retitle bug title" Change the \fItitle\fR of the \fIbug\fR. .IP "\fBsummary\fR \fIbug\fR [\fImessagenum\fR]" 4 .IX Item "summary bug [messagenum]" Select a message number that should be used as the summary of a \fIbug\fR. .Sp If no message number is given, the summary is cleared. .IP "\fBsubmitter\fR \fIbug\fR [\fIbug\fR ...] \fIsubmitter-email\fR" 4 .IX Item "submitter bug [bug ...] submitter-email" Change the submitter address of a \fIbug\fR or a number of bugs, with \fB!\fR meaning `use the address on the current email as the new submitter address'. .IP "\fBreassign\fR \fIbug\fR [\fIbug\fR ...] \fIpackage\fR [\fIversion\fR]" 4 .IX Item "reassign bug [bug ...] package [version]" Reassign a \fIbug\fR or a number of bugs to a different \fIpackage\fR. The \fIversion\fR field is optional; see the explanation at . .IP "\fBfound\fR \fIbug\fR [\fIversion\fR]" 4 .IX Item "found bug [version]" Indicate that a \fIbug\fR was found to exist in a particular package version. Without \fIversion\fR, the list of fixed versions is cleared and the bug is reopened. .IP "\fBnotfound\fR \fIbug\fR \fIversion\fR" 4 .IX Item "notfound bug version" Remove the record that \fIbug\fR was encountered in the given version of the package to which it is assigned. .IP "\fBfixed\fR \fIbug\fR \fIversion\fR" 4 .IX Item "fixed bug version" Indicate that a \fIbug\fR was fixed in a particular package version, without affecting the \fIbug\fR's open/closed status. .IP "\fBnotfixed\fR \fIbug\fR \fIversion\fR" 4 .IX Item "notfixed bug version" Remove the record that a \fIbug\fR was fixed in the given version of the package to which it is assigned. .Sp This is equivalent to the sequence of commands "\fBfound\fR \fIbug\fR \fIversion\fR\*(L", \&\*(R"\fBnotfound\fR \fIbug\fR \fIversion\fR". .IP "\fBblock\fR \fIbug\fR \fBby\fR|\fBwith\fR \fIbug\fR [\fIbug\fR ...]" 4 .IX Item "block bug by|with bug [bug ...]" Note that a \fIbug\fR is blocked from being fixed by a set of other bugs. .IP "\fBunblock\fR \fIbug\fR \fBby\fR|\fBwith\fR \fIbug\fR [\fIbug\fR ...]" 4 .IX Item "unblock bug by|with bug [bug ...]" Note that a \fIbug\fR is no longer blocked from being fixed by a set of other bugs. .IP "\fBmerge\fR \fIbug\fR \fIbug\fR [\fIbug\fR ...]" 4 .IX Item "merge bug bug [bug ...]" Merge a set of bugs together. .IP "\fBforcemerge\fR \fIbug\fR \fIbug\fR [\fIbug\fR ...]" 4 .IX Item "forcemerge bug bug [bug ...]" Forcibly merge a set of bugs together. The first \fIbug\fR listed is the master bug, and its settings (those which must be equal in a normal \fBmerge\fR) are assigned to the bugs listed next. .IP "\fBunmerge\fR \fIbug\fR" 4 .IX Item "unmerge bug" Unmerge a \fIbug\fR. .IP "\fBtag\fR \fIbug\fR [\fB+\fR|\fB\-\fR|\fB=\fR] \fItag\fR [\fItag\fR ...]" 4 .IX Item "tag bug [+|-|=] tag [tag ...]" .PD 0 .IP "\fBtags\fR \fIbug\fR [\fB+\fR|\fB\-\fR|\fB=\fR] \fItag\fR [\fItag\fR ...]" 4 .IX Item "tags bug [+|-|=] tag [tag ...]" .PD Set or unset a \fItag\fR on a \fIbug\fR. The tag may either be the exact tag name or it may be abbreviated to any unique tag substring. (So using \&\fBfixed\fR will set the tag \fBfixed\fR, not \fBfixed-upstream\fR, for example, but \fBfix\fR would not be acceptable.) Multiple tags may be specified as well. The two commands (tag and tags) are identical. At least one tag must be specified, unless the \fB=\fR flag is used, where the command .Sp .Vb 1 \& bts tags = .Ve .Sp will remove all tags from the specified \fIbug\fR. .Sp Adding/removing the \fBsecurity\fR tag will add \*(L"team\e@security.debian.org\*(R" to the Cc list of the control email. .Sp The list of valid tags and their significance is available at . The current valid tags are: .Sp patch, wontfix, moreinfo, unreproducible, fixed, help, security, upstream, pending, d\-i, confirmed, ipv6, lfs, fixed-upstream, l10n, newcomer, a11y, ftbfs .Sp There is also a tag for each release of Debian since \*(L"potato\*(R". Note that this list may be out of date, see the website for the most up to date source. .IP "\fBaffects\fR \fIbug\fR [\fB+\fR|\fB\-\fR|\fB=\fR] \fIpackage\fR [\fIpackage\fR ...]" 4 .IX Item "affects bug [+|-|=] package [package ...]" Indicates that a \fIbug\fR affects a \fIpackage\fR other than that against which it is filed, causing the \fIbug\fR to be listed by default in the \fIpackage\fR list of the other \fIpackage\fR. This should generally be used where the \fIbug\fR is severe enough to cause multiple reports from users to be assigned to the wrong package. At least one \fIpackage\fR must be specified, unless the \fB=\fR flag is used, where the command .Sp .Vb 1 \& bts affects = .Ve .Sp will remove all indications that \fIbug\fR affects other packages. .IP "\fBuser\fR \fIemail\fR" 4 .IX Item "user email" Specify a user \fIemail\fR address before using the \fBusertags\fR command. .IP "\fBusertag\fR \fIbug\fR [\fB+\fR|\fB\-\fR|\fB=\fR] \fItag\fR [\fItag\fR ...]" 4 .IX Item "usertag bug [+|-|=] tag [tag ...]" .PD 0 .IP "\fBusertags\fR \fIbug\fR [\fB+\fR|\fB\-\fR|\fB=\fR] \fItag\fR [\fItag\fR ...]" 4 .IX Item "usertags bug [+|-|=] tag [tag ...]" .PD Set or unset a user tag on a \fIbug\fR. The \fItag\fR must be the exact tag name wanted; there are no defaults or checking of tag names. Multiple tags may be specified as well. The two commands (\fBusertag\fR and \fBusertags\fR) are identical. At least one \fItag\fR must be specified, unless the \fB=\fR flag is used, where the command .Sp .Vb 1 \& bts usertags = .Ve .Sp will remove all user tags from the specified \fIbug\fR. .IP "\fBclaim\fR \fIbug\fR [\fIclaim\fR]" 4 .IX Item "claim bug [claim]" Record that you have claimed a \fIbug\fR (e.g. for a bug squashing party). \&\fIclaim\fR should be a unique token allowing the bugs you have claimed to be identified; an e\-mail address is often used. .Sp If no \fIclaim\fR is specified, the environment variable \fB\s-1DEBEMAIL\s0\fR or \fB\s-1EMAIL\s0\fR (checked in that order) is used. .IP "\fBunclaim\fR \fIbug\fR [\fIclaim\fR]" 4 .IX Item "unclaim bug [claim]" Remove the record that you have claimed a bug. .Sp If no \fIclaim\fR is specified, the environment variable \fB\s-1DEBEMAIL\s0\fR or \fB\s-1EMAIL\s0\fR (checked in that order) is used. .IP "\fBseverity\fR \fIbug\fR \fIseverity\fR" 4 .IX Item "severity bug severity" Change the \fIseverity\fR of a \fIbug\fR. Available severities are: \fBwishlist\fR, \fBminor\fR, \fBnormal\fR, \&\fBimportant\fR, \fBserious\fR, \fBgrave\fR, \fBcritical\fR. The severity may be abbreviated to any unique substring. .IP "\fBforwarded\fR \fIbug\fR \fIaddress\fR" 4 .IX Item "forwarded bug address" Mark the \fIbug\fR as forwarded to the given \fIaddress\fR (usually an email address or a \s-1URL\s0 for an upstream bug tracker). .IP "\fBnotforwarded\fR \fIbug\fR" 4 .IX Item "notforwarded bug" Mark a \fIbug\fR as not forwarded. .IP "\fBpackage\fR [\fIpackage\fR ...]" 4 .IX Item "package [package ...]" The following commands will only apply to bugs against the listed \&\fIpackage\fRs; this acts as a safety mechanism for the \s-1BTS.\s0 If no packages are listed, this check is turned off again. .IP "\fBlimit\fR [\fIkey\fR[\fB:\fR\fIvalue\fR]] ..." 4 .IX Item "limit [key[:value]] ..." The following commands will only apply to bugs which meet the specified criterion; this acts as a safety mechanism for the \s-1BTS.\s0 If no \fIvalue\fRs are listed, the limits for that \fIkey\fR are turned off again. If no \fIkey\fRs are specified, all limits are reset. .RS 4 .IP "\fBsubmitter\fR" 8 .IX Item "submitter" E\-mail address of the submitter. .IP "\fBdate\fR" 8 .IX Item "date" Date the bug was submitted. .IP "\fBsubject\fR" 8 .IX Item "subject" Subject of the bug. .IP "\fBmsgid\fR" 8 .IX Item "msgid" Message-id of the initial bug report. .IP "\fBpackage\fR" 8 .IX Item "package" Binary package name. .IP "\fBsource\fR" 8 .IX Item "source" Source package name. .IP "\fBtag\fR" 8 .IX Item "tag" Tags applied to the bug. .IP "\fBseverity\fR" 8 .IX Item "severity" Bug severity. .IP "\fBowner\fR" 8 .IX Item "owner" Bug's owner. .IP "\fBaffects\fR" 8 .IX Item "affects" Bugs affecting this package. .IP "\fBarchive\fR" 8 .IX Item "archive" Whether to search archived bugs or normal bugs; defaults to \fB0\fR (i.e. only search normal bugs). As a special case, if archive is \&\fBboth\fR, both archived and unarchived bugs are returned. .RE .RS 4 .Sp For example, to limit the set of bugs affected by the subsequent control commands to those submitted by jrandomdeveloper@example.com and tagged \&\fBwontfix\fR, one would use .Sp bts limit submitter:jrandomdeveloper@example.com tag:wontfix .Sp If a key is used multiple times then the set of bugs selected includes those matching any of the supplied values; for example .Sp bts limit package:foo severity:wishlist severity:minor .Sp only applies the subsequent control commands to bugs of package foo with either \fBwishlist\fR or \fBminor\fR severity. .RE .IP "\fBowner\fR \fIbug\fR \fIowner-email\fR" 4 .IX Item "owner bug owner-email" Change the \*(L"owner\*(R" address of a \fIbug\fR, with \fB!\fR meaning `use the address on the current email as the new owner address'. .Sp The owner of a bug accepts responsibility for dealing with it. .IP "\fBnoowner\fR \fIbug\fR" 4 .IX Item "noowner bug" Mark a bug as having no \*(L"owner\*(R". .IP "\fBsubscribe\fR \fIbug\fR [\fIemail\fR]" 4 .IX Item "subscribe bug [email]" Subscribe the given \fIemail\fR address to the specified \fIbug\fR report. If no email address is specified, the environment variable \fB\s-1DEBEMAIL\s0\fR or \fB\s-1EMAIL\s0\fR (in that order) is used. If those are not set, or \fB!\fR is given as email address, your default address will be used. .Sp After executing this command, you will be sent a subscription confirmation to which you have to reply. When subscribed to a bug report, you receive all relevant emails and notifications. Use the unsubscribe command to unsubscribe. .IP "\fBunsubscribe\fR \fIbug\fR [\fIemail\fR]" 4 .IX Item "unsubscribe bug [email]" Unsubscribe the given email address from the specified bug report. As with subscribe above, if no email address is specified, the environment variables \&\fB\s-1DEBEMAIL\s0\fR or \fB\s-1EMAIL\s0\fR (in that order) is used. If those are not set, or \fB!\fR is given as email address, your default address will be used. .Sp After executing this command, you will be sent an unsubscription confirmation to which you have to reply. Use the \fBsubscribe\fR command to, well, subscribe. .IP "\fBreportspam\fR \fIbug\fR ..." 4 .IX Item "reportspam bug ..." The \fBreportspam\fR command allows you to report a \fIbug\fR report as containing spam. It saves one from having to go to the bug web page to do so. .IP "\fBspamreport\fR \fIbug\fR ..." 4 .IX Item "spamreport bug ..." \&\fBspamreport\fR is a synonym for \fBreportspam\fR. .IP "\fBcache\fR [\fIoptions\fR] [\fImaint_email\fR | \fIpkg\fR | \fBsrc:\fR\fIpkg\fR | \fBfrom:\fR\fIsubmitter\fR]" 4 .IX Item "cache [options] [maint_email | pkg | src:pkg | from:submitter]" .PD 0 .IP "\fBcache\fR [\fIoptions\fR] [\fBrelease-critical\fR | \fBrelease\-critical/\fR... | \fB\s-1RC\s0\fR]" 4 .IX Item "cache [options] [release-critical | release-critical/... | RC]" .PD Generate or update a cache of bug reports for the given email address or package. By default it downloads all bugs belonging to the email address in the \fB\s-1DEBEMAIL\s0\fR environment variable (or the \fB\s-1EMAIL\s0\fR environment variable if \fB\s-1DEBEMAIL\s0\fR is unset). This command may be repeated to cache bugs belonging to several people or packages. If multiple packages or addresses are supplied, bugs belonging to any of the arguments will be cached; those belonging to more than one of the arguments will only be downloaded once. The cached bugs are stored in \&\fI\f(CI$XDG_CACHE_HOME\fI/devscripts/bts/\fR or, if \fB\s-1XDG_CACHE_HOME\s0\fR is not set, in \&\fI~/.cache/devscripts/bts/\fR. .Sp You can use the cached bugs with the \fB\-o\fR switch. For example: .Sp .Vb 2 \& bts \-o bugs \& bts \-o show 12345 .Ve .Sp Also, \fBbts\fR will update the files in it in a piecemeal fashion as it downloads information from the \s-1BTS\s0 using the \fBshow\fR command. You might thus set up the cache, and update the whole thing once a week, while letting the automatic cache updates update the bugs you frequently refer to during the week. .Sp Some options affect the behaviour of the \fBcache\fR command. The first is the setting of \fB\-\-cache\-mode\fR, which controls how much \fBbts\fR downloads of the referenced links from the bug page, including boring bits such as the acknowledgement emails, emails to the control bot, and the mbox version of the bug report. It can take three values: \fBmin\fR (the minimum), \fBmbox\fR (download the minimum plus the mbox version of the bug report) or \fBfull\fR (the whole works). The second is \fB\-\-force\-refresh\fR or \&\fB\-f\fR, which forces the download, even if the cached bug report is up-to-date. The \fB\-\-include\-resolved\fR option indicates whether bug reports marked as resolved should be downloaded during caching. .Sp Each of these is configurable from the configuration file, as described below. They may also be specified after the \&\fBcache\fR command as well as at the start of the command line. .Sp Finally, \fB\-q\fR or \fB\-\-quiet\fR will suppress messages about caches being up-to-date, and giving the option twice will suppress all cache messages (except for error messages). .Sp Beware of caching \s-1RC,\s0 though: it will take a \s-1LONG\s0 time! (With 1000+ \&\s-1RC\s0 bugs and a delay of 5 seconds between bugs, you're looking at a minimum of 1.5 hours, and probably significantly more than that.) .IP "\fBcleancache\fR \fIpackage\fR | \fBsrc:\fR\fIpackage\fR | \fImaintainer\fR" 4 .IX Item "cleancache package | src:package | maintainer" .PD 0 .IP "\fBcleancache from:\fR\fIsubmitter\fR | \fBtag:\fR\fItag\fR | \fBusertag:\fR\fItag\fR | \fInumber\fR | \fB\s-1ALL\s0\fR" 4 .IX Item "cleancache from:submitter | tag:tag | usertag:tag | number | ALL" .PD Clean the cache for the specified \fIpackage\fR, \fImaintainer\fR, etc., as described above for the \fBbugs\fR command, or clean the entire cache if \&\fB\s-1ALL\s0\fR is specified. This is useful if you are going to have permanent network access or if the database has become corrupted for some reason. Note that for safety, this command does not default to the value of \fB\s-1DEBEMAIL\s0\fR or \fB\s-1EMAIL\s0\fR. .IP "\fBlistcachedbugs\fR [\fInumber\fR]" 4 .IX Item "listcachedbugs [number]" List cached bug ids (intended to support bash completion). The optional number argument restricts the list to those bug ids that start with that number. .IP "\fBversion\fR" 4 .IX Item "version" Display version and copyright information. .IP "\fBhelp\fR" 4 .IX Item "help" Display a short summary of commands, suspiciously similar to parts of this man page. .SH "ENVIRONMENT VARIABLES" .IX Header "ENVIRONMENT VARIABLES" .IP "\fB\s-1DEBEMAIL\s0\fR" 4 .IX Item "DEBEMAIL" If this is set, the From: line in the email will be set to use this email address instead of your normal email address (as would be determined by \&\fBmail\fR). .IP "\fB\s-1DEBFULLNAME\s0\fR" 4 .IX Item "DEBFULLNAME" If \fB\s-1DEBEMAIL\s0\fR is set, \fB\s-1DEBFULLNAME\s0\fR is examined to determine the full name to use; if this is not set, \fBbts\fR attempts to determine a name from your \fIpasswd\fR entry. .IP "\fB\s-1BROWSER\s0\fR" 4 .IX Item "BROWSER" If set, it specifies the browser to use for the \fBshow\fR and \fBbugs\fR options. See the description above. .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_OFFLINE\s0\fR" 4 .IX Item "BTS_OFFLINE" If this is set to \fByes\fR, then it is the same as the \fB\-\-offline\fR command line parameter being used. Only has an effect on the \fBshow\fR and \fBbugs\fR commands. The default is \fBno\fR. See the description of the \fBshow\fR command above for more information. .IP "\fB\s-1BTS_CACHE\s0\fR" 4 .IX Item "BTS_CACHE" If this is set to \fBno\fR, then it is the same as the \fB\-\-no\-cache\fR command line parameter being used. Only has an effect on the \fBshow\fR and \fBbug\fR commands. The default is \fByes\fR. Again, see the \fBshow\fR command above for more information. .IP "\fBBTS_CACHE_MODE=\fR{\fBmin\fR,\fBmbox\fR,\fBfull\fR}" 4 .IX Item "BTS_CACHE_MODE={min,mbox,full}" How much of the \s-1BTS\s0 should we mirror when we are asked to cache something? Just the minimum, or also the mbox or the whole thing? The default is \&\fBmin\fR, and it has the same meaning as the \fB\-\-cache\-mode\fR command line parameter. Only has an effect on the cache. See the \fBcache\fR command for more information. .IP "\fB\s-1BTS_FORCE_REFRESH\s0\fR" 4 .IX Item "BTS_FORCE_REFRESH" If this is set to \fByes\fR, then it is the same as the \fB\-\-force\-refresh\fR command line parameter being used. Only has an effect on the \fBcache\fR command. The default is \fBno\fR. See the \fBcache\fR command for more information. .IP "\fB\s-1BTS_MAIL_READER\s0\fR" 4 .IX Item "BTS_MAIL_READER" If this is set, specifies a mail reader to use instead of \fBmutt\fR. Same as the \fB\-\-mailreader\fR command line option. .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. .IP "\fB\s-1BTS_ONLY_NEW\s0\fR" 4 .IX Item "BTS_ONLY_NEW" Download only new bugs when caching. Do not check for updates in bugs we already have. The default is \fBno\fR. Same as the \fB\-\-only\-new\fR command line option. .IP "\fB\s-1BTS_SMTP_HOST\s0\fR" 4 .IX Item "BTS_SMTP_HOST" If this is set, specifies an \s-1SMTP\s0 host to use for sending mail rather than using the \fBsendmail\fR command. Same as the \fB\-\-smtp\-host\fR command line option. .Sp Note that this option takes priority over \fB\s-1BTS_SENDMAIL_COMMAND\s0\fR if both are set, unless the \fB\-\-sendmail\fR option is used. .IP "\fB\s-1BTS_SMTP_AUTH_USERNAME\s0\fR, \fB\s-1BTS_SMTP_AUTH_PASSWORD\s0\fR" 4 .IX Item "BTS_SMTP_AUTH_USERNAME, BTS_SMTP_AUTH_PASSWORD" If these options are set, then it is the same as the \fB\-\-smtp\-username\fR and \&\fB\-\-smtp\-password\fR options being used. .IP "\fB\s-1BTS_SMTP_HELO\s0\fR" 4 .IX Item "BTS_SMTP_HELO" Same as the \fB\-\-smtp\-helo\fR command line option. .IP "\fB\s-1BTS_INCLUDE_RESOLVED\s0\fR" 4 .IX Item "BTS_INCLUDE_RESOLVED" If this is set to \fBno\fR, then it is the same as the \fB\-\-no\-include\-resolved\fR command line parameter being used. Only has an effect on the \fBcache\fR command. The default is \fByes\fR. See the \fBcache\fR command for more information. .IP "\fB\s-1BTS_SUPPRESS_ACKS\s0\fR" 4 .IX Item "BTS_SUPPRESS_ACKS" If this is set to \fByes\fR, then it is the same as the \fB\-\-no\-ack\fR command line parameter being used. The default is \fBno\fR. .IP "\fB\s-1BTS_INTERACTIVE\s0\fR" 4 .IX Item "BTS_INTERACTIVE" If this is set to \fByes\fR or \fBforce\fR, then it is the same as the \&\fB\-\-interactive\fR or \fB\-\-force\-interactive\fR command line parameter being used. The default is \fBno\fR. .IP "\fB\s-1BTS_DEFAULT_CC\s0\fR" 4 .IX Item "BTS_DEFAULT_CC" Specify a list of e\-mail addresses to which a carbon copy of the generated e\-mail to the control bot should automatically be sent. .IP "\fB\s-1BTS_SERVER\s0\fR" 4 .IX Item "BTS_SERVER" Specify the name of a debbugs server which should be used instead of https://bugs.debian.org. .SH "SEE ALSO" .IX Header "SEE ALSO" Please see for more details on how to control the \s-1BTS\s0 using emails and for more information about the \s-1BTS.\s0 .PP \&\fBquerybts\fR\|(1), \fBreportbug\fR\|(1), \fBpts\-subscribe\fR\|(1), \fBdevscripts.conf\fR\|(5) .SH "COPYRIGHT" .IX Header "COPYRIGHT" This program is Copyright (C) 2001\-2003 by Joey Hess . Many modifications have been made, Copyright (C) 2002\-2005 Julian Gilbey and Copyright (C) 2007 Josh Triplett . .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.