Any other helpful information you provide is most welcome.
Be sure to mention if it compiles and runs well on your arch. Has it actually been released by upstream sources, or is it just marked in the source tree? Some projects mark a release in the tree long time before it is officially released. Avoid zero-day bump requests (wait at least 48 hours after the release announcement). Search Bugzilla before posting a bump request - is there already a bug open? Has the local Portage tree been synced lately is it already in Portage?. Report a version bump a newer upstream release is available since a while What was the last working version of the package, if any?. What makes the program crash, behave wrong, not start. How is the program run (on the console, in a terminal, as a daemon, in what runlevel etc.). Description of the problem, so that other can reproduce it:. sys-apps/package-2.3-r4 crashes with error: Cannot proceed. The exact version of the package in the title of the bug report e.g. sys-apps/package-2.3-r4įiles and information of interest ordered by priority: First write the exact version of the package in the title of the bug report e.g. Use the Add an attachment button below the description text box in order to attach files in bugzilla. To do so, create a new attachment and paste the contents of: You should always add information about your system configuration to the bug. Attach the logs to the bug ticket if the ticket is about problems during runtime or installation. Optional: Gentoo consultants provide also commercial support for bugs and ebuilds. If you want to add useful information, add them to a related sub bug or create a new bug. If your problem is not discussed on a bug, search for one related to your issue or create a new report. Open one bug ticket per topic - Usually this means not more than one package and one bug per ticket. 
But if your and the confirmer's systems differ in an obvious way and that would be helpful to know, add this information. It does not help solving the problem, if you and another person report it twice. Confirm the existence of a problem only once.Keep them in the support channels (forums, IRC or mailing lists). Stay on topic - A bug ticket is used for technical reports and chitchat should be avoided.Search for duplicates, before creating a new bug.You know that the recipient can read English, but it is not his native language. Hint: Imagine you have only one chance in your life to write this very important bug report. Write in precise and clean language and avoid colloquial speech. Also any text entered into a bug report will be usually e-mailed immediately to many people. Reread the text before submission, the text cannot be edited afterwards.
2.4 Request for a new package ebuild request.2.3 Report a version bump a newer upstream release is available since a while.2.1 Report a build-time bug (emerge failed).
0 kommentar(er)
