Differences between revisions 6 and 8 (spanning 2 versions)
Revision 6 as of 2019-10-20 14:06:35
Size: 2625
Editor: nodiscc
Comment: add categories, redundant
Revision 8 as of 2021-09-17 15:09:35
Size: 2727
Editor: ThiagoPezzo
Comment: add translation header and language code
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#language en
~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: English - [[pt_BR/BugReport|Português (Brasil)]]-~
----
Line 8: Line 11:
You should check to see if your bug report has already been filed before submitting it.  You should check to see if your bug report has already been filed before submitting it.
Line 17: Line 20:
   The main purpose of bug reports is to help you contribute to the community 
   by improving the next version of the program. Many of the people who report bugs 
   don't realise this-they think that the point is for you to help them individually. 
   Some will ask you to focus on that instead of on making the program better. 
   If you comply with their wishes, you will have been distracted from the job 
   The main purpose of bug reports is to help you contribute to the community
   by improving the next version of the program. Many of the people who report bugs
   don't realise this-they think that the point is for you to help them individually.
   Some will ask you to focus on that instead of on making the program better.
   If you comply with their wishes, you will have been distracted from the job
Line 25: Line 28:
The purpose of bug reports in Debian can be found in the [[http://www.debian.org/social_contract|Debian Social Contract]] :  The purpose of bug reports in Debian can be found in the [[http://www.debian.org/social_contract|Debian Social Contract]] :
Line 30: Line 33:
=== time limitations === === Time limitations ===
Line 38: Line 41:
  * Some maintainer will tag those bug as "unreproducible" .    * Some maintainer will tag those bug as "unreproducible" .
Line 40: Line 43:
  * Others will close those bugreports that seem unreproducible.    * Others will close those bugreports that seem unreproducible.
Line 43: Line 46:
Bug reports are used by the maintainers 
 * as a reminder 
 * for Team organisation 
Bug reports are used by the maintainers
 * as a reminder
 * for Team organisation
Line 49: Line 52:
before sending a bug report.
  * Try to reproduce it a second time.
Before sending a bug report:
  * Try to reproduce it.
Line 52: Line 55:
  * Try to join some one on debian-user mailing list or irc.
  * check for duplicates. 
  * Try to join some one on debian-user mailing list or IRC.
  * check for duplicates.
Line 55: Line 58:
If you want to send a bug report.
  * Read http://www.debian.org/Bugs/Reporting 
If you want to send a bug report:
  * Read http://www.debian.org/Bugs/Reporting

Translation(s): English - Português (Brasil)


Introduction

The purpose of a bug report is to improve the stable and testing Debian Distributions.

You send a bug report to help the maintainer improve the package, not to receive help from them.

You should check to see if your bug report has already been filed before submitting it.

If you want to know how to report a bug see : http://www.debian.org/Bugs/Reporting

The purpose of a bug report

As it is written in : http://www.gnu.org/prep/maintain/maintain.html#Replying-to-Mail

   The main purpose of bug reports is to help you contribute to the community
   by improving the next version of the program. Many of the people who report bugs
   don't realise this-they think that the point is for you to help them individually.
   Some will ask you to focus on that instead of on making the program better.
   If you comply with their wishes, you will have been distracted from the job
   of maintaining the program.

The purpose of bug reports in Debian can be found in the Debian Social Contract :

  • We will not hide problems
  • Our priorities are our users and free software

Time limitations

You must keep in mind that maintainers receive a lot of bug reports, and have limited time to spare on Debian. Their priority is to :

  1. package a new upstream release that fixes a lot of bugs
  2. fix a nicely reported bug with a reproducible and a well-identified cause

They don't have time to investigate dubious bug report.

  • Some maintainer will tag those bug as "unreproducible" .
    • For some packages it means that no one will look at them within the next five years.
  • Others will close those bugreports that seem unreproducible.

Some interesting examples

Bug reports are used by the maintainers

  • as a reminder
  • for Team organisation
  • to alert about the presence of a problem

If a bug occurs

Before sending a bug report:

  • Try to reproduce it.
  • Be sure your debian installation is clean.
  • Try to join some one on debian-user mailing list or IRC.
  • check for duplicates.

If you want to send a bug report:

If you need a service

Debian has a list of consultants. If you need paid support for Debian, you can ask them.


CategoryBugs | CategoryRedundant: merge with BTS and other pages