Differences between revisions 11 and 12
Revision 11 as of 2018-06-22 07:48:50
Size: 2969
Editor: JensKorte
Comment: the page left alpha stage ;)
Revision 12 as of 2018-06-23 02:02:18
Size: 2976
Editor: PaulWise
Comment: fix typo, add a couple of spaces
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
mailto:submit@bugs.debian.org?subject=packagename:%0describe%20problem%20here&body=Package:(insert%20package%20name%20here)%0AVersion:(insert%20the%20version%20of%20the%20package%20here)%0A%0APlease%20include%20in%20your%20report:%0A%20%0AThe%20exact%20and%20complete%20text%20of%20any%20error%20messages%20printed%20or%20logged.%20This%20is%20very%20important!%0A%20Exactly%20what%20you%20typed%20or%20did%20to%20demonstrate%20the%20problem.%0A%20A%20description%20of%20the%20incorrect%20behaviour%20exactly%20what%20behaviour%20you%20were%20expecting,%20and%20what%20you%20observed.%20A%20transcript%20of%20an%20example%20session%20is%20a%20good%20way%20of%20showing%20this.%0A%20A%20suggested%20fix,%20or%20even%20a%20patch,%20if%20you%20have%20one.%0A%20Details%20of%20the%20configuration%20of%20the%20program%20with%20the%20problem.%20Include%20the%20complete%20text%20of%20its%20configuration%20files.%20%0A%20%0A%20Include%20any%20detail%20that%20seems%20relevant%20-%20you%20are%20in%20very%20little%20danger%20of%20making%20your%20report%20too%20long%20by%20including%20too%20much%20information.%20If%20they%20are%20small%20please%20include%20in%20your%20report%20any%20files%20you%20were%20using%20to%20reproduce%20the%20problem%20(uuencoding%20them%20if%20they%20may%20contain%20odd%20characters%20etc.).%0A" mailto:submit@bugs.debian.org?subject=packagename:%20describe%20problem%20here&body=Package:%20(insert%20package%20name%20here)%0AVersion:%20(insert%20the%20version%20of%20the%20package%20here)%0A%0APlease%20include%20in%20your%20report:%0A%20%0AThe%20exact%20and%20complete%20text%20of%20any%20error%20messages%20printed%20or%20logged.%20This%20is%20very%20important!%0A%20Exactly%20what%20you%20typed%20or%20did%20to%20demonstrate%20the%20problem.%0A%20A%20description%20of%20the%20incorrect%20behaviour%20exactly%20what%20behaviour%20you%20were%20expecting,%20and%20what%20you%20observed.%20A%20transcript%20of%20an%20example%20session%20is%20a%20good%20way%20of%20showing%20this.%0A%20A%20suggested%20fix,%20or%20even%20a%20patch,%20if%20you%20have%20one.%0A%20Details%20of%20the%20configuration%20of%20the%20program%20with%20the%20problem.%20Include%20the%20complete%20text%20of%20its%20configuration%20files.%20%0A%20%0A%20Include%20any%20detail%20that%20seems%20relevant%20-%20you%20are%20in%20very%20little%20danger%20of%20making%20your%20report%20too%20long%20by%20including%20too%20much%20information.%20If%20they%20are%20small%20please%20include%20in%20your%20report%20any%20files%20you%20were%20using%20to%20reproduce%20the%20problem%20(uuencoding%20them%20if%20they%20may%20contain%20odd%20characters%20etc.).%0A"
  • /!\ The preferred/official way to report bugs to the Debian distribution is by using reportbug. The method proposed here is an alternative, to be used very rarely, and it originated in the Devuan context. please refrain from using this method with Debian.

It is possible to report bugs by mail and not by using reportbug by clicking on the mail link below to have a bug report draft. More details on how it's generated can be found here.

A more human-readable version is below. The layout differs.

mailto:submit@bugs.debian.org?subject=packagename:%20describe%20problem%20here&body=Package:%20(insert%20package%20name%20here)%0AVersion:%20(insert%20the%20version%20of%20the%20package%20here)%0A%0APlease%20include%20in%20your%20report:%0A%20%0AThe%20exact%20and%20complete%20text%20of%20any%20error%20messages%20printed%20or%20logged.%20This%20is%20very%20important!%0A%20Exactly%20what%20you%20typed%20or%20did%20to%20demonstrate%20the%20problem.%0A%20A%20description%20of%20the%20incorrect%20behaviour%20exactly%20what%20behaviour%20you%20were%20expecting,%20and%20what%20you%20observed.%20A%20transcript%20of%20an%20example%20session%20is%20a%20good%20way%20of%20showing%20this.%0A%20A%20suggested%20fix,%20or%20even%20a%20patch,%20if%20you%20have%20one.%0A%20Details%20of%20the%20configuration%20of%20the%20program%20with%20the%20problem.%20Include%20the%20complete%20text%20of%20its%20configuration%20files.%20%0A%20%0A%20Include%20any%20detail%20that%20seems%20relevant%20-%20you%20are%20in%20very%20little%20danger%20of%20making%20your%20report%20too%20long%20by%20including%20too%20much%20information.%20If%20they%20are%20small%20please%20include%20in%20your%20report%20any%20files%20you%20were%20using%20to%20reproduce%20the%20problem%20(uuencoding%20them%20if%20they%20may%20contain%20odd%20characters%20etc.).%0A"

  • submit@bugs.debian.org

  • subject=packagename: describe problem here
  • body=
  • Package:(insert package name here)

  • Version:(insert the version of the package here)

  • Please include in your report:
  • The exact and complete text of any error messages printed or logged. This is very important
  • Exactly what you typed or did to demonstrate the problem.
  • A description of the incorrect behaviour: exactly what behaviour you were expecting, and what you observed. A transcript of an exampl session is a good way of showing this.
  • A suggested fix, or even a patch, if you have one.
  • Details of the configuration of the program with the problem. Include the complete text of its configuration files.
  • Include any detail that seems relevant - you are in very little danger of making your report too long by including too much information. If they are small please include in your report any files you were using to reproduce the problem (uuencoding them if they may contain odd characters etc.).