Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these lines ***
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, ’unstable’)
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages t-code depends on:
ii emacs-snapshot-nox [emacs-snapshot] 1:20111219-1
t-code recommends no packages.
t-code suggests no packages.
-- no debconf information
こういうひな形が表示されますのでこれを編集します。以下が編集後のレポートです。
Subject: t-code version 2.3.1 fails bushu-convert
Package: t-code
Version: 2:2.3.1-3
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* T-code pre bushu-convert doesn’t work
* pre bushu-convert error message is tcode-self-insert-command: Wrong type argument: characterp, nil
* T-code post bushu-convert doesn’t work(There is no error message).
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, ’unstable’)
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages t-code depends on:
ii emacs-snapshot-nox [emacs-snapshot] 1:20111219-1
t-code recommends no packages.
t-code suggests no packages.
-- no debconf information
ま、こんなとこでしょう。編集を終えると下記の確認をしてきます。
Report will be sent to ‘‘Debian Bug Tracking System’’ <submit@bugs.debian.org>’’--configure’’ option.
Submit this report on t-code (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|s|?]? Y
これでよいので Y を入力します。もう一度編集したければ e を入力します。
Connecting to reportbug.debian.org via SMTP...
Bug report submitted to: ‘‘Debian Bug Tracking System’’ <submit@bugs.debian.org>
Copies will be sent after processing to:
knishida@riken.jp
If you want to provide additional information, please wait to receive the bug tracking number via email;
you may then send any extra information to n@bugs.debian.org (e.g. 999999@bugs.debian.org), where n is the
bug number. Normally you will receive an acknowledgement via email including the bug report number within
an hour; if you haven’t received a confirmation, then the bug reporting process failed at some point
(reportbug or MTA failure, BTS maintenance, etc.).
これでバグレポートは終わりです。入力した自分のメールアドレスにバグレポートしたことを確認するメールが届いて
いることを確認してください。もしメールが届いていたらバグレポートの番号を確認して http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=653167 のように bug=の後にバグ ID を入力してウェブページでも内容を確認してみてくだ
12