/[gentoo]/xml/htdocs/doc/en/bugzilla-howto.xml
Gentoo

Diff of /xml/htdocs/doc/en/bugzilla-howto.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.15 Revision 1.16
1<?xml version="1.0" encoding="UTF-8"?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.15 2009/03/05 12:02:04 jkt Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.16 2009/03/05 12:13:20 jkt Exp $ -->
4 4
5<guide link="/doc/en/bugzilla-howto.xml"> 5<guide link="/doc/en/bugzilla-howto.xml">
6<title>Gentoo Bug Reporting Guide</title> 6<title>Gentoo Bug Reporting Guide</title>
7 7
8<author title="Author"> 8<author title="Author">
9 <mail link="chriswhite@gentoo.org">Chris White</mail> 9 <mail link="chriswhite@gentoo.org">Chris White</mail>
10</author> 10</author>
11<author title="Editor"> 11<author title="Editor">
12 <mail link="fox2mike@gentoo.org">Shyam Mani</mail> 12 <mail link="fox2mike@gentoo.org">Shyam Mani</mail>
13</author> 13</author>
14 14
15<abstract> 15<abstract>
16This document shows the proper method of reporting bugs using Bugzilla. 16This document shows the proper method of reporting bugs using Bugzilla.
17</abstract> 17</abstract>
18 18
19<!-- The content of this document is licensed under the CC-BY-SA license --> 19<!-- The content of this document is licensed under the CC-BY-SA license -->
20<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 20<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
21<license/> 21<license/>
22 22
23<version>1.13</version> 23<version>1.14</version>
24<date>2009-03-05</date> 24<date>2009-03-05</date>
25 25
26<chapter> 26<chapter>
27<title>Introduction</title> 27<title>Introduction</title>
28<section> 28<section>
29<title>Preface</title> 29<title>Preface</title>
30<body> 30<body>
31 31
32<p> 32<p>
33One of the factors that delay a bug being fixed is the way it is reported. By 33One of the factors that delay a bug being fixed is the way it is reported. By
34creating this guide, we hope to help improve the communication between 34creating this guide, we hope to help improve the communication between
35developers and users in bug resolution. Getting bugs fixed is an important, if 35developers and users in bug resolution. Getting bugs fixed is an important, if
36not crucial part of the quality assurance for any project and hopefully this 36not crucial part of the quality assurance for any project and hopefully this
37guide will help make that a success. 37guide will help make that a success.
38</p> 38</p>
480 480
481<comment>(emerge Error)</comment> 481<comment>(emerge Error)</comment>
482!!! ERROR: sys-apps/foobar2-1.0 failed. 482!!! ERROR: sys-apps/foobar2-1.0 failed.
483!!! Function src_compile, Line 19, Exitcode 2 483!!! Function src_compile, Line 19, Exitcode 2
484!!! Make failed! 484!!! Make failed!
485!!! If you need support, post the topmost build error, NOT this status message 485!!! If you need support, post the topmost build error, NOT this status message
486</pre> 486</pre>
487 487
488<p> 488<p>
489The compilation messages are what lead up to the error. Most often, it's good to 489The compilation messages are what lead up to the error. Most often, it's good to
490at least include 10 lines of compile information so that the developer knows 490at least include 10 lines of compile information so that the developer knows
491where the compilation was at when the error occurred. 491where the compilation was at when the error occurred.
492</p> 492</p>
493 493
494<p> 494<p>
495Please make sure you always include error messages in English, even when your
496system language is set to something else. You can temporarily switch to English
497locale by prepending <c>LC_ALL=C</c> to the emerge command like this:
498</p>
499
500<pre caption="Temporarily switching locale to English">
501# <i>LC_ALL=C emerge sys-apps/foobar2</i>
502</pre>
503
504<note>
505This is also about the only time you should use the <c>LC_ALL</c> environmental
506variable for specifying locale settings. If you are looking for a way to switch
507your system's language, then please consult our <uri
508link="guide-localization.xml">Localization Guide</uri> instead.
509</note>
510
511<p>
495Make errors are the actual error and the information the developer needs. When 512Make errors are the actual error and the information the developer needs. When
496you see "make: ***", this is often where the error has occurred. Normally, you 513you see "make: ***", this is often where the error has occurred. Normally, you
497can copy and paste 10 lines above it and the developer will be able to address 514can copy and paste 10 lines above it and the developer will be able to address
498the issue. However, this may not always work and we'll take a look at an 515the issue. However, this may not always work and we'll take a look at an
499alternative shortly. 516alternative shortly.
500</p> 517</p>
501 518
502<p> 519<p>
503The emerge error is what <c>emerge</c> throws out as an error. Sometimes, this 520The emerge error is what <c>emerge</c> throws out as an error. Sometimes, this
504might also contain some important information. Often people make the mistake of 521might also contain some important information. Often people make the mistake of
505posting the emerge error and that's all. This is useless by itself, but with 522posting the emerge error and that's all. This is useless by itself, but with
506make error and compile information, a developer can get what application and 523make error and compile information, a developer can get what application and
507what version of the package is failing. As a side note, make is commonly used as 524what version of the package is failing. As a side note, make is commonly used as
508the build process for programs (<b>but not always</b>). If you can't find a 525the build process for programs (<b>but not always</b>). If you can't find a
509"make: ***" error anywhere, then simply copy and paste 20 lines before the 526"make: ***" error anywhere, then simply copy and paste 20 lines before the

Legend:
Removed from v.1.15  
changed lines
  Added in v.1.16

  ViewVC Help
Powered by ViewVC 1.1.20