[gentoo-commits] gentoo commit in xml/htdocs/doc/en: bugzilla-howto.xml

[Joshua Saddler (nightmorph)]

nightmorph    09/01/26 07:34:42

  Modified:             bugzilla-howto.xml
  Log:
  new bugzie format, patches from pva on bug 254488

Revision  Changes    Path
1.14                 xml/htdocs/doc/en/bugzilla-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.14&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.14&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?r1=1.13&r2=1.14

Index: bugzilla-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- bugzilla-howto.xml	23 May 2008 20:42:42 -0000	1.13
+++ bugzilla-howto.xml	26 Jan 2009 07:34:41 -0000	1.14
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.13 2008/05/23 20:42:42 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.14 2009/01/26 07:34:41 nightmorph Exp $ -->
 
 <guide link="/doc/en/bugzilla-howto.xml">
 <title>Gentoo Bug Reporting Guide</title>
@@ -20,8 +20,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.11</version>
-<date>2008-01-31</date>
+<version>1.12</version>
+<date>2009-01-25</date>
 
 <chapter>
 <title>Introduction</title>
@@ -439,11 +439,15 @@
 Let's take a look at this very simple <c>emerge</c> error:
 </p>
 
-<pre caption="emerge Error">
-gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod   -c -o foobar2-7.o foobar2-7.c
-gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod   -c -o foobar2-8.o foobar2-8.c
-gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod   -c -o foobar2-9.o foobar2-9.c
-gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod   -c -o foobar2.o foobar2.c
+<pre caption="emerge Error (long lines are manually wrapped to fit the window)">
+gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \
+ -c -o foobar2-7.o foobar2-7.c
+gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \
+ -c -o foobar2-8.o foobar2-8.c
+gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \
+ -c -o foobar2-9.o foobar2-9.c
+gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \
+ -c -o foobar2.o foobar2.c
 foobar2.c:1:17: ogg.h: No such file or directory
 make: *** [foobar2.o] Error 1
 
@@ -459,12 +463,16 @@
 compile messages, the build error, and the emerge error message as shown below.
 </p>
 
-<pre caption="Parts of the error">
+<pre caption="Parts of the error (long lines are manually wrapped to fit the window)">
 <comment>(Compilation Messages)</comment>
-gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod   -c -o foobar2-7.o foobar2-7.c
-gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod   -c -o foobar2-8.o foobar2-8.c
-gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod   -c -o foobar2-9.o foobar2-9.c
-gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod   -c -o foobar2.o foobar2.c
+gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \
+ -c -o foobar2-7.o foobar2-7.c
+gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \
+ -c -o foobar2-8.o foobar2-8.c
+gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \
+ -c -o foobar2-9.o foobar2-9.c
+gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \
+ -c -o foobar2.o foobar2.c
 
 <comment>(Build Error)</comment>
 foobar2.c:1:17: ogg.h: No such file or directory
@@ -524,7 +532,7 @@
 </note>
 
 <pre caption="emerge-ing With PORT_LOGDIR">
-# <i>PORT_LOGDIR=/var/log/portage emerge foobar2</i>
+# <i>PORT_LOGDIR=/var/log/portage emerge cate-gory/foobar2</i>
 </pre>
 
 <p>
@@ -537,18 +545,16 @@
 total 16
 drwxrws---   2 root root 4096 Jun 30 10:08 .
 drwxr-xr-x  15 root root 4096 Jun 30 10:08 ..
--rw-r--r--   1 root root 7390 Jun 30 10:09 2115-foobar2-1.0.log
+-rw-r--r--   1 root root 7390 Jun 30 10:09 cate-gory:foobar2-1.0:20090110-213217.log
 </pre>
 
 <p>
-The log files have the format [counter]-[package name]-[version].log. Counter
-is a special variable that is meant to state this package as the n-th package
-you've emerged. This prevents duplicate logs from appearing. A quick look at
-the log file will show the entire emerge process. This can be attached later
-on as we'll see in the bug reporting section. Now that we've safely obtained
-our information needed to report the bug we can continue to do so. However,
-before we get started on that, we need to make sure no one else has reported
-the issue. Let's take a look at searching for bugs.
+The log files have the format [category]:[package name]-[version]:[date].log. A
+quick look at the log file will show the entire emerge process. This can be
+attached later on as we'll see in the bug reporting section. Now that we've
+safely obtained our information needed to report the bug we can continue to do
+so. However, before we get started on that, we need to make sure no one else
+has reported the issue. Let's take a look at searching for bugs.
 </p>
 
 </body>