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.
109 --use-default-cc
111 Add the addresses specified in the configuration file option
112 BTS_DEFAULT_CC to the list specified using --cc-addr. This is the
113 default.
114 --no-use-default-cc
116 Do not add addresses specified in BTS_DEFAULT_CC to the carbon copy
117 list.
118 --sendmail=SENDMAILCMD
120 Specify the sendmail command. The command will be split on white
121 space and will not be passed to a shell. Default is
122 /usr/sbin/sendmail. The -t option will be automatically added if
123 the command is /usr/sbin/sendmail or /usr/sbin/exim*. For other
124 mailers, if they require a -t option, this must be included in the
125 SENDMAILCMD, for example: --sendmail="/usr/sbin/mymailer -t".
126 --mutt
128 Use mutt for sending of mails. Default is not to use mutt, except
129 for some commands.
130 Note that one of $DEBEMAIL or $EMAIL must be set in the environment
132 in order to use mutt to send emails.
133 --no-mutt
135 Don't use mutt for sending of mails.
136 --soap-timeout=SECONDS
138 Specify a timeout for SOAP calls as used by the select and status
139 commands.
140 --smtp-host=SMTPHOST
142 Specify an SMTP host. If given, bts will send mail by talking
143 directly to this SMTP host rather than by invoking a sendmail
144 command.
145 The host name may be followed by a colon (":") and a port number in
147 order to use a port other than the default. It may also begin with
148 "ssmtp://" or "smtps://" to indicate that SMTPS should be used.
149 If SMTPS not specified, bts will still try to use STARTTLS if it's
151 advertised by the SMTP host.
152 Note that one of $DEBEMAIL or $EMAIL must be set in the environment
154 in order to use direct SMTP connections to send emails.
155 Note that when sending directly via an SMTP host, specifying
157 addresses in --cc-addr or BTS_DEFAULT_CC that the SMTP host will
158 not relay will cause the SMTP host to reject the entire mail.
159 Note also that the use of the reassign command may, when either
161 --interactive or --force-interactive mode is enabled, lead to the
162 automatic addition of a Cc to $newpackage@packages.debian.org. In
163 these cases, the note above regarding relaying applies. The
164 submission interface (port 587) on reportbug.debian.org does not
165 support relaying and, as such, should not be used as an SMTP server
166 for bts under the circumstances described in this paragraph.
167 --smtp-username=USERNAME, --smtp-password=PASSWORD
169 Specify the credentials to use when connecting to the SMTP server
170 specified by --smtp-host. If the server does not require
171 authentication then these options should not be used.
172 If a username is specified but not a password, bts will prompt for
174 the password before sending the mail.
175 --smtp-helo=HELO
177 Specify the name to use in the HELO command when connecting to the
178 SMTP server; defaults to the contents of the file /etc/mailname, if
179 it exists.
180 Note that some SMTP servers may reject the use of a HELO which
182 either does not resolve or does not appear to belong to the host
183 using it.
184 --bts-server
186 Use a debbugs server other than https://bugs.debian.org.
187 -f, --force-refresh
189 Download a bug report again, even if it does not appear to have
190 changed since the last cache command. Useful if a
191 --cache-mode=full is requested for the first time (otherwise
192 unchanged bug reports will not be downloaded again, even if the
193 boring bits have not been downloaded).
194 --no-force-refresh
196 Suppress any configuration file --force-refresh option.
197 --only-new
199 Download only new bugs when caching. Do not check for updates in
200 bugs we already have.
201 --include-resolved
203 When caching bug reports, include those that are marked as
204 resolved. This is the default behaviour.
205 --no-include-resolved
207 Reverse the behaviour of the previous option. That is, do not
208 cache bugs that are marked as resolved.
209 --no-ack
211 Suppress acknowledgment mails from the BTS. Note that this will
212 only affect the copies of messages CCed to bugs, not those sent to
213 the control bot.
214 --ack
216 Do not suppress acknowledgement mails. This is the default
217 behaviour.
218 -i, --interactive
220 Before sending an e-mail to the control bot, display the content
221 and allow it to be edited, or the sending cancelled.
222 --force-interactive
224 Similar to --interactive, with the exception that an editor is
225 spawned before prompting for confirmation of the message to be
226 sent.
227 --no-interactive
229 Send control e-mails without confirmation. This is the default
230 behaviour.
231 -q, --quiet
233 When running bts cache, only display information about newly cached
234 pages, not messages saying already cached. If this option is
235 specified twice, only output error messages (to stderr).
236 --no-conf, --noconf
238 Do not read any configuration files. This can only be used as the
239 first option given on the command-line.
240
242 For full details about the commands, see the BTS documentation.
243 <https://www.debian.org/Bugs/server-control>
244 show [options] [bug number | package | maintainer | : ] [opt=val ...]
246 show [options] [src:package | from:submitter] [opt=val ...]
247 show [options] [tag:tag | usertag:tag ] [opt=val ...]
248 show [release-critical | release-critical/... | RC]
249 This is a synonym for bts bugs.
250 bugs [options] [bug_number | package | maintainer | : ] [opt=val ...]
252 bugs [options] [src:package | from:submitter] [opt=val ...]
253 bugs [options] [tag:tag | usertag:tag ] [opt=val ...]
254 bugs [release-critical | release-critical/... | RC]
255 Display the page listing the requested bugs in a web browser using
256 sensible-browser(1).
257 Options may be specified after the bugs command in addition to or
259 instead of options at the start of the command line: recognised
260 options at this point are: -o/--offline/--online, -m/--mbox,
261 --mailreader and --[no-]cache. These are described earlier in this
262 manpage. If either the -o or --offline option is used, or there is
263 already an up-to-date copy in the local cache, the cached version
264 will be used.
265 The meanings of the possible arguments are as follows:
267 (none) If nothing is specified, bts bugs will display your bugs,
269 assuming that either DEBEMAIL or EMAIL (examined in that
270 order) is set to the appropriate email address.
271 bug_number
273 Display bug number bug_number.
274 package Display the bugs for the package package.
276 src:package
278 Display the bugs for the source package package.
279 maintainer
281 Display the bugs for the maintainer email address
282 maintainer.
283 from:submitter
285 Display the bugs for the submitter email address submitter.
286 tag:tag Display the bugs which are tagged with tag.
288 usertag:tag
290 Display the bugs which are tagged with usertag tag. See
291 the BTS documentation for more information on usertags.
292 This will require the use of a users=email option.
293 : Details of the bug tracking system itself, along with a
295 bug-request page with more options than this script, can be
296 found on https://bugs.debian.org/. This page itself will
297 be opened if the command 'bts bugs :' is used.
298 release-critical, RC
300 Display the front page of the release-critical pages on the
301 BTS. This is a synonym for
302 https://bugs.debian.org/release-critical/index.html. It is
303 also possible to say release-critical/debian/main.html and
304 the like. RC is a synonym for
305 release-critical/other/all.html.
306 After the argument specifying what to display, you can optionally
308 specify options to use to format the page or change what it
309 displayed. These are passed to the BTS in the URL downloaded. For
310 example, pass dist=stable to see bugs affecting the stable version
311 of a package, version=1.0 to see bugs affecting that version of a
312 package, or reverse=yes to display newest messages first in a bug
313 log.
314 If caching has been enabled (that is, --no-cache has not been used,
316 and BTS_CACHE has not been set to no), then any page requested by
317 bts show will automatically be cached, and be available offline
318 thereafter. Pages which are automatically cached in this way will
319 be deleted on subsequent "bts show|bugs|cache" invocations if they
320 have not been accessed in 30 days. Warning: on a filesystem
321 mounted with the "noatime" option, running "bts show|bugs" does not
322 update the cache files' access times; a cached bug will then be
323 subject to auto-cleaning 30 days after its initial download, even
324 if it has been accessed in the meantime.
325 Any other bts commands following this on the command line will be
327 executed after the browser has been exited.
328 The desired browser can be specified and configured by setting the
330 BROWSER environment variable. The conventions follow those defined
331 by Eric Raymond at http://www.catb.org/~esr/BROWSER/; we here
332 reproduce the relevant part.
333 The value of BROWSER may consist of a colon-separated series of
335 browser command parts. These should be tried in order until one
336 succeeds. Each command part may optionally contain the string %s;
337 if it does, the URL to be viewed is substituted there. If a command
338 part does not contain %s, the browser is to be launched as if the
339 URL had been supplied as its first argument. The string %% must be
340 substituted as a single %.
341 Rationale: We need to be able to specify multiple browser commands
343 so programs obeying this convention can do the right thing in
344 either X or console environments, trying X first. Specifying
345 multiple commands may also be useful for people who share files
346 like .profile across multiple systems. We need %s because some
347 popular browsers have remote-invocation syntax that requires it.
348 Unless %% reduces to %, it won't be possible to have a literal %s
349 in the string.
350 For example, on most Linux systems a good thing to do would be:
352 BROWSER='mozilla -raise -remote "openURL(%s,new-window)":links'
354 select [key:value ...]
356 Uses the SOAP interface to output a list of bugs which match the
357 given selection requirements.
358 The following keys are allowed, and may be given multiple times.
360 package Binary package name.
362 source Source package name.
364 maintainer
366 E-mail address of the maintainer.
367 submitter
369 E-mail address of the submitter.
370 severity
372 Bug severity.
373 status Status of the bug. One of open, done, or forwarded.
375 tag Tags applied to the bug. If users is specified, may include
377 usertags in addition to the standard tags.
378 owner Bug's owner.
380 correspondent
382 Address of someone who sent mail to the log.
383 affects Bugs which affect this package.
385 bugs List of bugs to search within.
387 users Users to use when looking up usertags.
389 archive Whether to search archived bugs or normal bugs; defaults to
391 0 (i.e. only search normal bugs). As a special case, if
392 archive is both, both archived and unarchived bugs are
393 returned.
394 For example, to select the set of bugs submitted by
396 jrandomdeveloper@example.com and tagged wontfix, one would use
397 bts select submitter:jrandomdeveloper@example.com tag:wontfix
399 If a key is used multiple times then the set of bugs selected
401 includes those matching any of the supplied values; for example
402 bts select package:foo severity:wishlist severity:minor
404 returns all bugs of package foo with either wishlist or minor
406 severity.
407 status [bug | file:file | fields:field[,field ...] | verbose] ...
409 Uses the SOAP interface to output status information for the given
410 bugs (or as read from the listed files -- use - to indicate STDIN).
411 By default, all populated fields for a bug are displayed.
413 If verbose is given, empty fields will also be displayed.
415 If fields is given, only those fields will be displayed. No
417 validity checking is performed on any specified fields.
418 clone bug new_ID [new_ID ...]
420 The clone control command allows you to duplicate a bug report. It
421 is useful in the case where a single report actually indicates that
422 multiple distinct bugs have occurred. "New IDs" are negative
423 numbers, separated by spaces, which may be used in subsequent
424 control commands to refer to the newly duplicated bugs. A new
425 report is generated for each new ID.
426 done bug [version]
428 Mark a bug as Done. This forces interactive mode since done
429 messages should include an explanation why the bug is being closed.
430 You should specify which version of the package closed the bug, if
431 possible.
432 reopen bug [submitter]
434 Reopen a bug, with optional submitter.
435 archive bug
437 Archive a bug that has previously been archived but is currently
438 not. The bug must fulfill all of the requirements for archiving
439 with the exception of those that are time-based.
440 unarchive bug
442 Unarchive a bug that is currently archived.
443 retitle bug title
445 Change the title of the bug.
446 summary bug [messagenum]
448 Select a message number that should be used as the summary of a
449 bug.
450 If no message number is given, the summary is cleared.
452 submitter bug [bug ...] submitter-email
454 Change the submitter address of a bug or a number of bugs, with !
455 meaning `use the address on the current email as the new submitter
456 address'.
457 reassign bug [bug ...] package [version]
459 Reassign a bug or a number of bugs to a different package. The
460 version field is optional; see the explanation at
461 <https://www.debian.org/Bugs/server-control>.
462 found bug [version]
464 Indicate that a bug was found to exist in a particular package
465 version. Without version, the list of fixed versions is cleared
466 and the bug is reopened.
467 notfound bug version
469 Remove the record that bug was encountered in the given version of
470 the package to which it is assigned.
471 fixed bug version
473 Indicate that a bug was fixed in a particular package version,
474 without affecting the bug's open/closed status.
475 notfixed bug version
477 Remove the record that a bug was fixed in the given version of the
478 package to which it is assigned.
479 This is equivalent to the sequence of commands "found bug version",
481 "notfound bug version".
482 block bug by|with bug [bug ...]
484 Note that a bug is blocked from being fixed by a set of other bugs.
485 unblock bug by|with bug [bug ...]
487 Note that a bug is no longer blocked from being fixed by a set of
488 other bugs.
489 merge bug bug [bug ...]
491 Merge a set of bugs together.
492 forcemerge bug bug [bug ...]
494 Forcibly merge a set of bugs together. The first bug listed is the
495 master bug, and its settings (those which must be equal in a normal
496 merge) are assigned to the bugs listed next.
497 unmerge bug
499 Unmerge a bug.
500 tag bug [+|-|=] tag [tag ...]
502 tags bug [+|-|=] tag [tag ...]
503 Set or unset a tag on a bug. The tag may either be the exact tag
504 name or it may be abbreviated to any unique tag substring. (So
505 using fixed will set the tag fixed, not fixed-upstream, for
506 example, but fix would not be acceptable.) Multiple tags may be
507 specified as well. The two commands (tag and tags) are identical.
508 At least one tag must be specified, unless the = flag is used,
509 where the command
510 bts tags <bug> =
512 will remove all tags from the specified bug.
514 Adding/removing the security tag will add
516 "team\@security.debian.org" to the Cc list of the control email.
517 The list of valid tags and their significance is available at
519 <https://www.debian.org/Bugs/Developer#tags>. The current valid
520 tags are:
521 patch, wontfix, moreinfo, unreproducible, fixed, help, security,
523 upstream, pending, d-i, confirmed, ipv6, lfs, fixed-upstream, l10n,
524 newcomer, a11y, ftbfs
525 There is also a tag for each release of Debian since "potato". Note
527 that this list may be out of date, see the website for the most up
528 to date source.
529 affects bug [+|-|=] package [package ...]
531 Indicates that a bug affects a package other than that against
532 which it is filed, causing the bug to be listed by default in the
533 package list of the other package. This should generally be used
534 where the bug is severe enough to cause multiple reports from users
535 to be assigned to the wrong package. At least one package must be
536 specified, unless the = flag is used, where the command
537 bts affects <bug> =
539 will remove all indications that bug affects other packages.
541 user email
543 Specify a user email address before using the usertags command.
544 usertag bug [+|-|=] tag [tag ...]
546 usertags bug [+|-|=] tag [tag ...]
547 Set or unset a user tag on a bug. The tag must be the exact tag
548 name wanted; there are no defaults or checking of tag names.
549 Multiple tags may be specified as well. The two commands (usertag
550 and usertags) are identical. At least one tag must be specified,
551 unless the = flag is used, where the command
552 bts usertags <bug> =
554 will remove all user tags from the specified bug.
556 claim bug [claim]
558 Record that you have claimed a bug (e.g. for a bug squashing
559 party). claim should be a unique token allowing the bugs you have
560 claimed to be identified; an e-mail address is often used.
561 If no claim is specified, the environment variable DEBEMAIL or
563 EMAIL (checked in that order) is used.
564 unclaim bug [claim]
566 Remove the record that you have claimed a bug.
567 If no claim is specified, the environment variable DEBEMAIL or
569 EMAIL (checked in that order) is used.
570 severity bug severity
572 Change the severity of a bug. Available severities are: wishlist,
573 minor, normal, important, serious, grave, critical. The severity
574 may be abbreviated to any unique substring.
575 forwarded bug address
577 Mark the bug as forwarded to the given address (usually an email
578 address or a URL for an upstream bug tracker).
579 notforwarded bug
581 Mark a bug as not forwarded.
582 package [package ...]
584 The following commands will only apply to bugs against the listed
585 packages; this acts as a safety mechanism for the BTS. If no
586 packages are listed, this check is turned off again.
587 limit [key[:value]] ...
589 The following commands will only apply to bugs which meet the
590 specified criterion; this acts as a safety mechanism for the BTS.
591 If no values are listed, the limits for that key are turned off
592 again. If no keys are specified, all limits are reset.
593 submitter
595 E-mail address of the submitter.
596 date Date the bug was submitted.
598 subject Subject of the bug.
600 msgid Message-id of the initial bug report.
602 package Binary package name.
604 source Source package name.
606 tag Tags applied to the bug.
608 severity
610 Bug severity.
611 owner Bug's owner.
613 affects Bugs affecting this package.
615 archive Whether to search archived bugs or normal bugs; defaults to
617 0 (i.e. only search normal bugs). As a special case, if
618 archive is both, both archived and unarchived bugs are
619 returned.
620 For example, to limit the set of bugs affected by the subsequent
622 control commands to those submitted by jrandomdeveloper@example.com
623 and tagged wontfix, one would use
624 bts limit submitter:jrandomdeveloper@example.com tag:wontfix
626 If a key is used multiple times then the set of bugs selected
628 includes those matching any of the supplied values; for example
629 bts limit package:foo severity:wishlist severity:minor
631 only applies the subsequent control commands to bugs of package foo
633 with either wishlist or minor severity.
634 owner bug owner-email
636 Change the "owner" address of a bug, with ! meaning `use the
637 address on the current email as the new owner address'.
638 The owner of a bug accepts responsibility for dealing with it.
640 noowner bug
642 Mark a bug as having no "owner".
643 subscribe bug [email]
645 Subscribe the given email address to the specified bug report. If
646 no email address is specified, the environment variable DEBEMAIL or
647 EMAIL (in that order) is used. If those are not set, or ! is given
648 as email address, your default address will be used.
649 After executing this command, you will be sent a subscription
651 confirmation to which you have to reply. When subscribed to a bug
652 report, you receive all relevant emails and notifications. Use the
653 unsubscribe command to unsubscribe.
654 unsubscribe bug [email]
656 Unsubscribe the given email address from the specified bug report.
657 As with subscribe above, if no email address is specified, the
658 environment variables DEBEMAIL or EMAIL (in that order) is used.
659 If those are not set, or ! is given as email address, your default
660 address will be used.
661 After executing this command, you will be sent an unsubscription
663 confirmation to which you have to reply. Use the subscribe command
664 to, well, subscribe.
665 reportspam bug ...
667 The reportspam command allows you to report a bug report as
668 containing spam. It saves one from having to go to the bug web
669 page to do so.
670 spamreport bug ...
672 spamreport is a synonym for reportspam.
673 cache [options] [maint_email | pkg | src:pkg | from:submitter]
675 cache [options] [release-critical | release-critical/... | RC]
676 Generate or update a cache of bug reports for the given email
677 address or package. By default it downloads all bugs belonging to
678 the email address in the DEBEMAIL environment variable (or the
679 EMAIL environment variable if DEBEMAIL is unset). This command may
680 be repeated to cache bugs belonging to several people or packages.
681 If multiple packages or addresses are supplied, bugs belonging to
682 any of the arguments will be cached; those belonging to more than
683 one of the arguments will only be downloaded once. The cached bugs
684 are stored in $XDG_CACHE_HOME/devscripts/bts/ or, if XDG_CACHE_HOME
685 is not set, in ~/.cache/devscripts/bts/.
686 You can use the cached bugs with the -o switch. For example:
688 bts -o bugs
690 bts -o show 12345
691 Also, bts will update the files in it in a piecemeal fashion as it
693 downloads information from the BTS using the show command. You
694 might thus set up the cache, and update the whole thing once a
695 week, while letting the automatic cache updates update the bugs you
696 frequently refer to during the week.
697 Some options affect the behaviour of the cache command. The first
699 is the setting of --cache-mode, which controls how much bts
700 downloads of the referenced links from the bug page, including
701 boring bits such as the acknowledgement emails, emails to the
702 control bot, and the mbox version of the bug report. It can take
703 three values: min (the minimum), mbox (download the minimum plus
704 the mbox version of the bug report) or full (the whole works). The
705 second is --force-refresh or -f, which forces the download, even if
706 the cached bug report is up-to-date. The --include-resolved option
707 indicates whether bug reports marked as resolved should be
708 downloaded during caching.
709 Each of these is configurable from the configuration file, as
711 described below. They may also be specified after the cache
712 command as well as at the start of the command line.
713 Finally, -q or --quiet will suppress messages about caches being
715 up-to-date, and giving the option twice will suppress all cache
716 messages (except for error messages).
717 Beware of caching RC, though: it will take a LONG time! (With
719 1000+ RC bugs and a delay of 5 seconds between bugs, you're looking
720 at a minimum of 1.5 hours, and probably significantly more than
721 that.)
722 cleancache package | src:package | maintainer
724 cleancache from:submitter | tag:tag | usertag:tag | number | ALL
725 Clean the cache for the specified package, maintainer, etc., as
726 described above for the bugs command, or clean the entire cache if
727 ALL is specified. This is useful if you are going to have permanent
728 network access or if the database has become corrupted for some
729 reason. Note that for safety, this command does not default to the
730 value of DEBEMAIL or EMAIL.
731 listcachedbugs [number]
733 List cached bug ids (intended to support bash completion). The
734 optional number argument restricts the list to those bug ids that
735 start with that number.
736 version
738 Display version and copyright information.
739 help
741 Display a short summary of commands, suspiciously similar to parts
742 of this man page.
743
745 DEBEMAIL
746 If this is set, the From: line in the email will be set to use this
747 email address instead of your normal email address (as would be
748 determined by mail).
749 DEBFULLNAME
751 If DEBEMAIL is set, DEBFULLNAME is examined to determine the full
752 name to use; if this is not set, bts attempts to determine a name
753 from your passwd entry.
754 BROWSER
756 If set, it specifies the browser to use for the show and bugs
757 options. See the description above.
758
760 The two configuration files /etc/devscripts.conf and ~/.devscripts are
761 sourced by a shell in that order to set configuration variables.
762 Command line options can be used to override configuration file
763 settings. Environment variable settings are ignored for this purpose.
764 The currently recognised variables are:
765 BTS_OFFLINE
767 If this is set to yes, then it is the same as the --offline command
768 line parameter being used. Only has an effect on the show and bugs
769 commands. The default is no. See the description of the show
770 command above for more information.
771 BTS_CACHE
773 If this is set to no, then it is the same as the --no-cache command
774 line parameter being used. Only has an effect on the show and bug
775 commands. The default is yes. Again, see the show command above
776 for more information.
777 BTS_CACHE_MODE={min,mbox,full}
779 How much of the BTS should we mirror when we are asked to cache
780 something? Just the minimum, or also the mbox or the whole thing?
781 The default is min, and it has the same meaning as the --cache-mode
782 command line parameter. Only has an effect on the cache. See the
783 cache command for more information.
784 BTS_FORCE_REFRESH
786 If this is set to yes, then it is the same as the --force-refresh
787 command line parameter being used. Only has an effect on the cache
788 command. The default is no. See the cache command for more
789 information.
790 BTS_MAIL_READER
792 If this is set, specifies a mail reader to use instead of mutt.
793 Same as the --mailreader command line option.
794 BTS_SENDMAIL_COMMAND
796 If this is set, specifies a sendmail command to use instead of
797 /usr/sbin/sendmail. Same as the --sendmail command line option.
798 BTS_ONLY_NEW
800 Download only new bugs when caching. Do not check for updates in
801 bugs we already have. The default is no. Same as the --only-new
802 command line option.
803 BTS_SMTP_HOST
805 If this is set, specifies an SMTP host to use for sending mail
806 rather than using the sendmail command. Same as the --smtp-host
807 command line option.
808 Note that this option takes priority over BTS_SENDMAIL_COMMAND if
810 both are set, unless the --sendmail option is used.
811 BTS_SMTP_AUTH_USERNAME, BTS_SMTP_AUTH_PASSWORD
813 If these options are set, then it is the same as the
814 --smtp-username and --smtp-password options being used.
815 BTS_SMTP_HELO
817 Same as the --smtp-helo command line option.
818 BTS_INCLUDE_RESOLVED
820 If this is set to no, then it is the same as the
821 --no-include-resolved command line parameter being used. Only has
822 an effect on the cache command. The default is yes. See the cache
823 command for more information.
824 BTS_SUPPRESS_ACKS
826 If this is set to yes, then it is the same as the --no-ack command
827 line parameter being used. The default is no.
828 BTS_INTERACTIVE
830 If this is set to yes or force, then it is the same as the
831 --interactive or --force-interactive command line parameter being
832 used. The default is no.
833 BTS_DEFAULT_CC
835 Specify a list of e-mail addresses to which a carbon copy of the
836 generated e-mail to the control bot should automatically be sent.
837 BTS_SERVER
839 Specify the name of a debbugs server which should be used instead
840 of https://bugs.debian.org.
841
843 Please see <https://www.debian.org/Bugs/server-control> for more
844 details on how to control the BTS using emails and
845 <https://www.debian.org/Bugs/> for more information about the BTS.
846 querybts(1), reportbug(1), pts-subscribe(1), devscripts.conf(5)
848
850 This program is Copyright (C) 2001-2003 by Joey Hess
851 <joeyh@debian.org>. Many modifications have been made, Copyright (C)
852 2002-2005 Julian Gilbey <jdg@debian.org> and Copyright (C) 2007 Josh
853 Triplett <josh@freedesktop.org>.
854 It is licensed under the terms of the GPL, either version 2 of the
856 License, or (at your option) any later version.
857Debian Utilities 2019-07-24 BTS(1)