/[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.1 Revision 1.2
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.1 2005/07/07 12:02:21 fox2mike Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.2 2005/07/07 18:19:23 fox2mike 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">
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.0</version> 23<version>1.1</version>
24<date>2005-07-07</date> 24<date>2005-07-07</date>
25 25
26<chapter> 26<chapter>
27<title>Introduction</title> 27<title>Introduction</title>
28<section> 28<section>
362<pre caption="Running foobar2 through strace"> 362<pre caption="Running foobar2 through strace">
363# <i>strace -ostrace.log ./foobar2</i> 363# <i>strace -ostrace.log ./foobar2</i>
364</pre> 364</pre>
365 365
366<p> 366<p>
367This creates a file called strace.log in the current directory. We check the 367This creates a file called <path>strace.log</path> in the current directory. We
368file, and shown below are the relevant parts from the file. 368check the file, and shown below are the relevant parts from the file.
369</p> 369</p>
370 370
371<pre caption="A Look At the strace Log"> 371<pre caption="A Look At the strace Log">
372open(".foobar2/config", O_RDONLY) = 3 372open(".foobar2/config", O_RDONLY) = 3
373read(3, "bar", 3) = 3 373read(3, "bar", 3) = 3
376<p> 376<p>
377Aha! So There's the problem. Someone moved the configuration directory to 377Aha! So There's the problem. Someone moved the configuration directory to
378<path>.foobar2</path> instead of <path>.foobar</path>. We also see the program 378<path>.foobar2</path> instead of <path>.foobar</path>. We also see the program
379reading in "bar" as it should. In this case, we can recommend the ebuild 379reading in "bar" as it should. In this case, we can recommend the ebuild
380maintainer to put a warning about it. For now though, we can copy over the 380maintainer to put a warning about it. For now though, we can copy over the
381config file from .foobar and modify it to produce the correct results. 381config file from <path>.foobar</path> and modify it to produce the correct
382results.
382</p> 383</p>
383 384
384</body> 385</body>
385</section> 386</section>
386<section> 387<section>
582!!! 'emake shared' failed 583!!! 'emake shared' failed
583</pre> 584</pre>
584 585
585<p> 586<p>
586So to begin searching, we head over to the <uri 587So to begin searching, we head over to the <uri
587link="http://bugs.gentoo.org/">Bugzilla Homepage</uri>. 588link="https://bugs.gentoo.org/">Bugzilla Homepage</uri>.
588</p> 589</p>
589 590
590<figure link="/images/docs/bugzie-homepage.png" caption="Bugzilla Homepage"/> 591<figure link="/images/docs/bugzie-homepage.png" caption="Bugzilla Homepage"/>
591 592
592<p> 593<p>
962After all this work, the bug can undergo various status markings. Here's a few: 963After all this work, the bug can undergo various status markings. Here's a few:
963</p> 964</p>
964 965
965<ul> 966<ul>
966 <li> 967 <li>
967 UNCONFIRMED - You're generally not going to see this too often. This 968 UNCONFIRMED - You're generally not going to see this too often. This
968 means that a bug reporter has opened a bug using the advanced method and is 969 means that a bug reporter has opened a bug using the advanced method and is
969 uncertain his or her bug is an actual bug. 970 uncertain his or her bug is an actual bug.
970 </li> 971 </li>
971 <li> 972 <li>
972 NEW - Bugs that are first opened are considered new. 973 NEW - Bugs that are first opened are considered new.
973 </li> 974 </li>
974 <li> 975 <li>
975 ASSIGNED - When the person you've assigned the bug too validates your 976 ASSIGNED - When the person you've assigned the bug too validates your
976 bug, it will often receive ASSIGNED status while they figure out the issue. 977 bug, it will often receive ASSIGNED status while they figure out the issue.
977 This let's you know that they've accepted your bug as a real bug. 978 This let's you know that they've accepted your bug as a real bug.
978 </li> 979 </li>
979 <li> 980 <li>
980 REOPENED - Someone has resolved a bug and you think the solution is not 981 REOPENED - Someone has resolved a bug and you think the solution is not
981 feasible or the problem still persists. At this point, you may re-open the 982 feasible or the problem still persists. At this point, you may re-open the
982 bug. However <b>please do not abuse this</b>. If a developer closes the bug a 983 bug. However <b>please do not abuse this</b>. If a developer closes the bug a
983 second or even third time, chances are that your bug is closed. 984 second or even third time, chances are that your bug is closed.
984 </li> 985 </li>
985</ul> 986</ul>
986 987
987<p> 988<p>
988Now shortly afterward, I find the error in the strace log. I resolve the bug 989Now shortly afterward, I find the error in the strace log. I resolve the bug
989as RESOLVED FIXED and say that there was a change in the location of 990as RESOLVED FIXED and say that there was a change in the location of
1005fixed! However, different resolutions can occur. Here's a small list: 1006fixed! However, different resolutions can occur. Here's a small list:
1006</p> 1007</p>
1007 1008
1008<ul> 1009<ul>
1009 <li> 1010 <li>
1010 FIXED - The bug is fixed, follow the instructions to resolve your 1011 FIXED - The bug is fixed, follow the instructions to resolve your
1011 issue. 1012 issue.
1012 </li> 1013 </li>
1013 <li> 1014 <li>
1014 INVALID - You did not do something specifically documented, causing the 1015 INVALID - You did not do something specifically documented, causing the
1015 bug 1016 bug
1016 </li> 1017 </li>
1017 <li> 1018 <li>
1018 DUPLICATE - You didn't use this guide and reported a duplicate bug 1019 DUPLICATE - You didn't use this guide and reported a duplicate bug
1019 :) 1020 :)
1020 </li> 1021 </li>
1021 <li> 1022 <li>
1022 WORKSFORME - Developer/person assigned the bug cannot reproduce your 1023 WORKSFORME - Developer/person assigned the bug cannot reproduce your
1023 error 1024 error
1024 </li> 1025 </li>
1025</ul> 1026</ul>
1026 1027
1027</body> 1028</body>
1028</section> 1029</section>
1029 1030

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.2

  ViewVC Help
Powered by ViewVC 1.1.20