1BTS(1) BTS(1)
2
6 bts - developers' command line interface to the BTS
7
9 bts [options] command [args] [#comment] [.|, command [args] [#comment]]
10 ...
11
13 This is a command line interface to the Debian Bug Tracking System
14 (BTS), intended mainly for use by developers. It lets the BTS be
15 manipulated using simple commands that can be run at the prompt or in a
16 script, does various sanity checks on the input, and constructs and
17 sends a mail to the BTS control address for you. A local cache of web
18 pages and e-mails from the BTS may also be created and updated.
19 In general, the command line interface is the same as what you would
21 write in a mail to control@bugs.debian.org, just prefixed with "bts".
22 For example:
23 % bts severity 69042 normal
25 % bts merge 69042 43233
26 % bts retitle 69042 blah blah
27 A few additional commands have been added for your convenience, and
29 this program is less strict about what constitutes a valid bug number.
30 For example, "severity Bug#85942 normal" is understood, as is "severity
31 #85942 normal". (Of course, your shell may regard "#" as a comment
32 character though, so you may need to quote it!)
33 Also, for your convenience, this program allows you to abbreviate
35 commands to the shortest unique substring (similar to how cvs lets you
36 abbreviate commands). So it understands things like "bts cl 85942".
37 It is also possible to include a comment in the mail sent to the BTS.
39 If your shell does not strip out the comment in a command like "bts
40 severity 30321 normal #inflated severity", then this program is smart
41 enough to figure out where the comment is, and include it in the email.
42 Note that most shells do strip out such comments before they get to the
43 program, unless the comment is quoted. (Something like "bts severity
44 #85942 normal" will not be treated as a comment!)
45 You can specify multiple commands by separating them with a single dot,
47 rather like update-rc.d; a single comma may also be used; all the
48 commands will then be sent in a single mail. It is important the
49 dot/comma is surrounded by whitespace so it is not mistaken for part of
50 a command. For example (quoting where necessary so that bts sees the
51 comment):
52 % bts severity 95672 normal , merge 95672 95673 \#they are the same!
54 The abbreviation "it" may be used to refer to the last mentioned bug
56 number, so you could write:
57 % bts severity 95672 wishlist , retitle it "bts: please add a --foo option"
59 Please use this program responsibly, and do take our users into
61 consideration.
62
64 bts examines the devscripts configuration files as described below.
65 Command line options override the configuration file settings, though.
66 -o, --offline
68 Make bts use cached bugs for the show and bugs commands, if a cache
69 is available for the requested data. See the cache command, below
70 for information on setting up a cache.
71 --online, --no-offline
73 Opposite of --offline; overrides any configuration file directive
74 to work offline.
75 -n, --no-action
77 Do not send emails but print them to standard output.
78 --cache, --no-cache
80 Should we attempt to cache new versions of BTS pages when
81 performing show/bugs commands? Default is to cache.
82 --cache-mode={min|mbox|full}
84 When running a bts cache command, should we only mirror the basic
85 bug (min), or should we also mirror the mbox version (mbox), or
86 should we mirror the whole thing, including the mbox and the boring
87 attachments to the BTS bug pages and the acknowledgement emails
88 (full)? Default is min.
89 --cache-delay=seconds
91 Time in seconds to delay between each download, to avoid hammering
92 the BTS web server. Default is 5 seconds.
93 --mbox
95 Open a mail reader to read the mbox corresponding to a given bug
96 number for show and bugs commands.
97 --mailreader=READER
99 Specify the command to read the mbox. Must contain a "%s" string
100 (unquoted!), which will be replaced by the name of the mbox file.
101 The command will be split on white space and will not be passed to
102 a shell. Default is 'mutt -f %s'. (Also, %% will be substituted
103 by a single % if this is needed.)
104 --cc-addr=CC_EMAIL_ADDRESS
106 Send carbon copies to a list of users. CC_EMAIL_ADDRESS should be a
107 comma-separated list of email addresses.
108 --use-default-cc
110 Add the addresses specified in the configuration file option
111 BTS_DEFAULT_CC to the list specified using --cc-addr. This is the
112 default.
113 --no-use-default-cc
115 Do not add addresses specified in BTS_DEFAULT_CC to the carbon copy
116 list.
117 --sendmail=SENDMAILCMD
119 Specify the sendmail command. The command will be split on white
120 space and will not be passed to a shell. Default is
121 /usr/sbin/sendmail. The -t option will be automatically added if
122 the command is /usr/sbin/sendmail or /usr/sbin/exim*. For other
123 mailers, if they require a -t option, this must be included in the
124 SENDMAILCMD, for example: --sendmail="/usr/sbin/mymailer -t".
125 --mutt
127 Use mutt for sending of mails. Default is not to use mutt, except
128 for some commands.
129 Note that one of $DEBEMAIL or $EMAIL must be set in the environment
131 in order to use mutt to send emails.
132 --no-mutt
134 Don't use mutt for sending of mails.
135 --soap-timeout=SECONDS
137 Specify a timeout for SOAP calls as used by the select and status
138 commands.
139 --smtp-host=SMTPHOST
141 Specify an SMTP host. If given, bts will send mail by talking
142 directly to this SMTP host rather than by invoking a sendmail
143 command.
144 The host name may be followed by a colon (":") and a port number in
146 order to use a port other than the default. It may also begin with
147 "ssmtp://" or "smtps://" to indicate that SMTPS should be used.
148 If SMTPS not specified, bts will still try to use STARTTLS if it's
150 advertised by the SMTP host.
151 Note that one of $DEBEMAIL or $EMAIL must be set in the environment
153 in order to use direct SMTP connections to send emails.
154 Note that when sending directly via an SMTP host, specifying
156 addresses in --cc-addr or BTS_DEFAULT_CC that the SMTP host will
157 not relay will cause the SMTP host to reject the entire mail.
158 Note also that the use of the reassign command may, when either
160 --interactive or --force-interactive mode is enabled, lead to the
161 automatic addition of a Cc to $newpackage@packages.debian.org. In
162 these cases, the note above regarding relaying applies. The
163 submission interface (port 587) on reportbug.debian.org does not
164 support relaying and, as such, should not be used as an SMTP server
165 for bts under the circumstances described in this paragraph.
166 --smtp-username=USERNAME, --smtp-password=PASSWORD
168 Specify the credentials to use when connecting to the SMTP server
169 specified by --smtp-host. If the server does not require
170 authentication then these options should not be used.
171 If a username is specified but not a password, bts will prompt for
173 the password before sending the mail.
174 --smtp-helo=HELO
176 Specify the name to use in the HELO command when connecting to the
177 SMTP server; defaults to the contents of the file /etc/mailname, if
178 it exists.
179 Note that some SMTP servers may reject the use of a HELO which
181 either does not resolve or does not appear to belong to the host
182 using it.
183 --bts-server
185 Use a debbugs server other than https://bugs.debian.org.
186 -f, --force-refresh
188 Download a bug report again, even if it does not appear to have
189 changed since the last cache command. Useful if a
190 --cache-mode=full is requested for the first time (otherwise
191 unchanged bug reports will not be downloaded again, even if the
192 boring bits have not been downloaded).
193 --no-force-refresh
195 Suppress any configuration file --force-refresh option.
196 --only-new
198 Download only new bugs when caching. Do not check for updates in
199 bugs we already have.
200 --include-resolved
202 When caching bug reports, include those that are marked as
203 resolved. This is the default behaviour.
204 --no-include-resolved
206 Reverse the behaviour of the previous option. That is, do not
207 cache bugs that are marked as resolved.
208 --no-ack
210 Suppress acknowledgment mails from the BTS. Note that this will
211 only affect the copies of messages CCed to bugs, not those sent to
212 the control bot.
213 --ack
215 Do not suppress acknowledgement mails. This is the default
216 behaviour.
217 -i, --interactive
219 Before sending an e-mail to the control bot, display the content
220 and allow it to be edited, or the sending cancelled.
221 --force-interactive
223 Similar to --interactive, with the exception that an editor is
224 spawned before prompting for confirmation of the message to be
225 sent.
226 --no-interactive
228 Send control e-mails without confirmation. This is the default
229 behaviour.
230 -q, --quiet
232 When running bts cache, only display information about newly cached
233 pages, not messages saying already cached. If this option is
234 specified twice, only output error messages (to stderr).
235 --no-conf, --noconf
237 Do not read any configuration files. This can only be used as the
238 first option given on the command-line.
239
241 For full details about the commands, see the BTS documentation.
242 <https://www.debian.org/Bugs/server-control>
243 show [options] [bug number | package | maintainer | : ] [opt=val ...]
245 show [options] [src:package | from:submitter] [opt=val ...]
246 show [options] [tag:tag | usertag:tag ] [opt=val ...]
247 show [release-critical | release-critical/... | RC]
248 This is a synonym for bts bugs.
249 bugs [options] [bug_number | package | maintainer | : ] [opt=val ...]
251 bugs [options] [src:package | from:submitter] [opt=val ...]
252 bugs [options] [tag:tag | usertag:tag ] [opt=val ...]
253 bugs [release-critical | release-critical/... | RC]
254 Display the page listing the requested bugs in a web browser using
255 sensible-browser(1).
256 Options may be specified after the bugs command in addition to or
258 instead of options at the start of the command line: recognised
259 options at this point are: -o/--offline/--online, -m/--mbox,
260 --mailreader and --[no-]cache. These are described earlier in this
261 manpage. If either the -o or --offline option is used, or there is
262 already an up-to-date copy in the local cache, the cached version
263 will be used.
264 The meanings of the possible arguments are as follows:
266 (none) If nothing is specified, bts bugs will display your bugs,
268 assuming that either DEBEMAIL or EMAIL (examined in that
269 order) is set to the appropriate email address.
270 bug_number
272 Display bug number bug_number.
273 package Display the bugs for the package package.
275 src:package
277 Display the bugs for the source package package.
278 maintainer
280 Display the bugs for the maintainer email address
281 maintainer.
282 from:submitter
284 Display the bugs for the submitter email address submitter.
285 tag:tag Display the bugs which are tagged with tag.
287 usertag:tag
289 Display the bugs which are tagged with usertag tag. See
290 the BTS documentation for more information on usertags.
291 This will require the use of a users=email option.
292 : Details of the bug tracking system itself, along with a
294 bug-request page with more options than this script, can be
295 found on https://bugs.debian.org/. This page itself will
296 be opened if the command 'bts bugs :' is used.
297 release-critical, RC
299 Display the front page of the release-critical pages on the
300 BTS. This is a synonym for
301 https://bugs.debian.org/release-critical/index.html. It is
302 also possible to say release-critical/debian/main.html and
303 the like. RC is a synonym for
304 release-critical/other/all.html.
305 After the argument specifying what to display, you can optionally
307 specify options to use to format the page or change what it
308 displayed. These are passed to the BTS in the URL downloaded. For
309 example, pass dist=stable to see bugs affecting the stable version
310 of a package, version=1.0 to see bugs affecting that version of a
311 package, or reverse=yes to display newest messages first in a bug
312 log.
313 If caching has been enabled (that is, --no-cache has not been used,
315 and BTS_CACHE has not been set to no), then any page requested by
316 bts show will automatically be cached, and be available offline
317 thereafter. Pages which are automatically cached in this way will
318 be deleted on subsequent "bts show|bugs|cache" invocations if they
319 have not been accessed in 30 days. Warning: on a filesystem
320 mounted with the "noatime" option, running "bts show|bugs" does not
321 update the cache files' access times; a cached bug will then be
322 subject to auto-cleaning 30 days after its initial download, even
323 if it has been accessed in the meantime.
324 Any other bts commands following this on the command line will be
326 executed after the browser has been exited.
327 The desired browser can be specified and configured by setting the
329 BROWSER environment variable. The conventions follow those defined
330 by Eric Raymond at http://www.catb.org/~esr/BROWSER/; we here
331 reproduce the relevant part.
332 The value of BROWSER may consist of a colon-separated series of
334 browser command parts. These should be tried in order until one
335 succeeds. Each command part may optionally contain the string %s;
336 if it does, the URL to be viewed is substituted there. If a command
337 part does not contain %s, the browser is to be launched as if the
338 URL had been supplied as its first argument. The string %% must be
339 substituted as a single %.
340 Rationale: We need to be able to specify multiple browser commands
342 so programs obeying this convention can do the right thing in
343 either X or console environments, trying X first. Specifying
344 multiple commands may also be useful for people who share files
345 like .profile across multiple systems. We need %s because some
346 popular browsers have remote-invocation syntax that requires it.
347 Unless %% reduces to %, it won't be possible to have a literal %s
348 in the string.
349 For example, on most Linux systems a good thing to do would be:
351 BROWSER='mozilla -raise -remote "openURL(%s,new-window)":links'
353 select [key:value ...]
355 Uses the SOAP interface to output a list of bugs which match the
356 given selection requirements.
357 The following keys are allowed, and may be given multiple times.
359 package Binary package name.
361 source Source package name.
363 maintainer
365 E-mail address of the maintainer.
366 submitter
368 E-mail address of the submitter.
369 severity
371 Bug severity.
372 status Status of the bug. One of open, done, or forwarded.
374 tag Tags applied to the bug. If users is specified, may include
376 usertags in addition to the standard tags.
377 owner Bug's owner.
379 correspondent
381 Address of someone who sent mail to the log.
382 affects Bugs which affect this package.
384 bugs List of bugs to search within.
386 users Users to use when looking up usertags.
388 archive Whether to search archived bugs or normal bugs; defaults to
390 0 (i.e. only search normal bugs). As a special case, if
391 archive is both, both archived and unarchived bugs are
392 returned.
393 For example, to select the set of bugs submitted by
395 jrandomdeveloper@example.com and tagged wontfix, one would use
396 bts select submitter:jrandomdeveloper@example.com tag:wontfix
398 If a key is used multiple times then the set of bugs selected
400 includes those matching any of the supplied values; for example
401 bts select package:foo severity:wishlist severity:minor
403 returns all bugs of package foo with either wishlist or minor
405 severity.
406 status [bug | file:file | fields:field[,field ...] | verbose] ...
408 Uses the SOAP interface to output status information for the given
409 bugs (or as read from the listed files -- use - to indicate STDIN).
410 By default, all populated fields for a bug are displayed.
412 If verbose is given, empty fields will also be displayed.
414 If fields is given, only those fields will be displayed. No
416 validity checking is performed on any specified fields.
417 clone bug new_ID [new_ID ...]
419 The clone control command allows you to duplicate a bug report. It
420 is useful in the case where a single report actually indicates that
421 multiple distinct bugs have occurred. "New IDs" are negative
422 numbers, separated by spaces, which may be used in subsequent
423 control commands to refer to the newly duplicated bugs. A new
424 report is generated for each new ID.
425 done bug [version]
427 Mark a bug as Done. This forces interactive mode since done
428 messages should include an explanation why the bug is being closed.
429 You should specify which version of the package closed the bug, if
430 possible.
431 reopen bug [submitter]
433 Reopen a bug, with optional submitter.
434 archive bug
436 Archive a bug that has previously been archived but is currently
437 not. The bug must fulfill all of the requirements for archiving
438 with the exception of those that are time-based.
439 unarchive bug
441 Unarchive a bug that is currently archived.
442 retitle bug title
444 Change the title of the bug.
445 summary bug [messagenum]
447 Select a message number that should be used as the summary of a
448 bug.
449 If no message number is given, the summary is cleared.
451 submitter bug [bug ...] submitter-email
453 Change the submitter address of a bug or a number of bugs, with !
454 meaning `use the address on the current email as the new submitter
455 address'.
456 reassign bug [bug ...] package [version]
458 Reassign a bug or a number of bugs to a different package. The
459 version field is optional; see the explanation at
460 <https://www.debian.org/Bugs/server-control>.
461 found bug [version]
463 Indicate that a bug was found to exist in a particular package
464 version. Without version, the list of fixed versions is cleared
465 and the bug is reopened.
466 notfound bug version
468 Remove the record that bug was encountered in the given version of
469 the package to which it is assigned.
470 fixed bug version
472 Indicate that a bug was fixed in a particular package version,
473 without affecting the bug's open/closed status.
474 notfixed bug version
476 Remove the record that a bug was fixed in the given version of the
477 package to which it is assigned.
478 This is equivalent to the sequence of commands "found bug version",
480 "notfound bug version".
481 block bug by|with bug [bug ...]
483 Note that a bug is blocked from being fixed by a set of other bugs.
484 unblock bug by|with bug [bug ...]
486 Note that a bug is no longer blocked from being fixed by a set of
487 other bugs.
488 merge bug bug [bug ...]
490 Merge a set of bugs together.
491 forcemerge bug bug [bug ...]
493 Forcibly merge a set of bugs together. The first bug listed is the
494 master bug, and its settings (those which must be equal in a normal
495 merge) are assigned to the bugs listed next.
496 unmerge bug
498 Unmerge a bug.
499 tag bug [+|-|=] tag [tag ...]
501 tags bug [+|-|=] tag [tag ...]
502 Set or unset a tag on a bug. The tag may either be the exact tag
503 name or it may be abbreviated to any unique tag substring. (So
504 using fixed will set the tag fixed, not fixed-upstream, for
505 example, but fix would not be acceptable.) Multiple tags may be
506 specified as well. The two commands (tag and tags) are identical.
507 At least one tag must be specified, unless the = flag is used,
508 where the command
509 bts tags <bug> =
511 will remove all tags from the specified bug.
513 Adding/removing the security tag will add
515 "team\@security.debian.org" to the Cc list of the control email.
516 The list of valid tags and their significance is available at
518 <https://www.debian.org/Bugs/Developer#tags>. The current valid
519 tags are:
520 patch, wontfix, moreinfo, unreproducible, fixed, help, security,
522 upstream, pending, d-i, confirmed, ipv6, lfs, fixed-upstream, l10n,
523 newcomer, a11y, ftbfs
524 There is also a tag for each release of Debian since "potato". Note
526 that this list may be out of date, see the website for the most up
527 to date source.
528 affects bug [+|-|=] package [package ...]
530 Indicates that a bug affects a package other than that against
531 which it is filed, causing the bug to be listed by default in the
532 package list of the other package. This should generally be used
533 where the bug is severe enough to cause multiple reports from users
534 to be assigned to the wrong package. At least one package must be
535 specified, unless the = flag is used, where the command
536 bts affects <bug> =
538 will remove all indications that bug affects other packages.
540 user email
542 Specify a user email address before using the usertags command.
543 usertag bug [+|-|=] tag [tag ...]
545 usertags bug [+|-|=] tag [tag ...]
546 Set or unset a user tag on a bug. The tag must be the exact tag
547 name wanted; there are no defaults or checking of tag names.
548 Multiple tags may be specified as well. The two commands (usertag
549 and usertags) are identical. At least one tag must be specified,
550 unless the = flag is used, where the command
551 bts usertags <bug> =
553 will remove all user tags from the specified bug.
555 claim bug [claim]
557 Record that you have claimed a bug (e.g. for a bug squashing
558 party). claim should be a unique token allowing the bugs you have
559 claimed to be identified; an e-mail address is often used.
560 If no claim is specified, the environment variable DEBEMAIL or
562 EMAIL (checked in that order) is used.
563 unclaim bug [claim]
565 Remove the record that you have claimed a bug.
566 If no claim is specified, the environment variable DEBEMAIL or
568 EMAIL (checked in that order) is used.
569 severity bug severity
571 Change the severity of a bug. Available severities are: wishlist,
572 minor, normal, important, serious, grave, critical. The severity
573 may be abbreviated to any unique substring.
574 forwarded bug address
576 Mark the bug as forwarded to the given address (usually an email
577 address or a URL for an upstream bug tracker).
578 notforwarded bug
580 Mark a bug as not forwarded.
581 package [package ...]
583 The following commands will only apply to bugs against the listed
584 packages; this acts as a safety mechanism for the BTS. If no
585 packages are listed, this check is turned off again.
586 limit [key[:value]] ...
588 The following commands will only apply to bugs which meet the
589 specified criterion; this acts as a safety mechanism for the BTS.
590 If no values are listed, the limits for that key are turned off
591 again. If no keys are specified, all limits are reset.
592 submitter
594 E-mail address of the submitter.
595 date Date the bug was submitted.
597 subject Subject of the bug.
599 msgid Message-id of the initial bug report.
601 package Binary package name.
603 source Source package name.
605 tag Tags applied to the bug.
607 severity
609 Bug severity.
610 owner Bug's owner.
612 affects Bugs affecting this package.
614 archive Whether to search archived bugs or normal bugs; defaults to
616 0 (i.e. only search normal bugs). As a special case, if
617 archive is both, both archived and unarchived bugs are
618 returned.
619 For example, to limit the set of bugs affected by the subsequent
621 control commands to those submitted by jrandomdeveloper@example.com
622 and tagged wontfix, one would use
623 bts limit submitter:jrandomdeveloper@example.com tag:wontfix
625 If a key is used multiple times then the set of bugs selected
627 includes those matching any of the supplied values; for example
628 bts limit package:foo severity:wishlist severity:minor
630 only applies the subsequent control commands to bugs of package foo
632 with either wishlist or minor severity.
633 owner bug owner-email
635 Change the "owner" address of a bug, with ! meaning `use the
636 address on the current email as the new owner address'.
637 The owner of a bug accepts responsibility for dealing with it.
639 noowner bug
641 Mark a bug as having no "owner".
642 subscribe bug [email]
644 Subscribe the given email address to the specified bug report. If
645 no email address is specified, the environment variable DEBEMAIL or
646 EMAIL (in that order) is used. If those are not set, or ! is given
647 as email address, your default address will be used.
648 After executing this command, you will be sent a subscription
650 confirmation to which you have to reply. When subscribed to a bug
651 report, you receive all relevant emails and notifications. Use the
652 unsubscribe command to unsubscribe.
653 unsubscribe bug [email]
655 Unsubscribe the given email address from the specified bug report.
656 As with subscribe above, if no email address is specified, the
657 environment variables DEBEMAIL or EMAIL (in that order) is used.
658 If those are not set, or ! is given as email address, your default
659 address will be used.
660 After executing this command, you will be sent an unsubscription
662 confirmation to which you have to reply. Use the subscribe command
663 to, well, subscribe.
664 reportspam bug ...
666 The reportspam command allows you to report a bug report as
667 containing spam. It saves one from having to go to the bug web
668 page to do so.
669 spamreport bug ...
671 spamreport is a synonym for reportspam.
672 cache [options] [maint_email | pkg | src:pkg | from:submitter]
674 cache [options] [release-critical | release-critical/... | RC]
675 Generate or update a cache of bug reports for the given email
676 address or package. By default it downloads all bugs belonging to
677 the email address in the DEBEMAIL environment variable (or the
678 EMAIL environment variable if DEBEMAIL is unset). This command may
679 be repeated to cache bugs belonging to several people or packages.
680 If multiple packages or addresses are supplied, bugs belonging to
681 any of the arguments will be cached; those belonging to more than
682 one of the arguments will only be downloaded once. The cached bugs
683 are stored in $XDG_CACHE_HOME/devscripts/bts/ or, if XDG_CACHE_HOME
684 is not set, in ~/.cache/devscripts/bts/.
685 You can use the cached bugs with the -o switch. For example:
687 bts -o bugs
689 bts -o show 12345
690 Also, bts will update the files in it in a piecemeal fashion as it
692 downloads information from the BTS using the show command. You
693 might thus set up the cache, and update the whole thing once a
694 week, while letting the automatic cache updates update the bugs you
695 frequently refer to during the week.
696 Some options affect the behaviour of the cache command. The first
698 is the setting of --cache-mode, which controls how much bts
699 downloads of the referenced links from the bug page, including
700 boring bits such as the acknowledgement emails, emails to the
701 control bot, and the mbox version of the bug report. It can take
702 three values: min (the minimum), mbox (download the minimum plus
703 the mbox version of the bug report) or full (the whole works). The
704 second is --force-refresh or -f, which forces the download, even if
705 the cached bug report is up-to-date. The --include-resolved option
706 indicates whether bug reports marked as resolved should be
707 downloaded during caching.
708 Each of these is configurable from the configuration file, as
710 described below. They may also be specified after the cache
711 command as well as at the start of the command line.
712 Finally, -q or --quiet will suppress messages about caches being
714 up-to-date, and giving the option twice will suppress all cache
715 messages (except for error messages).
716 Beware of caching RC, though: it will take a LONG time! (With
718 1000+ RC bugs and a delay of 5 seconds between bugs, you're looking
719 at a minimum of 1.5 hours, and probably significantly more than
720 that.)
721 cleancache package | src:package | maintainer
723 cleancache from:submitter | tag:tag | usertag:tag | number | ALL
724 Clean the cache for the specified package, maintainer, etc., as
725 described above for the bugs command, or clean the entire cache if
726 ALL is specified. This is useful if you are going to have permanent
727 network access or if the database has become corrupted for some
728 reason. Note that for safety, this command does not default to the
729 value of DEBEMAIL or EMAIL.
730 listcachedbugs [number]
732 List cached bug ids (intended to support bash completion). The
733 optional number argument restricts the list to those bug ids that
734 start with that number.
735 version
737 Display version and copyright information.
738 help
740 Display a short summary of commands, suspiciously similar to parts
741 of this man page.
742
744 DEBEMAIL
745 If this is set, the From: line in the email will be set to use this
746 email address instead of your normal email address (as would be
747 determined by mail).
748 DEBFULLNAME
750 If DEBEMAIL is set, DEBFULLNAME is examined to determine the full
751 name to use; if this is not set, bts attempts to determine a name
752 from your passwd entry.
753 BROWSER
755 If set, it specifies the browser to use for the show and bugs
756 options. See the description above.
757
759 The two configuration files /etc/devscripts.conf and ~/.devscripts are
760 sourced by a shell in that order to set configuration variables.
761 Command line options can be used to override configuration file
762 settings. Environment variable settings are ignored for this purpose.
763 The currently recognised variables are:
764 BTS_OFFLINE
766 If this is set to yes, then it is the same as the --offline command
767 line parameter being used. Only has an effect on the show and bugs
768 commands. The default is no. See the description of the show
769 command above for more information.
770 BTS_CACHE
772 If this is set to no, then it is the same as the --no-cache command
773 line parameter being used. Only has an effect on the show and bug
774 commands. The default is yes. Again, see the show command above
775 for more information.
776 BTS_CACHE_MODE={min,mbox,full}
778 How much of the BTS should we mirror when we are asked to cache
779 something? Just the minimum, or also the mbox or the whole thing?
780 The default is min, and it has the same meaning as the --cache-mode
781 command line parameter. Only has an effect on the cache. See the
782 cache command for more information.
783 BTS_FORCE_REFRESH
785 If this is set to yes, then it is the same as the --force-refresh
786 command line parameter being used. Only has an effect on the cache
787 command. The default is no. See the cache command for more
788 information.
789 BTS_MAIL_READER
791 If this is set, specifies a mail reader to use instead of mutt.
792 Same as the --mailreader command line option.
793 BTS_SENDMAIL_COMMAND
795 If this is set, specifies a sendmail command to use instead of
796 /usr/sbin/sendmail. Same as the --sendmail command line option.
797 BTS_ONLY_NEW
799 Download only new bugs when caching. Do not check for updates in
800 bugs we already have. The default is no. Same as the --only-new
801 command line option.
802 BTS_SMTP_HOST
804 If this is set, specifies an SMTP host to use for sending mail
805 rather than using the sendmail command. Same as the --smtp-host
806 command line option.
807 Note that this option takes priority over BTS_SENDMAIL_COMMAND if
809 both are set, unless the --sendmail option is used.
810 BTS_SMTP_AUTH_USERNAME, BTS_SMTP_AUTH_PASSWORD
812 If these options are set, then it is the same as the
813 --smtp-username and --smtp-password options being used.
814 BTS_SMTP_HELO
816 Same as the --smtp-helo command line option.
817 BTS_INCLUDE_RESOLVED
819 If this is set to no, then it is the same as the
820 --no-include-resolved command line parameter being used. Only has
821 an effect on the cache command. The default is yes. See the cache
822 command for more information.
823 BTS_SUPPRESS_ACKS
825 If this is set to yes, then it is the same as the --no-ack command
826 line parameter being used. The default is no.
827 BTS_INTERACTIVE
829 If this is set to yes or force, then it is the same as the
830 --interactive or --force-interactive command line parameter being
831 used. The default is no.
832 BTS_DEFAULT_CC
834 Specify a list of e-mail addresses to which a carbon copy of the
835 generated e-mail to the control bot should automatically be sent.
836 BTS_SERVER
838 Specify the name of a debbugs server which should be used instead
839 of https://bugs.debian.org.
840
842 Please see <https://www.debian.org/Bugs/server-control> for more
843 details on how to control the BTS using emails and
844 <https://www.debian.org/Bugs/> for more information about the BTS.
845 querybts(1), reportbug(1), pts-subscribe(1), devscripts.conf(5)
847
849 This program is Copyright (C) 2001-2003 by Joey Hess
850 <joeyh@debian.org>. Many modifications have been made, Copyright (C)
851 2002-2005 Julian Gilbey <jdg@debian.org> and Copyright (C) 2007 Josh
852 Triplett <josh@freedesktop.org>.
853 It is licensed under the terms of the GPL, either version 2 of the
855 License, or (at your option) any later version.
856Debian Utilities 2018-12-10 BTS(1)