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