You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

568 lines
22 KiB

  1. .TH reportbug 1
  2. .SH NAME
  3. reportbug \- reports a bug to a debbugs server
  5. .B reportbug
  6. .I "[options] <package | pseudo-package | absolute-pathname>"
  8. .B reportbug
  9. is primarily designed to report bugs in the Debian distribution; by
  10. default, it creates an email to the Debian bug tracking system at
  11. \\fP with information about the bug you've
  12. found, and makes a carbon copy of the report for you as well.
  13. .PP
  14. Using the \fB\-\-bts\fP option, you can also report bugs to other
  15. servers that use the Debian bug tracking system, \fBdebbugs\fP.
  16. .PP
  17. You may specify either a package name or a filename; if you use a
  18. filename, it must either be an absolute filename (so beginning with a
  19. \fB/\fP) or if you want \fBreportbug\fP to search the system for a
  20. filename, see the \fB\-\-filename\fP and \fP\-\-path\fP options
  21. below. If installed, also \fBdlocate\fP is used to identify the
  22. filename location and thus the package containing it.
  23. .PP
  24. You can also specify a \fBpseudo-package\fP; these are used in the
  25. Debian bug tracking system to track issues that are not related to one
  26. specific package. Run \fBreportbug\fP without any arguments, then
  27. enter \fBother\fP at the package prompt, to see a list of the most
  28. commonly-used \fBpseudo-packages\fP.
  30. The program follows the usual GNU command line syntax, with long
  31. options starting with two dashes (`\fB\-\-\fP'). A summary of options
  32. are included below.
  33. .TP
  34. .B \-h, \-\-help
  35. Show summary of options.
  36. .TP
  37. .B \-\-version
  38. Show the version of \fBreportbug\fP and exit.
  39. .TP
  40. .B \-A FILENAME, \-\-attach=FILENAME
  41. Attach a file to the bug report; both text and binary files are
  42. acceptable; this option can be specified multiple times to attach
  43. several files. This routine will create a MIME attachment with the
  44. file included; in some cases (usually text files), it is probably
  45. better to use \fB\-i/\-\-include\fP option. (Please note that
  46. Debian's bug tracking system has limited support for MIME
  47. attachments.)
  48. This option supports also globbing (i.e. names with wildcards, like
  49. file.*) but remember to include them between single quotes (the
  50. previous example becomes: 'file.*') else the shell would expand it
  51. before calling reportbug leading to an error.
  52. Be aware that when using an external MUA to send the message (such
  53. as mutt), the attachment feature is not available and no file will
  54. be attached at all: the MUA feature to attach files must be used
  55. instead (so from within the MUA).
  56. .TP
  57. .B \-b, \-\-no\-query\-bts
  58. Don't check the Debian bug tracking system to see if this problem has
  59. already been reported; useful for offline use or if you're
  60. \fBreally\fP sure it's a bug.
  61. .TP
  62. .B \-\-query\-bts
  63. Check the Debian bug tracking system to see if this problem has
  64. already been reported (default).
  65. .TP
  66. .B \-B SYSTEM, \-\-bts=SYSTEM
  67. Instead of the Debian bug server (or the bug server specified in
  68. \fB/etc/reportbug.conf\fP, use the server specified by \fBSYSTEM\fP.
  69. .TP
  70. .B \-\-body=BODY
  71. Use the specified \fIBODY\fP as the body of the message. The body
  72. text will be wrapped at 70 columns, and the normal \fBreportbug\fP
  73. headers and footers will be added as appropriate. The editor prompt
  74. and any "special" prompting will be bypassed.
  75. .TP
  76. .B \-\-body\-file=BODYFILE, \-\-bodyfile=BODYFILE
  77. The contents of the (assumed to be) text file \fIBODYFILE\fP will be
  78. used as the message body. This file is assumed to be properly
  79. formatted (i.e. reasonable line lengths, etc.). The usual headers and
  80. footers will be added, and the editor step and "special" prompts will
  81. be skipped. (\fIBODYFILE\fP may also be a named pipe; using a device
  82. special file may lead to unusual results.)
  83. .TP
  84. .B \-c, \-\-no\-config\-files
  85. Omit configuration files from the bug report without asking. By
  86. default, you are asked if you want to include them; in some cases,
  87. doing so may cause sensitive information to be sent via email.
  88. .TP
  89. .B \-C CLASS, \-\-class=CLASS
  90. Specify report class for GNATS BTSes.
  91. .TP
  92. .B \-\-configure
  93. Rerun the \fBreportbug\fP first time configuration routine, and write
  94. a new \fB$HOME/.reportbugrc\fP file. This will erase any pre-existing
  95. settings in the file; however, a backup will be written as
  96. \fB$HOME/.reportbugrc~\fP.
  97. .TP
  98. .B \-\-check\-available
  99. Check for newer releases of the package at \\fP
  100. (default). In \fBadvanced\fP and \fBexpert\fP mode, check
  101. \\fP and
  102. \fB\fP too.
  103. .TP
  104. .B \-\-no\-check\-available
  105. Do not check for newer releases of the package at
  106. \\fP.
  107. .TP
  108. .B \-\-debconf
  109. Include debconf settings in your report.
  110. .TP
  111. .B \-\-no\-debconf
  112. Do not include debconf settings from your report.
  113. .TP
  114. .B \-d, \-\-debug
  115. Don't send a real bug report to Debian; send it to yourself instead.
  116. This is primarily used for testing by the maintainer.
  117. .TP
  118. .B \-\-test
  119. Operate in test mode (maintainer use only).
  120. .TP
  121. .B \-\-draftpath=DRAFTPATH
  122. Save the draft (for example, when exiting and saving the report
  123. without reporting it) into \fIDRAFTPATH\fP directory.
  124. .TP
  125. .B \-e EDITOR, \-\-editor=EDITOR
  126. Specify the editor to use, overriding any \fBEDITOR\fP or \fBVISUAL\fP
  127. environment variable setting.
  128. .TP
  129. .B \-\-email=ADDRESS
  130. Set the email address your report should appear to be sent from
  131. (i.e. the address that appears in the \fBFrom\fP header). This should
  132. be the actual Internet email address on its own (i.e. without a real
  133. name or comment part, like \\fP). This setting will
  134. override the \fBEMAIL\fP and \fBDEBEMAIL\fP environment variables, but
  135. not \fBREPORTBUGEMAIL\fP.
  136. .TP
  137. .B \-\-envelope\-from
  138. Specify the Envelope From mail header (also known as Return-path); by default
  139. it's the From address but it can be selected a different one in case the MTA
  140. doesn't canonicalize local users to public addresses.
  141. .TP
  142. .B \-\-mbox\-reader\-cmd=MBOX_READER_CMD
  143. Specify a command to open the bug reports mbox file. You can use
  144. \fB%s\fP to substitute the mbox file to be used, and \fB%%\fP to insert
  145. a literal percent sign. If no \fB%s\fP is specified, the mbox file name
  146. is supplied at the end of the argument list.
  147. .TP
  148. .B \-\-exit\-prompt
  149. Display a prompt before exiting; this is useful if \fBreportbug\fP is
  150. run in a transient terminal (i.e. from its Debian menu entry).
  151. .TP
  152. .B \-f FILENAME, \-\-filename=FILENAME
  153. Report a bug in the package containing \fIFILENAME\fP so you don't
  154. have to figure out what package the file belongs to. The path will be
  155. searched for an exact path for \fIFILENAME\fP before attempting to
  156. broaden the search to all files. If \fBdlocate\fP is installed,
  157. \fIFILENAME\fP is actually a regular expression.
  158. .TP
  159. .B \-\-from-buildd=BUILDD_FORMAT
  160. This options is a shortcut for buildd admins to report bugs from
  161. buildd log; the option expects a value in the format of
  162. \fI$source_$version\fP where \fI$source\fP is the source package the
  163. bug will be reported against and \fI$version\fP is its version.
  164. .TP
  165. .B \-\-path
  166. If the \fB\-f/\-\-filename\fP option is also specified, only search
  167. the path for the specified \fIFILENAME\fP. Specifying an absolute
  168. path with the \fB\-f/\-\-filename\fP option (i.e. one beginning with a
  169. \fB/\fP) overrides this behavior.
  170. .TP
  171. .B \-g, \-\-gnupg, \-\-gpg
  172. Attach a digital signature to the bug report using \fBGnuPG\fP (the
  173. GNU Privacy Guard). (This argument will be ignored if you are using
  174. an MUA to edit and send your report.)
  175. .TP
  176. .B \-G, \-\-gnus
  177. Use the Gnus mail and news reader to send your report, rather than
  178. using the editor.
  179. .TP
  180. .B \-H HEADER, \-\-header=HEADER
  181. Add a custom RFC2822 header to your email; for example, to send a
  182. carbon copy of the report to \\fP you
  183. could use
  184. .I \-H 'X\-Debbugs\-CC: debian\-68k@lists.linux\'
  185. .TP
  186. .B \-i FILE, \-\-include=FILE
  187. Include the specified \fIFILE\fP as part of the body of the message to
  188. be edited. Can be used multiple times to add multiple files;
  189. text-only please! From a suggestion by Michael Alan Dorman in the
  190. \fBbug\fP mailing list. (See also the \fB\-a/\-\-attach\fP option.)
  191. .TP
  192. .B \-I, \-\-no\-check\-installed
  193. Do not check whether the package is installed before filing a report.
  194. This is generally only useful when filing a report on a package you
  195. know is not installed on your system.
  196. .TP
  197. .B \-\-check\-installed
  198. Check if the specified package is installed when filing reports.
  199. (This is the default behavior of \fBreportbug\fP.)
  200. .TP
  201. .B \-j JUSTIFICATION, \-\-justification=JUSTIFICATION
  202. Bugs in Debian that have \fBserious\fP, \fBgrave\fP, or \fBcritical\fP
  203. severities must meet certain criteria to be classified as such. This
  204. option allows you to specify the justification for a release-critical
  205. bug, instead of being prompted for it.
  206. .TP
  207. .B \-k, \-\-kudos
  208. Send appreciative email to the recorded maintainer address, rather
  209. than filing a bug report. (You can also send kudos to
  210. \\fP, for packages in the Debian
  211. archive; however, this option uses the Maintainer address from the
  212. control file, so it works with other package sources too.)
  213. .TP
  214. .B \-K KEYID, \-\-keyid=KEYID
  215. Private key to use for PGP/GnuPG signatures. If not specified, the
  216. first key in the secret keyring that matches your email address will
  217. be used.
  218. .TP
  219. .B \-\-latest-first
  220. Display the bug reports list sorted and with the latest reports at the top.
  221. .TP
  222. .B \-\-license
  223. Show \fBreportbug\fP's copyright and license information on standard
  224. output.
  225. .TP
  226. .B \-\-list\-cc=ADDRESS
  227. Send a carbon copy of the report to the specified list after a report
  228. number is assigned; this is the equivalent to the option
  229. \fI\-H 'X\-Debbugs\-CC: ADDRESS'\fP. This option will only work as
  230. intended with \fBdebbugs\fP systems.
  231. .TP
  232. .B \-m, \-\-maintonly
  233. Only send the bug to the package maintainer; the bug tracking system
  234. will not send a copy to the bug report distribution lists.
  235. .TP
  236. .B \-\-max-attachment-size=MAX_ATTACHMENT_SIZE
  237. Specify the maximum size any attachment file can have (this also include the file for \-\-body-file option). If an attachment file is too big, there could be problems in delivering the email (and also to compose it), so we set a limit to attachment size. By default this is 10 megabytes.
  238. .TP
  239. .B \-\-mirror=MIRRORS
  240. Add a BTS mirror.
  241. .TP
  242. .B \-\-mode=MODE
  243. Set the operating mode for \fBreportbug\fP. \fBreportbug\fP
  244. currently has four operating modes: \fBnovice\fP (the
  245. default), \fBstandard\fP, \fBadvanced\fP, and \fBexpert\fP.
  246. \fBnovice\fP mode is designed to minimize prompting about things that
  247. "ordinary users" would be unlikely to know or care about, shifting the
  248. triage burden onto the maintainer. Checking for new versions is only
  249. done for the stable distribution in this mode. It is currently the
  250. default mode.
  251. \fBstandard\fP mode includes a relatively large number of prompts and
  252. tries to encourage users to not file frivolous or duplicate bug
  253. reports.
  254. \fBadvanced\fP mode is like \fBstandard\fP mode, but may include
  255. shortcuts suitable for more advanced users of Debian, without being as
  256. close to the metal (and potential flamage) as \fBexpert\fP mode.
  257. (Currently, the only differences from \fBstandard\fP mode are that it
  258. assumes familiarity with the "incoming" queue; it allows the reporting
  259. of bugs on "dependency" packages; and it does not prompt where to
  260. insert the report text in the editor.)
  261. \fBexpert\fP mode is designed to minimize prompts that are designed to
  262. discourage frivolous or unnecessary bug reports, "severity inflation,"
  263. and the like. In \fBexpert\fP mode, \fBreportbug\fP assumes the user
  264. is thoroughly familiar with Debian policies. In practice, this means
  265. that reporters are no longer required to justify setting a high
  266. severity on a bug report, and certain automated cleanups of the
  267. message are bypassed. Individuals who do not regularly contribute to
  268. the Debian project are \fIhighly\fP discouraged from using expert
  269. mode, as it can lead to flamage from maintainers when used improperly.
  270. .TP
  271. .B \-M, \-\-mutt
  272. Instead of spawning an editor to revise the bug report, use the
  273. \fBmutt\fP mail reader to edit and send it.
  274. .TP
  275. .B \-\-mta=MTA
  276. Specify an alternate \fIMTA\fP, instead of \fB/usr/sbin/sendmail\fP
  277. (the default). Any \fBsmtphost\fP setting will override this one.
  278. .TP
  279. .B \-\-mua=MUA
  280. Instead of spawning an editor to revise the bug report, use the
  281. specified \fIMUA\fP (mail user agent) to edit and send
  282. it. \fB--mutt\fP and \fB--nmh\fP options are processed.
  283. .TP
  284. .B \-n, \-\-mh, \-\-nmh
  285. Instead of spawning an editor to revise the bug report, use the
  286. \fBcomp\fP command (part of the \fBnmh\fP and \fBmh\fP mail systems)
  287. to edit and send it.
  288. .TP
  289. .B \-N BUGNUMBER, \-\-bugnumber BUGNUMBER
  290. Run \fBreportbug\fP against the specified bug report, useful when
  291. following-up a bug and its number is already known.
  292. .TP
  293. .B \-\-no\-bug\-script
  294. Do not execute the bug script (if present); this option can be useful
  295. together with \-\-template to suppress every interactive actions,
  296. since some bug scripts can ask questions.
  297. .TP
  298. .B \-\-no\-cc\-menu
  299. Don't display the menu to enter additional addresses (CC).
  300. .TP
  301. .B \-\-no\-tags\-menu
  302. Don't display the menu to enter additional tags.
  303. .TP
  304. .B \-o FILE, \-\-output=FILE
  305. Instead of sending an email, redirect it to the specified filename.
  306. The output file is a full dump of the email message, so it contains
  307. both headers and mail body. If you want to use it as a template to
  308. create a new bug report, then you have to remove all the headers (mind
  309. the \fBSubject\fP one, though) and start the report at the
  310. \fBPackage\fP pseudo-header.
  311. .TP
  312. .B \-O, \-\-offline
  313. Disable all external queries. Currently has the same effect as
  314. \fB\-\-no\-check\-available \-\-no\-query\-bts\fP.
  315. .TP
  316. .B \-p, \-\-print
  317. Instead of sending an email, print the bug report to standard output,
  318. so you can redirect it to a file or pipe it to another program.
  319. This option only outputs a template for a bug report (but, differently
  320. from \fB\-\-template\fP it's more interactive); you will need to fill
  321. in the long description.
  322. .TP
  323. .B \-\-paranoid
  324. Show the contents of the message before it is sent, including all
  325. headers. Automatically disabled if in template mode.
  326. .TP
  327. .B \-\-no\-paranoid
  328. Don't show the full contents of the message before it is sent
  329. (default).
  330. .TP
  331. .B \-\-pgp
  332. Attach a digital signature to the bug report using \fBPGP\fP (Pretty
  333. Good Privacy). Please note, however, that the Debian project is
  334. phasing out the use of \fBPGP\fP in favor of \fBGnuPG\fP. (This
  335. argument will be ignored if using an MUA to edit and send your
  336. report.)
  337. .TP
  338. .B \-\-proxy=PROXY, \-\-http_proxy=PROXY
  339. Specify the WWW proxy server to use to handle the query of the bug
  340. tracking system. You should only need this parameter if you are
  341. behind a firewall. The \fIPROXY\fP argument should be formatted as a
  342. valid HTTP URL, including (if necessary) a port number; for example,
  343. \fBhttp://\fP.
  344. .TP
  345. .B \-P PSEUDO-HEADER, \-\-pseudo\-header=PSEUDO-HEADER
  346. Add a custom pseudo-header to your report; for example, to add the
  347. \fImytag\fP usertag for the user \\fP to the
  348. bug, you could use \fI\-P 'User:' \-P 'Usertags:
  349. mytag'\fP.
  350. .TP
  351. .B \-q, \-\-quiet
  352. Suppress diagnostic messages to standard error.
  353. .TP
  354. .B \-Q, \-\-query\-only
  355. Do not submit a bug report; just query the BTS. Option ignored if you
  356. specify \fB\-\-no\-bts\-query\fP.
  357. .TP
  358. .B \-\-query\-source
  359. Query on all binary packages built by the same source, not just the
  360. binary package specified.
  361. .TP
  362. .B \-\-no\-query\-source
  363. Only query on the binary package specified on the command line.
  364. .TP
  365. .B \-\-realname=NAME
  366. Set the real name (human-readable name) to use for your report.
  367. .TP
  368. .B \-\-report\-quiet
  369. Register the bug in the bug tracking system, but don't send a report
  370. to the package maintainer or anyone else. Don't do this unless you're
  371. the maintainer of the package in question, or you really know what you
  372. are doing.
  373. .TP
  374. .B \-\-reply-to=ADDRESS, \-\-replyto=ADDRESS
  375. Set the \fBReply-To\fP address header in your report.
  376. .TP
  377. .B \-s SUBJECT, \-\-subject=SUBJECT
  378. Set the subject of the bug report (i.e. a brief explanation of the
  379. problem, less than 60 characters). If you do not specify this switch,
  380. you will be prompted for a subject.
  381. .TP
  382. .B \-\-security\-team
  383. If the 'security' tag is set, this option will explicitly specify to send the
  384. report only to the Debian Security Team, as this is an undisclosed
  385. vulnerability.
  386. .TP
  387. .B \-\-no\-security\-team
  388. If the 'security' tag is set, this option will explicitly specify to not send
  389. the report only to the Debian Security Team, as this is not an undisclosed
  390. vulnerability.
  391. .TP
  392. .B \-S SEVERITY, \-\-severity=SEVERITY
  393. Specify a severity level, from \fBcritical\fP, \fBgrave\fP,
  394. \fBserious\fP, \fBimportant\fP, \fBnormal\fP, \fBminor\fP, and
  395. \fBwishlist\fP.
  396. .TP
  397. .B \-\-smtphost=HOST[:PORT]
  398. Use the mail transport agent (MTA) at \fBHOST\fP to send your report,
  399. instead of your local \fB/usr/sbin/sendmail\fP program. This should
  400. generally be your ISP's outgoing mail server; you can also
  401. use 'localhost' if you have a working mail server running on your
  402. machine. If the \fBPORT\fP is omitted, the standard port for SMTP,
  403. port 25, is used.
  404. .TP
  405. .B \-\-timeout=SECONDS
  406. Specify the network timeout, the number of seconds to wait for a
  407. resource to respond. If nothing is specified, a default timeout of 1
  408. minute is selected.
  409. In case of a network error, there are chances it's due to a too low
  410. timeout: try passing the \-\-timeout option with a higher value than
  411. default.
  412. .TP
  413. .B \-\-tls
  414. If using SMTP, use Transport Layer Security (TLS) encryption to secure
  415. the connection to the mail server. Some SMTP servers may require this
  416. option.
  417. .TP
  418. .B \-\-smtpuser=USERNAME
  419. If using SMTP, use the specified \fIUSERNAME\fP for authentication.
  420. .TP
  421. .B \-\-smtppasswd=PASSWORD
  422. If using SMTP, use the specified \fIPASSWORD\fP for authentication.
  423. If the password isn't specified on the command line or in the
  424. configuration file, a prompt will be displayed asking for it.
  425. Use of this option is insecure on multiuser systems. Instead, you
  426. should set this option in \fB$HOME/.reportbugrc\fP and ensure it is
  427. only readable by your user (e.g. with \fBchmod 600
  428. $HOME/.reportbugrc\fP).
  429. .TP
  430. .B \-\-src, \-\-source
  431. Specify to report the bug against the source package, and not the
  432. binary package (default behaviour). In order for this option to work,
  433. you have to populate the relevant 'deb-src' lines in
  434. /etc/apt/sources.list so that apt cache will know about source packages
  435. too.
  436. .TP
  437. .B \-t TYPE, \-\-type=TYPE
  438. Specify the type of report to be submitted; currently accepts either
  439. \fBgnats\fP or \fBdebbugs\fP.
  440. .TP
  441. .B \-T TAG, \-\-tag=TAG
  442. Specify a tag to be filed on this report, for example
  443. \fB\-\-tag=patch\fP. Multiple tags can be specified using multiple
  444. \fB\-T/\-\-tag\fP arguments.
  445. Alternatively, you can specify the 'tag' \fBnone\fP to bypass the tags
  446. prompt without specifying any tags; this will also ignore any tags
  447. specified on the command line.
  448. .TP
  449. .B \-\-template
  450. Output a template report to standard output. Differently from
  451. \fP\-p/\-\-print\fP, it tries to be not interactive, and presents a
  452. template without user's input.
  453. .TP
  454. .B \-u INTERFACE, \-\-interface=INTERFACE, \-\-ui=INTERFACE
  455. Specify the user interface to use. Valid options are \fBtext\fP,
  456. \fBurwid\fP, and \fBgtk2\fP; default is taken from the \fBreportbug\fP
  457. configuration files.
  458. .TP
  459. .B \-v, \-\-verify
  460. Verify the integrity of the package (if installed) using \fBdebsums\fP
  461. before reporting.
  462. .TP
  463. .B \-\-no\-verify
  464. Do not verify the integrity of the package with \fBdebsums\fP.
  465. .TP
  466. .B \-V VERSION, \-\-package\-version=VERSION
  467. Specify the version of the package the problem was found in. This is
  468. probably most useful if you are reporting a bug in a package that is
  469. not installable or installed on a different system.
  470. .TP
  471. .B \-x, \-\-no\-cc
  472. Don't send a blind carbon copy (BCC) of the bug report to the
  473. submitter (i.e. yourself).
  474. .TP
  475. .B \-z, \-\-no\-compress
  476. Don't compress configuration files by removing comments and blank
  477. lines.
  479. .TP
  480. .B reportbug lynx-ssl
  481. Report a bug in the lynx-ssl package.
  482. .TP
  483. .B reportbug \-\-path \-\-filename=ls
  484. Report a bug in the installed package that includes a program in your
  485. path called \fBls\fP.
  487. From version 0.22 on, \fBreportbug\fP has supported a simple run
  488. control file syntax. Commands are read from \fB/etc/reportbug.conf\fP
  489. and \fB$HOME/.reportbugrc\fP with commands in the latter overriding
  490. those in the former.
  491. Commands are not case sensitive, and currently take 0 or 1 argument;
  492. arguments containing whitespace must be enclosed in quotes.
  493. Any line starting with \fB#\fP is taken to be a comment and will be
  494. ignored.
  495. Generally, options corresponding to the long options for
  496. \fBreportbug\fP are supported, without leading \fB\-\-\fP sequences.
  497. See \fBreportbug.conf(5)\fP for all acceptable options and detailed
  498. information.
  500. .TP
  501. .B VISUAL
  502. Editor to use for editing your bug report.
  503. .TP
  504. .B EDITOR
  505. Editor to use for editing the bug report (overridden by \fBVISUAL\fP).
  506. .TP
  508. Email address to use as your from address (in this order). If no
  509. environment variable exists, the default is taken from your user name
  510. and \fB/etc/mailname\fP.
  511. .TP
  513. Real name to use; default is taken from \fB/etc/passwd\fP.
  514. .TP
  515. .B REPLYTO
  516. Address for \fBReply-To\fP header in outgoing mail.
  517. .TP
  518. .B MAILCC
  519. Use the specified CC address on your email. Note you can also use the
  520. \fB-H\fP option for this (and for Bcc's too).
  521. .TP
  522. .B MAILBCC
  523. Use the specified BCC address, instead of your email address. (CC and
  524. BCC based on suggestions from Herbert Thielen in the \fBbug\fP
  525. wishlist).
  526. .TP
  527. .B http_proxy
  528. Provides the address of a proxy server to handle the BTS query. This
  529. should be a valid \fBhttp\fP URL for a proxy server, including any
  530. required port number (simply specifying a hostname, or omitting a port
  531. other than 80, WILL NOT WORK).
  532. .SH NOTES
  533. .B reportbug
  534. should probably be compatible with other bug tracking systems, like
  535. \fBbugzilla\fP (used by the GNOME and Mozilla projects) and
  536. \fBjitterbug\fP (used by Samba, AbiSource and FreeCiv) but it isn't.
  537. .SH "SEE ALSO"
  538. reportbug.conf(5),
  539. .I
  540. for available tags, querybts(1)
  541. .SH AUTHOR
  542. Chris Lawrence <>,
  543. Sandro Tosi <>.
  544. \" LocalWords: reportbug debbugs pathname Debian bts fBdebbugs fP filename fB
  545. \" LocalWords: Debian's BODYFILE config reportbugrc pre DEBEMAIL gnupg gpg
  546. \" LocalWords: REPORTBUGEMAIL GnuPG MUA debian Dorman severities KEYID keyid
  547. \" LocalWords: PGP maintonly mta MTA smtphost mua nmh mh pgp http realname
  548. \" LocalWords: replyto wishlist ISP's localhost SMTP tls smtpuser USERNAME
  549. \" LocalWords: smtppasswd multiuser chmod debsums uninstallable BCC ssl Bcc's
  550. \" LocalWords: whitespace DEBFULLNAME DEBNAME MAILCC MAILBCC Thielen hostname
  551. \" LocalWords: getopt bugzilla Mozilla AbiSource FreeCiv querybts