- - ログのコピーは World Wide Web 上の???で参照できます。 - -
-
- リクエストをコントロールメールサーバに送ってバグ報告をプレーンテキスト形式で取り寄せることもできます。
- 使い方は、e-mailの本文にhelpとだけ書いて(Subjectは無視されます)requestに送るか、
- World Wide Web 上のbug-log-mailserver.txtを読んで下さい。
-
-
-
- Debian bug tracking system - copyright 1994-1997 Ian Jackson, copyright 1997 nCipher Corporation Ltd, - copyright 1995 Steven Brenner. - Available - under the GPL. - -
- - diff --git a/support/bugs/Developer.php b/support/bugs/Developer.php deleted file mode 100644 index 803e5ab..0000000 --- a/support/bugs/Developer.php +++ /dev/null @@ -1,217 +0,0 @@ - - -submit@bugs.kde.orgに送信されます。
- これには番号が割り当てられ、ユーザに受け取ったことを通知してkde-bugs-distに転送されます。
- もし送信した人がPackage行にメンテナのいるパッケージを書いていた場合はそのメンテナにも転送されます。
-
-
-
- Subject 行には Bug#nnn: というのが付け加えられ、Reply-To にはそのバグ報告を送信した人と nnn@bugs.kde.org が追加されます。
-
-
- -
kde-bugs-dist, and takes
- responsibility for it should hit Reply in their favourite mailreader,
- and then edit the To field to say
- nnn-done@bugs.kde.org instead of
- nnn@bugs
- (nnn-close is provided as an alias for
- nnn-done).
-
-
- The address of the original submitter of the bug report will be
- included in the default To field, because the bug system
- included it in the Reply-To.
-
-
- `Done' messages are not automatically forwarded to the mailing list,
- so it may sometimes be worthwhile including the
- kde-devel@kde.org mailing list if the other developers are
- likely to be interested.
-
- - The person closing the bug and the person who submitted it will each - get a notification about the change in status of the report. - -
@bugs and to the original
- submitter of the bug report. The bug tracking system will file the
- reply with the rest of the logs for that bug report and forward it to
- kde-bugs-dist. The bug will not be marked as done.
-
-
- If you wish to send a followup message which is not appropriate for
- kde-bugs-dist you can do so by sending it to
- nnn-quiet@bugs or
- nnn-maintonly@bugs, which only file it (not
- forwarding it anywhere) and send it on only to the maintainer of the
- package in question, respectively.
-
-
- Do not use the `reply to all recipients' or `followup'
- feature of your mailer unless you intend to edit down the recipients
- substantially. In particular, don't send a followup message both to
- nnn@bugs.kde.org and to
- submit@bugs.kde.org, because the bug system will then
- get two copies of it and each one will be forwarded to
- kde-bugs-dist separately.
-
- -
normalに設定されますが、
- バグ報告を送信する時に疑似ヘッダにSeverity行を書く(バグ報告の手順を参照)か、
- リクエストサーバに対してseverityコマンドを発行することで上書きすることができます。
-
- - - 利用できる重大レベルは次の通りです。 - -
critical(致命的)
- grave(重大)
- normal(通常)
- wishlist(要望)
-
-
- Make sure that the To field of your message to the author
- to has only the author(s) address(es) in it; put both the person who
- reported the bug and
- nnn-forwarded@bugs.kde.org in the
- CC field.
-
-
- Ask the author to preserve the CC to
- nnn-forwarded@bugs when they reply, so that
- the bug tracking system will file their reply with the original
- report.
-
-
- When the bug tracking system gets a message at
- nnn-forwarded it will mark the relevant bug as
- having been forwarded to the address(es) in the To field
- of the message it gets.
-
-
- You can also manipulate the `forwarded to' information by sending
- messages to control@bugs.kde.org.
-
-
kde-bugs-distkde-bugs-dist, sorted by age of report.
- Every Tuesday a list of bug reports that have gone unanswered too long
- is posted, sorted by package maintainer.
- - - - -
control@bugs.kde.org.
-
-
- The format of these messages is
- described in another document available on the World Wide Web or in
- the file bug-maint-mailcontrol.txt. A plain text version
- can also be obtained by mailing the word help to the
- server at the address above.
-
-
submit or bugs whose
- Subject starts Bug#nnn will be treated as
- having been sent to nnn@bugs. This is both
- for backwards compatibility with mail forwarded from the old
- addresses, and to catch followup mail sent to submit by
- mistake (for example, by using reply to all recipients).
-
-
-
- A similar scheme operates for maintonly,
- done, quiet and forwarded,
- which treat mail arriving with a Subject tag as having been sent to
- the corresponding nnn-whatever@bugs address.
-
-
-
- Messages arriving at plain forwarded and
- done - ie, with no bug report number in the address - and
- without a bug number in the Subject will be filed under `junk' and
- kept for a few weeks, but otherwise ignored.
-
-
Package: secondary header field may
- become mandatory - at the moment omitting it just produces a warning
- message.
-
-
-
- - Debian bug tracking system - copyright 1994-1997 Ian Jackson, copyright 1997 nCipher Corporation Ltd, - copyright 1995 Steven Brenner. - Available - under the GPL. - -
- - diff --git a/support/bugs/Reporting.php b/support/bugs/Reporting.php deleted file mode 100644 index 1a58f1b..0000000 --- a/support/bugs/Reporting.php +++ /dev/null @@ -1,162 +0,0 @@ - - -submit@bugs.kde.orgに
- 以下の解説に従ってメールを出して下さい。
-
-
- 関連のない複数のバグ、特に異なるパッケージのバグをまとめて1つのメッセージで報告するのはやめて下さい。
- また、バグ報告をsubmit@bugs以外のメーリングリストやその他の受信者宛に送らないで下さい(これをやる時の正しい方法は以下を見て下さい)。
-
- - 現在未解決のバグの一覧はWorld Wide Web上か別の場所で見ることができます。 - 詳しくは他のドキュメントを参照して下さい。 -
-
- バグ報告のメッセージの先頭には、Package: と Version: の疑似ヘッダを入れなければなりません。
- それぞれそのバグが発生したパッケージの名前とバージョンを記述します。
- (疑似ヘッダはメッセージの最初の最初になければなりません。
- 現在のところ、バグ追跡システムはMIMEやPGPを使ったメールには対応していません。)
- また、こちらの手順にも従って下さい。
-
-
- バグを報告する際にPackage行に記述できるパッケージについては
- バグ追跡システムのWWW 上のページをご覧下さい。
-
-
- To: submit@bugs.kde.org - From: diligent@testing.linux.org - Subject: Hello says `goodbye' - - Package: hello - Version: 1.3-2 - - When I invoke `hello' without arguments from an ordinary shell - prompt it prints `goodbye', rather than the expected `hello, world'. - Here is a transcript: - - $ hello - goodbye - $ /usr/bin/hello - goodbye - $ - - I suggest that the output string, in hello.c, be corrected. - - I am using Debian 1.1, kernel version 1.3.99.15z - and libc 5.2.18.3.2.1.3-beta. -- -
-
- もちろん、通常のe-mailと同様、メールのヘッダのSubjectは明確で内容が分かりやすいように書いて下さい。
- Subjectの記述はバグ追跡システムが付ける最初のタイトルに使われるので、できるだけそのバグを説明するようなものにして下さい！
-
-
kde-bugs-distとパッケージのメンテナ以外に送らなければならないことがあります。
-
-
- その場合、バグ報告をCcすることもできますが、そうするとそれを受け取った人のメールはReply-ToとSubjectの行にバグ報告の番号が含まれません。
- もし受け取った人がそのメールに返信した場合、ヘッダにはsubmit@bugs.kde.orgが含まれるでしょうから、新たなバグ報告となってしまいます。
- これは、同じバグ報告が複数登録されてしまうことにつながります。
-
-
- 正しい方法は、X-KDE-CCを使うことです。
- 次のような行をメールのヘッダ(Packageのような疑似ヘッダではなく)に加えて下さい。
-
- X-KDE-CC: other-list@cosmic.edu -- こうすると、バグ追跡システムは
kde-bugs-distに加えてX-KDE-CCに書かれているアドレスにもバグ報告を送ります。
-
-
- この機能は、後で述べるquietと組み合わせて使うこともできます。
-
-
-
- 重大レベルを付けるには、疑似ヘッダにPackageとVersionに加えてSeverity: severity行を書きます。
- どのような重大レベルがあるかは
- 開発者向けのドキュメントを参照して下さい。
-
-
maintonly@bugs または quiet@bugs に送って下さい。
- maintonly はパッケージのメンテナにだけバグ報告を送ります
- (Package行が疑似ヘッダに正しく記述されていて、メンテナがいる場合)。
- quiet はそのバグ報告をどこにも送らず、単にファイルするだけです
- (例えば、似たようなバグを大量に送る際にサマリだけを送りたい場合)。
-
-
- このようにした場合、バグ追跡システムはバグ報告を通知するメールのReply-Toを設定して、そのメールに返信すると最初に送られたのと同じ扱いになるようにします。
-
-
Packageが設定されていないバグ報告maintonlyであってもそのバグ報告をkde-bugs-distに転送します。
-
-
- maintonly@bugs または nnn-maintonly@bugs に送る場合、
- バグ報告の先頭にPackageを正しく記述してパッケージを指定してあることを確認して下さい。
- 既にしてしまった場合は、control@bugsサービスを使って適切なパッケージを(再)指定して下さい。
-
-
- Debian bug tracking system - copyright 1994-1997 Ian Jackson, copyright 1997 nCipher Corporation Ltd, - copyright 1995 Steven Brenner. - Available - under the GPL. - -
- - diff --git a/support/bugs/index2.php b/support/bugs/index2.php deleted file mode 100644 index f9f39fb..0000000 --- a/support/bugs/index2.php +++ /dev/null @@ -1,99 +0,0 @@ - - -This information is old. / この情報は古くなっています - -- Debian bug tracking system - copyright 1994-1997 Ian Jackson, copyright 1997 nCipher Corporation Ltd, - copyright 1995 Steven Brenner. - Available - under the GPL. - -
- diff --git a/support/bugs/server-control.php b/support/bugs/server-control.php deleted file mode 100644 index 93c1daa..0000000 --- a/support/bugs/server-control.php +++ /dev/null @@ -1,222 +0,0 @@ - - -request@bugs.kde.org
- which allows the retrieval of bug data and documentation by email,
- there is another server on control@bugs.kde.org which
- also allows bug reports to be manipulated in various ways.
- - - The control server works just like the request server, except that it - has some additional commands; in fact, it's the same program. The two - addresses are only separated to avoid users making mistakes and - causing problems while merely trying to request information. -
-
- Please see the
- introduction to
- the request server
- available on the World Wide Web, in the file
- bug-maint-mailcontrol.txt, or by sending
- help to either mailserver, for details of the basics of
- operating the mailservers and the common commands available when
- mailing either address.
-
-
- The reference card for the
- mailservers is available via the WWW, in
- bug-mailserver-refcard.txt or by email using the
- refcard command).
-
-
close bugnumber
-
-
- A notification is sent to the user who reported the bug, but (in
- contrast to mailing bugnumber-done@bugs) the
- text of the mail which caused the bug to be closed is not
- included in that notification. The maintainer who closes a report
- should ensure, probably by sending a separate message, that the user
- who reported the bug knows why it is being closed.
-
-
reassign bugnumber package
- reopen bugnumber
- [ originator-address | = | ! ]
-
-
- By default, or if you specify =, the original submitter is
- still as the originator of the report, so that they will get the ack
- when it is closed again.
-
-
- If you supply an originator-address the originator will be
- set to the address you supply. If you wish to become the new
- originator of the reopened report you can use the !
- shorthand or specify your own email address.
-
- - It is usually a good idea to tell the person who is about to be - recorded as the originator that you're reopening the report, so that - they will know to expect the ack which they'll get when it is closed - again. -
- - If the bug is not closed then reopen won't do anything, not even - change the originator. There is no way to change the originator of an - open bug report (this is deliberate, so that you can't have a bug be - closed and then deleted 200 days later without someone being told about - it). - -
forwarded bugnumber address
- notforwarded bugnumber
- retitle bugnumber new-title
- Subject mail header from the original report.
- - - Unlike most of the other bug-manipulation commands when used on one of - a set of merged reports this will change the title of only the - individual bug requested, and not all those with which it is merged. - -
severity bugnumber severity
-
-
- Severities are critical, grave,
- normal and wishlist.
-
- For their meanings please
- consult the general developers' documentation for the bug system.
-
-
merge bugnumber bugnumber ...
-
-
- Before bugs can be merged they must be in exactly the same state:
- either all open or all closed, with the same forwarded-to upstream
- author address or all not marked as forwarded, and all assigned to the
- same package or package(s) (an exact string comparison is done on the
- package to which the bug is assigned). If they don't start out in the
- same state you should use reassign, reopen
- and so forth to make sure that they are before using
- merge.
-
-
- If any of the bugs listed in a merge command is already
- merged with another bug then all the reports merged with any of the
- ones listed will all be merged together. Merger is like equality: it
- is reflexive, transitive and symmetric.
-
- - Merging reports causes a note to appear on each report's logs; on the - WWW pages this is includes links to the other bugs. -
- - Merged reports are all expired simultaneously, and only when all of - the reports each separately meet the criteria for expiry. - -
unmerge bugnumber
- - - If many bug reports are merged and you wish to split them into two - separate groups of merged reports you must unmerge each report in one - of the new groups separately and then merge them into the required new - group. -
-
- You can only unmerge one report with each unmerge
- command; if you want to disconnect more than one bug simply include
- several unmerge commands in your message.
-
-
- Debian bug tracking system - copyright 1994-1997 Ian Jackson, copyright 1997 nCipher Corporation Ltd, - copyright 1995 Steven Brenner. - Available - under the GPL. - -
- - diff --git a/support/bugs/server-refcard.php b/support/bugs/server-refcard.php deleted file mode 100644 index 67b50d2..0000000 --- a/support/bugs/server-refcard.php +++ /dev/null @@ -1,110 +0,0 @@ - - -help を送信して取り寄せて下さい。
-
- request@bugs.kde.orgで使えるコマンドの概要send bugnumber
- send-detail bugnumber
- index [full]
- index-summary by-package
- index-summary by-number
- index-maint
- index-maint maintainer-substring
- index-packages
- index packages package-substring
- send-unmatched [this|0]
- send-unmatched last|-1
- send-unmatched old|-2
- getinfo filename (下記参照)
- help
- refcard
- quit|stop|thank...|--...
- #... (コメント)
- debug level
- getinfoで指定できる情報ファイルの一覧maintainers
- override.stable
- override.development
- override.contrib
- override.non-free
- override.experimental
- override.codeword
- pseudo-packages.description
- pseudo-packages.maintainers
- close bugnumber
- (you must separately tell originator why)
- reassign bugnumber package
- severity bugnumber severity
- reopen bugnumber
- [ originator-address | = | ! ]
- forwarded bugnumber address
- notforwarded bugnumber
- retitle bugnumber new-title
- merge bugnumber bugnumber ...
- unmerge bugnumber
- reopen で = を指定するか originator-address を指定しない場合は originator はオリジナルの送信者のままです。
- ! を指定した場合は reopen を発行したあなたに設定されます。
-
-
- 重大レベルには critical、 grave、normal
- そして wishlist があります。
-
-
-
- Debian bug tracking system - copyright 1994-1997 Ian Jackson, copyright 1997 nCipher Corporation Ltd, - copyright 1995 Steven Brenner. - Available - under the GPL. - -
- - diff --git a/support/bugs/server-request.php b/support/bugs/server-request.php deleted file mode 100644 index 01bd496..0000000 --- a/support/bugs/server-request.php +++ /dev/null @@ -1,204 +0,0 @@ - - -
-
- To use it you send a mail message to
- request@bugs.kde.org.
- The Subject of the message is ignored, except
- for generating the Subject of the reply.
-
- - The body you send should be a series of commands, one per line. - You'll receive a reply which looks like a transcript of your message - being interpreted, with a response to each command. No notifications - are sent to anyone for most commands; however, the messages are logged - and made available in the WWW pages. -
-
- Any text on a line starting with a hash sign # is
- ignored; the server will stop processing when it finds a line starting
- with quit, stop, thank or two
- hyphens (to avoid parsing a signature). It will also stop if it
- encounters too many unrecognised or badly-formatted commands. If no
- commands are successfully handled it will send the help text for the
- server.
-
-
send bugnumber
- send-detail bugnumber
- send-detail sends all of the `boring' messages in the
- transcript, such as the various auto-acks (you should usually use
- send as well, as the interesting messages are not sent by
- send-detail).
-
- index [full]
- index-summary by-package
- index-summary by-number
- index-maint
- index-maint maintainer
- index-packages
- index packages package
- send-unmatched [this|0]
- send-unmatched last|-1
- send-unmatched old|-2
- getinfo filename
- maintainers
- pseudo-packages.description
- pseudo-packages.maintainers
- refcards
- help
- quit
- stop
- thank...
- --...
- #, for
- example for the benefit of human readers of your message (reading it
- via the tracking system logs or due to a CC or
- BCC).
-
- #...
- # must be at the start of the
- line.
-
- debug level
- bug-mailserver-refcard.txt or by email using the
- refcard command (see above).
-
-
- If you wish to manipulate bug reports you should use the
- control@bugs.kde.org address, which understands a
- superset of the commands listed
- above. This is described in another document, available on the
- WWW, in the file bug-maint-mailcontrol.txt, or by
- sending help to control@bugs.
-
-
- In case you are reading this as a plain text file or via email: an
- HTML version is available via the bug system main contents page
- http://www.kde.org/Bugs/.
-
- -
- Debian bug tracking system - copyright 1994-1997 Ian Jackson, copyright 1997 nCipher Corporation Ltd, - copyright 1995 Steven Brenner. - Available - under the GPL. - -
- -