# Azamat H. Hackimov , 2009. msgid "" msgstr "" "Project-Id-Version: \n" "POT-Creation-Date: 2010-10-21 23:56+0600\n" "PO-Revision-Date: 2009-10-18 05:06+0600\n" "Last-Translator: Azamat H. Hackimov \n" "Language-Team: Russian \n" "Language: ru\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" "%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" "X-Generator: Lokalize 1.0\n" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):6 msgid "Gentoo Bug Reporting Guide" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(author:title):8 msgid "Author" msgstr "автор" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(mail:link):9 msgid "chriswhite@gentoo.org" msgstr "chriswhite@gentoo.org" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(mail):9 msgid "Chris White" msgstr "Chris White" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(author:title):11 msgid "Editor" msgstr "редактор" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(mail:link):12 msgid "fox2mike@gentoo.org" msgstr "fox2mike@gentoo.org" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(mail):12 msgid "Shyam Mani" msgstr "Shyam Mani" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(abstract):15 msgid "This document shows the proper method of reporting bugs using Bugzilla." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(version):23 #, fuzzy msgid "1.15" msgstr "1.14" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(date):24 #, fuzzy msgid "2010-02-27" msgstr "2009-03-05" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):27 #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):104 #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):344 #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):422 #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):584 #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):756 msgid "Introduction" msgstr "Введение" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):29 msgid "Preface" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):32 msgid "" "One of the factors that delay a bug being fixed is the way it is reported. " "By creating this guide, we hope to help improve the communication between " "developers and users in bug resolution. Getting bugs fixed is an important, " "if not crucial part of the quality assurance for any project and hopefully " "this guide will help make that a success." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):43 msgid "Bugs!!!!" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):46 msgid "" "You're emerge-ing a package or working with a program and suddenly the worst " "happens -- you find a bug. Bugs come in many forms like emerge failures or " "segmentation faults. Whatever the cause, the fact still remains that such a " "bug must be fixed. Here is a few examples of such bugs." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):53 msgid "A run time error" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):53 #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):179 #, fuzzy, no-wrap msgid "" "\n" "$ ./bad_code `perl -e 'print \"A\"x100'`\n" "Segmentation fault\n" msgstr "" "\n" "$ ./bad_code `perl -e 'print Ax100'`\n" "Segmentation fault\n" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):58 msgid "An emerge failure" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):58 #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):605 #, no-wrap msgid "" "\n" "/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/include/g++-v3/backward/backward_warning.h:32:2:\n" "warning: #warning This file includes at least one deprecated or antiquated\n" "header. Please consider using one of the 32 headers found in section 17.4.1.2 of\n" "the C++ standard. Examples include substituting the <X> header for the <X.h>\n" "header for C++ includes, or <sstream> instead of the deprecated header\n" "<strstream.h>. To disable this warning use -Wno-deprecated.\n" "In file included from main.cc:40:\n" "menudef.h:55: error: brace-enclosed initializer used to initialize `\n" "OXPopupMenu*'\n" "menudef.h:62: error: brace-enclosed initializer used to initialize `\n" "OXPopupMenu*'\n" "menudef.h:70: error: brace-enclosed initializer used to initialize `\n" "OXPopupMenu*'\n" "menudef.h:78: error: brace-enclosed initializer used to initialize `\n" "OXPopupMenu*'\n" "main.cc: In member function `void OXMain::DoOpen()':\n" "main.cc:323: warning: unused variable `FILE*fp'\n" "main.cc: In member function `void OXMain::DoSave(char*)':\n" "main.cc:337: warning: unused variable `FILE*fp'\n" "make[1]: *** [main.o] Error 1\n" "make[1]: Leaving directory\n" "`/var/tmp/portage/xclass-0.7.4/work/xclass-0.7.4/example-app'\n" "make: *** [shared] Error 2\n" "\n" "!!! ERROR: x11-libs/xclass-0.7.4 failed.\n" "!!! Function src_compile, Line 29, Exitcode 2\n" "!!! 'emake shared' failed\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):88 msgid "" "These errors can be quite troublesome. However, once you find them, what do " "you do? The following sections will look at two important tools for handling " "run time errors. After that, we'll take a look at compile errors, and how to " "handle them. Let's start out with the first tool for debugging run time " "errors -- gdb." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):102 msgid "Debugging using GDB" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):107 msgid "" "GDB, or the (G)NU (D)e(B)ugger, is a program used to find run time errors " "that normally involve memory corruption. First off, let's take a look at " "what debugging entails. One of the main things you must do in order to debug " "a program is to emerge the program with FEATURES=\"nostrip\". " "This prevents the stripping of debug symbols. Why are programs stripped by " "default? The reason is the same as that for having gzipped man pages -- " "saving space. Here's how the size of a program varies with and without debug " "symbol stripping." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):117 msgid "Filesize Comparison" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):117 #, no-wrap msgid "" "\n" "(debug symbols stripped)\n" "-rwxr-xr-x 1 chris users 3140 6/28 13:11 bad_code\n" "(debug symbols intact)\n" "-rwxr-xr-x 1 chris users 6374 6/28 13:10 bad_code\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):124 msgid "" "Just for reference, bad_code is the program we'll be debugging with " "gdb later on. As you can see, the program without debugging symbols " "is 3140 bytes, while the program with them is 6374 bytes. That's close to " "double the size! Two more things can be done for debugging. The first is " "adding ggdb to your CFLAGS and CXXFLAGS. This flag adds more " "debugging information than is generally included. We'll see what that means " "later on. This is how /etc/make.confmight look with the " "newly added flags." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):134 msgid "make.conf settings" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):134 #, no-wrap msgid "" "\n" "CFLAGS=\"-O1 -pipe -ggdb\"\n" "CXXFLAGS=\"${CFLAGS}\"\n" msgstr "" "\n" "CFLAGS=\"-O1 -pipe -ggdb\"\n" "CXXFLAGS=\"${CFLAGS}\"\n" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):139 msgid "" "Lastly, you can also add debug to the package's USE flags. This can be done " "with the package.use file." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):144 msgid "Using package.use to add debug USE flag" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):144 #, no-wrap msgid "" "\n" "# echo \"category/package debug\" >> /etc/portage/package.use\n" msgstr "" "\n" "# echo \"category/package debug\" >> /etc/portage/package.use\n" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):148 msgid "" "The directory /etc/portage does not exist by default and you " "may have to create it, if you have not already done so. If the package " "already has USE flags set in package.use, you will need to " "manually modify them in your favorite editor." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):155 msgid "" "Then we re-emerge the package with the modifications we've done so far as " "shown below." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):160 msgid "Re-emergeing a package with debugging" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):160 #, no-wrap msgid "" "\n" "# FEATURES=\"nostrip\" emerge package\n" msgstr "" "\n" "# FEATURES=\"nostrip\" emerge package\n" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):164 msgid "" "Now that debug symbols are setup, we can continue with debugging the program." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):171 msgid "Running the program with GDB" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):174 msgid "" "Let's say we have a program here called \"bad_code\". Some person claims " "that the program crashes and provides an example. You go ahead and test it " "out:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):179 msgid "Breaking The Program" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):184 msgid "" "It seems this person was right. Since the program is obviously broken, we " "have a bug at hand. Now, it's time to use gdb to help solve this " "matter. First we run gdb with --args, then give it the full " "program with arguments like shown:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):191 msgid "Running Our Program Through GDB" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):191 #, no-wrap msgid "" "\n" "$ gdb --args ./bad_code `perl -e 'print \"A\"x100'`\n" "GNU gdb 6.3\n" "Copyright 2004 Free Software Foundation, Inc.\n" "GDB is free software, covered by the GNU General Public License, and you are\n" "welcome to change it and/or distribute copies of it under certain conditions.\n" "Type \"show copying\" to see the conditions.\n" "There is absolutely no warranty for GDB. Type \"show warranty\" for details.\n" "This GDB was configured as \"i686-pc-linux-gnu\"...Using host libthread_db library \"/lib/libthread_db.so.1\".\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):202 msgid "" "One can also debug with core dumps. These core files contain the same " "information that the program would produce when run with gdb. In order to " "debug with a core file with bad_code, you would run gdb ./bad_code core where core is the name of the core file." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):209 msgid "" "You should see a prompt that says \"(gdb)\" and waits for input. First, we " "have to run the program. We type in run at the command and receive a " "notice like:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):214 msgid "Running the program in GDB" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):214 #, no-wrap msgid "" "\n" "(gdb) run\n" "Starting program: /home/chris/bad_code\n" "\n" "Program received signal SIGSEGV, Segmentation fault.\n" "0xb7ec6dc0 in strcpy () from /lib/libc.so.6\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):222 msgid "" "Here we see the program starting, as well as a notification of SIGSEGV, or " "Segmentation Fault. This is GDB telling us that our program has crashed. It " "also gives the last run function it could trace when the program crashes. " "However, this isn't too useful, as there could be multiple strcpy's in the " "program, making it hard for developers to find which one is causing the " "issue. In order to help them out, we do what's called a backtrace. A " "backtrace runs backwards through all the functions that occurred upon " "program execution, to the function at fault. Functions that return (without " "causing a crash) will not show up on the backtrace. To get a backtrace, at " "the (gdb) prompt, type in bt. You will get something like this:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):235 msgid "Program backtrace" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):235 #, no-wrap msgid "" "\n" "(gdb) bt\n" "#0 0xb7ec6dc0 in strcpy () from /lib/libc.so.6\n" "#1 0x0804838c in run_it ()\n" "#2 0x080483ba in main ()\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):242 msgid "" "You can notice the trace pattern clearly. main() is called first, followed " "by run_it(), and somewhere in run_it() lies the strcpy() at fault. Things " "such as this help developers narrow down problems. There are a few " "exceptions to the output. First off is forgetting to enable debug symbols " "with FEATURES=\"nostrip\". With debug symbols stripped, the output " "looks something like this:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):251 msgid "Program backtrace With debug symbols stripped" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):251 #, no-wrap msgid "" "\n" "(gdb) bt\n" "#0 0xb7e2cdc0 in strcpy () from /lib/libc.so.6\n" "#1 0x0804838c in ?? ()\n" "#2 0xbfd19510 in ?? ()\n" "#3 0x00000000 in ?? ()\n" "#4 0x00000000 in ?? ()\n" "#5 0xb7eef148 in libgcc_s_personality () from /lib/libc.so.6\n" "#6 0x080482ed in ?? ()\n" "#7 0x080495b0 in ?? ()\n" "#8 0xbfd19528 in ?? ()\n" "#9 0xb7dd73b8 in __guard_setup () from /lib/libc.so.6\n" "#10 0xb7dd742d in __guard_setup () from /lib/libc.so.6\n" "#11 0x00000006 in ?? ()\n" "#12 0xbfd19548 in ?? ()\n" "#13 0x080483ba in ?? ()\n" "#14 0x00000000 in ?? ()\n" "#15 0x00000000 in ?? ()\n" "#16 0xb7deebcc in __new_exitfn () from /lib/libc.so.6\n" "#17 0x00000000 in ?? ()\n" "#18 0xbfd19560 in ?? ()\n" "#19 0xb7ef017c in nullserv () from /lib/libc.so.6\n" "#20 0xb7dd6f37 in __libc_start_main () from /lib/libc.so.6\n" "#21 0x00000001 in ?? ()\n" "#22 0xbfd195d4 in ?? ()\n" "#23 0xbfd195dc in ?? ()\n" "#24 0x08048201 in ?? ()\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):280 msgid "" "This backtrace contains a large number of ?? marks. This is because without " "debug symbols, gdb doesn't know how the program was run. Hence, it is " "crucial that debug symbols are not stripped. Now remember a while ago " "we mentioned the -ggdb flag. Let's see what the output looks like with the " "flag enabled:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):288 msgid "Program backtrace with -ggdb" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):288 #, no-wrap msgid "" "\n" "(gdb) bt\n" "#0 0xb7e4bdc0 in strcpy () from /lib/libc.so.6\n" "#1 0x0804838c in run_it (input=0x0) at bad_code.c:7\n" "#2 0x080483ba in main (argc=1, argv=0xbfd3a434) at bad_code.c:12\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):295 msgid "" "Here we see that a lot more information is available for developers. Not " "only is function information displayed, but even the exact line numbers of " "the source files. This method is the most preferred if you can spare the " "extra space. Here's how much the file size varies between debug, strip, and -" "ggdb enabled programs." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):303 msgid "Filesize differences With -ggdb flag" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):303 #, no-wrap msgid "" "\n" "(debug symbols stripped)\n" "-rwxr-xr-x 1 chris users 3140 6/28 13:11 bad_code\n" "(debug symbols enabled)\n" "-rwxr-xr-x 1 chris users 6374 6/28 13:10 bad_code\n" "(-ggdb flag enabled)\n" "-rwxr-xr-x 1 chris users 19552 6/28 13:11 bad_code\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):312 msgid "" "As you can see, -ggdb adds about 13178 more bytes to the file size " "over the one with debugging symbols. However, as shown above, this increase " "in file size can be worth it if presenting debug information to developers. " "The backtrace can be saved to a file by copying and pasting from the " "terminal (if it's a non-x based terminal, you can use gpm. To keep this doc " "simple, I recommend you read up on the documentation for gpm to see how to copy and paste " "with it). Now that we're done with gdb, we can quit." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):323 msgid "Quitting GDB" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):323 #, no-wrap msgid "" "\n" "(gdb) quit\n" "The program is running. Exit anyway? (y or n) y\n" "$\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):329 msgid "" "This ends the walk-through of gdb. Using gdb, we hope that you " "will be able to use it to create better bug reports. However, there are " "other types of errors that can cause a program to fail during run time. One " "of the other ways is through improper file access. We can find those using a " "nifty little tool called strace." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):342 msgid "Finding file access errors using strace" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):347 msgid "" "Programs often use files to fetch configuration information, access hardware " "or write logs. Sometimes, a program attempts to reach such files " "incorrectly. A tool called strace was created to help deal with this. " "strace traces system calls (hence the name) which include calls that " "use the memory and files. For our example, we're going to take a program " "foobar2. This is an updated version of foobar. However, during the change " "over to foobar2, you notice all your configurations are missing! In foobar " "version 1, you had it setup to say \"foo\", but now it's using the default " "\"bar\"." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):358 msgid "Foobar2 With an invalid configuration" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):358 #, no-wrap msgid "" "\n" "$ ./foobar2\n" "Configuration says: bar\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):363 msgid "" "Our previous configuration specifically had it set to foo, so let's use " "strace to find out what's going on." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):371 msgid "Using strace to track the issue" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):374 msgid "" "We make strace log the results of the system calls. To do this, we " "run strace with the -o[file] arguments. Let's use it on foobar2 as " "shown." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):379 msgid "Running foobar2 through strace" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):379 #, no-wrap msgid "" "\n" "# strace -ostrace.log ./foobar2\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):383 msgid "" "This creates a file called strace.log in the current directory. " "We check the file, and shown below are the relevant parts from the file." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):388 msgid "A Look At the strace Log" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):388 #, no-wrap msgid "" "\n" "open(\".foobar2/config\", O_RDONLY) = 3\n" "read(3, \"bar\", 3) = 3\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):393 msgid "" "Aha! So There's the problem. Someone moved the configuration directory to " ".foobar2 instead of .foobar. We also see the " "program reading in \"bar\" as it should. In this case, we can recommend the " "ebuild maintainer to put a warning about it. For now though, we can copy " "over the config file from .foobar and modify it to produce the " "correct results." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):405 #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):740 #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):1456 msgid "Conclusion" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):408 msgid "" "Now we've taken care of finding run time bugs. These bugs prove to be " "problematic when you try and run your programs. However, run time errors are " "the least of your concerns if your program won't compile at all. Let's take " "a look at how to address emerge compile errors." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):420 msgid "Handling emerge Errors" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):425 msgid "" "emerge errors, such as the one displayed earlier, can be a major " "cause of frustration for users. Reporting them is considered crucial for " "maintaining the health of Gentoo. Let's take a look at a sample ebuild, " "foobar2, which contains some build errors." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):435 msgid "Evaluating emerge Errors" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):438 msgid "Let's take a look at this very simple emerge error:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):442 msgid "emerge Error (long lines are manually wrapped to fit the window)" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):442 #, no-wrap msgid "" "\n" "gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n" " -c -o foobar2-7.o foobar2-7.c\n" "gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n" " -c -o foobar2-8.o foobar2-8.c\n" "gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n" " -c -o foobar2-9.o foobar2-9.c\n" "gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n" " -c -o foobar2.o foobar2.c\n" "foobar2.c:1:17: ogg.h: No such file or directory\n" "make: *** [foobar2.o] Error 1\n" "\n" "!!! ERROR: sys-apps/foobar2-1.0 failed.\n" "!!! Function src_compile, Line 19, Exitcode 2\n" "!!! Make failed!\n" "!!! If you need support, post the topmost build error, NOT this status message\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):460 msgid "" "The program is compiling smoothly when it suddenly stops and presents an " "error message. This particular error can be split into 3 different sections, " "The compile messages, the build error, and the emerge error message as shown " "below." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):466 msgid "Parts of the error (long lines are manually wrapped to fit the window)" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):466 #, no-wrap msgid "" "\n" "(Compilation Messages)\n" "gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n" " -c -o foobar2-7.o foobar2-7.c\n" "gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n" " -c -o foobar2-8.o foobar2-8.c\n" "gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n" " -c -o foobar2-9.o foobar2-9.c\n" "gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \\\n" " -c -o foobar2.o foobar2.c\n" "\n" "(Build Error)\n" "foobar2.c:1:17: ogg.h: No such file or directory\n" "make: *** [foobar2.o] Error 1\n" "\n" "(emerge Error)\n" "!!! ERROR: sys-apps/foobar2-1.0 failed.\n" "!!! Function src_compile, Line 19, Exitcode 2\n" "!!! Make failed!\n" "!!! If you need support, post the topmost build error, NOT this status message\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):488 msgid "" "The compilation messages are what lead up to the error. Most often, it's " "good to at least include 10 lines of compile information so that the " "developer knows where the compilation was at when the error occurred." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):494 msgid "" "Please make sure you always include error messages in English, even when " "your system language is set to something else. You can temporarily switch to " "English locale by prepending LC_ALL=C to the emerge command like this:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):500 msgid "Temporarily switching locale to English" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):500 #, no-wrap msgid "" "\n" "# LC_ALL=C emerge sys-apps/foobar2\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):504 msgid "" "This is also about the only time you should use the LC_ALL " "environmental variable for specifying locale settings. If you are looking " "for a way to switch your system's language, then please consult our Localization Guide instead." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):511 msgid "" "Make errors are the actual error and the information the developer needs. " "When you see \"make: ***\", this is often where the error has occurred. " "Normally, you can copy and paste 10 lines above it and the developer will be " "able to address the issue. However, this may not always work and we'll take " "a look at an alternative shortly." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):519 msgid "" "The emerge error is what emerge throws out as an error. Sometimes, " "this might also contain some important information. Often people make the " "mistake of posting the emerge error and that's all. This is useless by " "itself, but with make error and compile information, a developer can get " "what application and what version of the package is failing. As a side note, " "make is commonly used as the build process for programs (but not always). If you can't find a \"make: ***\" error anywhere, then simply copy and " "paste 20 lines before the emerge error. This should take care of most all " "build system error messages. Now let's say the errors seem to be quite " "large. 10 lines won't be enough to catch everything. That's where " "PORT_LOGDIR comes into play." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):535 msgid "emerge and PORT_LOGDIR" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):538 msgid "" "PORT_LOGDIR is a portage variable that sets up a log directory for separate " "emerge logs. Let's take a look and see what that entails. First, run your " "emerge with PORT_LOGDIR set to your favorite log location. Let's say we have " "a location /var/log/portage. We'll use that for our log " "directory:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):545 msgid "" "In the default setup, /var/log/portage does not exist, and you " "will most likely have to create it. If you do not, portage will fail to " "write the logs." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):551 msgid "emerge-ing With PORT_LOGDIR" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):551 #, no-wrap msgid "" "\n" "# PORT_LOGDIR=/var/log/portage emerge cate-gory/foobar2\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):555 msgid "" "Now the emerge fails again. However, this time we have a log we can work " "with, and attach to the bug later on. Let's take a quick look at our log " "directory." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):560 msgid "PORT_LOGDIR Contents" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):560 #, no-wrap msgid "" "\n" "# ls -la /var/log/portage\n" "total 16\n" "drwxrws--- 2 root root 4096 Jun 30 10:08 .\n" "drwxr-xr-x 15 root root 4096 Jun 30 10:08 ..\n" "-rw-r--r-- 1 root root 7390 Jun 30 10:09 cate-gory:foobar2-1.0:20090110-213217.log\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):568 msgid "" "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." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):582 msgid "Searching Using Bugzilla" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):587 msgid "" "Bugzilla is what we at Gentoo " "use to handle bugs. Gentoo's Bugzilla is reachable by HTTPS and HTTP. HTTPS " "is available for those on insecure networks or simply paranoid :). For the " "sake of consistency, we will be using the HTTPS version in the examples to " "follow. Head over to Gentoo Bugs " "to see how it looks." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):596 msgid "" "One of the most frustrating things for developers and bug-wranglers is " "finding duplicate bug reports. These cost them valuable time that they could " "otherwise use to work on more important bugs. Often, this can be prevented " "by a few simple search methods. So we're going to see how to search for bugs " "and find out if you have one that's similar. For this example, we're going " "to use the xclass emerge error that was used earlier." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):605 msgid "xclass emerge error" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):635 msgid "" "So to begin searching, we head over to the Bugzilla Homepage." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):640 #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):764 msgid "/images/docs/bugzie-homepage.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):640 #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):764 msgid "Bugzilla Homepage" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):642 msgid "" "We'll click on \"Query Existing bug reports\". The reason why we choose this " "over the basic bug search is because the basic bug search tends to give " "vague results and often hinders users from looking through the results and " "finding the duplicate bug. Once we click on the query screen, we reach the " "next page:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):649 msgid "/images/docs/bugzie-search.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):649 msgid "Bugzilla Search Page" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):651 msgid "" "If you've used the Advanced Search before, you'll most likely see that " "screen instead." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):656 msgid "" "Proceed by clicking on the \"Advanced Search\" link to bring up the Advanced " "Search page." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):661 msgid "/images/docs/bugzie-adv-search.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):661 msgid "Advanced Search Page" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):663 msgid "" "This is how the Advanced Search Page looks like. While it may seem " "overwhelming at first, we're going to look at a few simple areas to narrow " "down the rather vague searches bugzilla returns." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):669 msgid "/images/docs/bugzie-content.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):669 msgid "Content" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):671 msgid "" "The first field is the summary of the bug. Here we're simply going to put " "the name of the package that's crashing. If bugzie doesn't return results, " "try removing the package name, just in case someone didn't put that in the " "summary (highly unlikely, but we've seen a fair share of strange bug " "reports)." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):678 msgid "" "Product, Component, and Version should all be set to the default. This " "prevents us from being too specific and missing all the bugs." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):683 msgid "" "Comment is the important part. Use the comment field to list what appears to " "be a specific instance of the error. Basically, don't use anything like the " "beginning of the build error, find a line that's before it stating a true " "error. Also, you'll want to filter out any punctuation to prevent bugzilla " "from interpreting the results the comment the wrong way. Example from the " "xclass emerge error:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):692 msgid "Comment Line Content" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):692 #, no-wrap msgid "" "\n" "menudef.h:78: error: brace-enclosed initializer used to initialize `OXPopupMenu'\n" "(Remove the quotes ' ')\n" "menudef.h 78 error brace-enclosed initializer used to initialize OXPopupMenu\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):698 msgid "" "The above is specific enough to where we'll find the bug without wading " "through other xclass compile failure candidates." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):703 msgid "" "URI, Whiteboard, and Keywords can all be left alone. What we've entered so " "far should be enough to find our bug. Let's take a look at what we have " "filled out." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):708 msgid "/images/docs/bugzie-comp-search.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):708 msgid "Completed Search Form" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):710 msgid "Now we click on the Search button and here come the results..." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):714 msgid "/images/docs/bugzie-search-result.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):714 msgid "Search Results" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):716 msgid "" "Only 2 bugs! That's a lot easier to deal with. We click on the first one to " "check, and sure enough it's the one we're looking for." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):721 msgid "/images/docs/bugzie-located.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):721 msgid "Bug Located" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):723 msgid "" "Not only is it the one we want, but it has also been resolved. By checking " "the last comment we see the solution and know what to do in order to resolve " "it. Now, let's see what would have happened if we had not used the advanced " "search." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):729 msgid "/images/docs/bugzie-basic-search-result.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):729 msgid "Basic Search Results" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):731 msgid "" "4 more bugs to deal with! It gets even worse with larger packages. However, " "with these simple tools, we're able to significantly narrow down the search " "to try and locate a specific bug." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):743 msgid "" "Let's say that you have searched and searched but still can't find a bug. " "You've found yourself a new bug. Let's take a look at the bug reporting " "process for submitting your new bug." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):754 msgid "Reporting Bugs" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):759 msgid "" "In this chapter, we'll figure out how to use Bugzilla to file a shiny, new " "bug. Head over to Gentoo Bugs " "and..." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):766 msgid "Click on \"Report a Bug - Using the guided format\"." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):770 msgid "/images/docs/bugzie-prod-select.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):770 msgid "Product Selection" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):772 msgid "" "As you can see, major emphasis has been placed on putting your bug in " "the right place. Gentoo Linux is where a large majority of bugs go." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):777 msgid "" "Despite this, some people will file ebuild bugs in portage development " "(assumption that portage team handles the portage tree) or infra (assumption " "that infra has access to mirrors and rsync and can fix it directly). This is " "simply not how things work." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):784 msgid "" "Another common misconception occurs with our Documentation bugs. For " "example, a user finds a bug with the Catalyst Docs. The general tendency is to file a bug under Docs-" "user, which gets assigned to the GDP, when it should actually go to a member of the Release Engineering team. As a rule of thumb, only " "documentation under http://www.gentoo.org/doc/* is under the " "GDP. Anything under http://www.gentoo.org/proj/* is under the " "respective teams." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):795 msgid "" "We would rather see a bug whose product was not supposed to be Gentoo Linux " "but has been filed under the same rather than seeing a bug which belongs the " "Gentoo Linux product and filed elsewhere. While neither is preferred, the " "former is more acceptable and understandable (except website bugs.. we might " "have an issue with that...)." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):803 msgid "" "Our bug goes in Gentoo Linux as it's an ebuild bug. We head over there and " "are presented with the multi-step bug reporting process. Let us now proceed " "with Step 1..." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):809 msgid "/images/docs/bugzie-guide-step1.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):809 msgid "Guided Format Step 1" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):811 msgid "" "The first step here is really important (as the red text tells you). This is " "where you search to see that someone else hasn't hit the same bug you have, " "yet. If you do skip this step and a bug like yours already exists, it will " "be marked as a DUPLICATE thus wasting a large amount of QA effort. To give " "you an idea, the bug numbers that are struck out above are duplicate bugs. " "Now comes step 2, where we give the information." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):823 msgid "Required Information" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):826 msgid "/images/docs/bugzie-basic.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):826 msgid "Basic Information" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):828 msgid "Let us take a closer look at what's what." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):833 msgid "" "First, there's the Product. The product will narrow down the bug to a " "specific area of Gentoo like Bugzilla (for bugs relating to bugs.gentoo." "org), Docs-user(for User Documentation) or Gentoo Linux (for ebuilds and the " "like)." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):839 msgid "" "Component is where exactly the problem occurs, more specifically which part " "of selected product the bug comes under. This makes classification easier." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):843 msgid "" "Hardware platform is what architecture you're running. If you were running " "SPARC, you would set it to SPARC." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):847 msgid "" "Operating System is what Operating System you're using. Because Gentoo is " "considered a \"Meta-distribution\", it can run on other operating systems " "beside Linux." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):854 msgid "So, for our example bug, we have :" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):859 msgid "Product - Gentoo Linux (Since it is an ebuild issue)" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):860 msgid "Component - Application (It is an application at fault, foobar2)" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):861 msgid "Hardware Platform - All (This error could occur across architectures)" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):862 msgid "Operation System - All (It could occur on all types of systems)" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):865 msgid "/images/docs/bugzie-basic-comp.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):865 msgid "Completed Basic Information" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):868 msgid "" "Build Identifier is basically the User Agent of the browser that is being " "used to report the bugs (for logging purposes). You can just leave this as " "is." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):873 msgid "" "URL is optional and is used to point to relevant information on another site " "(upstream bugzilla, release notes on package homepage etc.). You should " "never use URL to point to pastebins for error messages, logs, emerge --" "info output, screenshots or similar information. Instead, these should " "always be attached to the bug." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):880 msgid "In the Summary, you should put the package category, name, and number." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):885 msgid "" "Not including the category in the summary really isn't too bad, but it's " "recommended. If you don't include the package name, however, we won't know " "what you're filling a bug for, and will have to ask you about it later. The " "version number is important for people searching for bugs. If 20 people " "filed bugs and not one put a version number, how would people looking for " "similar bugs be able to tell if one was there's? They'd have to look through " "every single bug, which isn't too hard, but if there are say, 200 bugs.. " "it's not that easy. After all the package information, you'll want to " "include a small description of the incident. Here's an example:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):897 msgid "/images/docs/bugzie-summary.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):897 msgid "Summary" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):899 msgid "" "These simple rules can make handling bugs a lot easier. Next are the " "details. Here we put in the information about the bug. We'll demonstrate " "with an example:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):904 msgid "/images/docs/bugzie-details.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):904 msgid "Details" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):906 msgid "" "Now the developer knows why we're filing the bug. They can then try to " "reproduce it. Reproducibility tells us how often we were able to make the " "problem recur. In this example, we can reproduce it any time simply by " "running foobar2. Let's put that information in." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):913 msgid "/images/docs/bugzie-reprod.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):913 msgid "Reproduction" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):915 msgid "" "We have explained how we found the bug. The next step is to explain what " "were the results we got and what we think they should actually be." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):920 msgid "/images/docs/bugzie-results.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):920 msgid "Results" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):922 msgid "" "We could then provide additional information. This could be things such as " "stack traces, sections (since the whole log is usually big and of not " "much use) of strace logs, but most importantly, your emerge --info " "output. Here's an example." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):929 msgid "/images/docs/bugzie-addl-info.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):929 msgid "Additional Information" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):931 msgid "" "Lastly we select the severity of the bug. Please look this over carefully. " "In most cases it's OK to leave it as is and someone will raise/lower it for " "you. However, if you raise the severity of the bug, please make sure you " "read it over carefully and make sure you're not making a mistake. A run down " "of the various levels is given below." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):940 msgid "" "Blocker - The program just plain doesn't want to emerge or is a major " "hinderance to the system. For example a baselayout issue which " "prevents a system from booting up would be a sure candidate to be labelled " "blocker." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):946 msgid "" "Critical - The program has loss of data or severe memory leaks during " "runtime. Again, an important program like say net-tools failing to " "compile could be labelled critical. It won't prevent the system from " "starting up, but is quite essential for day to day stuff." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):952 msgid "" "Major - The program crashes, but nothing that causes your system severe " "damage or information loss." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):956 msgid "Minor - Your program crashes here and there with apparent workarounds." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):959 msgid "" "Normal - The default. If you're not sure leave it here unless it's a new " "build or cosmetic change, then read below for more information." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):963 msgid "Trivial - Things such as a mispelled word or whitespace clean up." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):964 msgid "" "Enhancement - A request to enable a new feature in a program, or more " "specifically new ebuilds." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):970 msgid "/images/docs/bugzie-sev.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):970 msgid "Severity" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):972 msgid "Here, we'll set it to Normal." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):976 msgid "" "Now we can submit the bug report by clicking on the Submit Bug Report box. " "You will now see your new bug come up. See Bug 97561 for what the result looks like. " "We've reported our bug! Now let's see how it's dealt with." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):987 msgid "Zero-day bump requests" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):990 msgid "" "So far, we've shown what to do when filing a bug. Now let's take a look at " "what not to do." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):995 msgid "" "Suppose that you've eagerly been following an upstream project's schedule, " "and when you check their homepage, guess what? They just released a new " "version a few minutes ago! Most users would immediately rush over to " "Gentoo's bugzilla to report the new version is available; please bump the " "existing version and add it to Portage, etc. However, this is exactly what " "you should not do. These kinds of requests are called zero-day (or 0-" "day) bump requests, as they're made the same day that a new version is " "released." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(impo):1005 msgid "" "Please wait at least 48 hours before reporting a new release on " "our bugzilla. Also, you must check bugzilla before posting your " "request to make sure that someone else hasn't already reported it, or that " "the Gentoo maintainers haven't already dealt with the new version." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1012 msgid "" "Why should you wait? First, it's quite rude to demand that Gentoo developers " "drop everything they're doing just to add a new release that came out 15 " "minutes ago. Your zero-day bump request could be marked as INVALID or LATER, " "as developers have plenty of pressing issues to keep them busy. Second, " "developers are usually aware of pending new releases well in advance of " "users, as they must follow upstream quite closely. They already know a new " "version is on its way. In many cases, they will have already opened a bug, " "or might even already added it in Portage as a masked package." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1023 msgid "" "Be smart when testing and requesting new versions of packages. Search " "bugzilla before posting your bump request -- is there already a bug open? " "Have you synced lately; is it already in Portage? Has it actually been " "released by upstream? Basic common sense will go a long way, and will endear " "you to developers that already have a lot to do. If it's been several days " "since release and you're sure that there are no open requests for it (and " "that it's not in Portage), then you can open up a new bug. Be sure to " "mention that it compiles and runs well on your arch. Any other helpful " "information you provide is most welcome." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1034 msgid "" "Want to see the newest version of your favorite package in Portage? File " "smart bugs." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):1044 msgid "Working With Your Bug" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1048 msgid "" "Looking at the bug, we see the information we provided earlier. You will " "notice that the bug has been assigned to bug-wranglers@gentoo.org. This is " "the default location for Application component bugs." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1054 msgid "/images/docs/bugzie-new-basic.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1054 msgid "New Bug Basic Information" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1056 msgid "The details we entered about the bug are available as well." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1060 msgid "/images/docs/bugzie-new-details.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1060 msgid "New Bug Details" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1062 msgid "" "However, bug-wranglers (usually) won't fix our bugs, so we'll reassign it to " "someone that can (you can let bug-wranglers re-assign it for you as well). " "For this we use the package's metadata.xml. You can normally find them in " "/usr/portage/category/package/metadata.xml. Here's one I've " "made up for foobar2." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):1070 msgid "" "You have to be the reporter of the bug or a member of certain Gentoo " "Bugzilla groups (like Gentoo Developers) to be able to reassign bugs." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1075 msgid "metadata.xml" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1075 #, no-wrap msgid "" "\n" "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" "<!DOCTYPE pkgmetadata SYSTEM \"http://www.gentoo.org/dtd/metadata.dtd\">\n" "<pkgmetadata>\n" "<herd>chriswhite</herd>\n" "<maintainer>\n" "<email>chriswhite@gentoo.org</email>\n" "<name>Chris White</name>\n" "</maintainer>\n" "<longdescription lang=\"en\">\n" "Foobar2 is a package that uses a configuration file to display a word.\n" "</longdescription>\n" "</pkgmetadata>\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1090 msgid "" "Notice the maintainer section. This lists the maintainer of the package, " "which in this case is myself, Chris White. The email listed is " "chriswhite@gentoo.org. We will use this to re-assign the bug to the proper " "person. To do this, click the bubble next to Reassign bug to, then fill in " "the email." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):1097 msgid "" "A bug for a package without a metadata.xml file should be re-assigned to " "maintainer-needed@gentoo.org and a package that needs a Gentoo Developer to " "maintain should be assigned to maintainer-wanted@gentoo.org." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1103 msgid "/images/docs/bugzie-reassign.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1103 msgid "Bug Reassignment" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1105 msgid "" "Then hit the Commit button for the changes to take place. The bug has been " "reassigned to me. Shortly afterward, you notice (by email usually) that I've " "responded to your bug. I've stated that I'd like to see an strace log to " "figure out how the program is trying to reach your configuration file. You " "follow the previous instructions on using strace and obtain an strace log. " "Now you need to attach it to the bug. In order to do this, click on \"Create " "A New Attachment\"." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1114 msgid "/images/docs/bugzie-new-attach.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1114 msgid "New Attachment" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1116 msgid "Now we have to attach the log. Let's go throught it step wise." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1121 msgid "" "File - This is the location of the file in your machine. In this example, " "the location of strace.log. You can use the \"Browse...\" " "button to select the file, or enter the path directly in the text field." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1126 msgid "" "Description - A short one liner, or a few wors describing the attachment. " "We'll just enter strace.log here, since that's quite self-explanatory." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1130 msgid "Content Type - This is the type of the file we're attaching to the bug." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1133 msgid "" "Obsoletes - If there were attachements submitted to the bug before the " "current one, you have an option of declaring them obsoleted by yours. Since " "we have no prior attachments to this bug, we need not bother." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1138 msgid "" "Comment - Enter comments that will be visible along with the attachments. " "You could elaborate on the attachment here, if needed." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1144 msgid "" "With respect to Content Type, here are a few more details. You can check the " "\"patch\" checkbox if you're submitting a patch. Otherwise, you could ask " "Bugzilla to \"auto-detect\" the file type (not advisable). The other options " "are \"select from list\", which is most frequently used. Use plain text " "(text/plain) for most attachments except binary files like images " "(which can use image/gif, image/jpeg or image/png depending on type) or " "compressed files like .tar.bz2 which would use application/octet-stream as " "content type." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1155 msgid "/images/docs/bugzie-new-attach-comp.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1155 msgid "New Attachment Completed" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1157 msgid "" "We submit strace.log and it is reflected on the bug report." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1161 msgid "/images/docs/bugzie-strace.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1161 msgid "Attached strace log" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1163 msgid "" "We've mentioned before that sometimes ebuilds will tell you to attach a file " "in the emerge error. An example can be seen below." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1168 msgid "Example File Attachment Request" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1168 #, no-wrap msgid "" "\n" "configure: error: PNG support requires ZLIB. Use --with-zlib-dir=<DIR>\n" "\n" "!!! Please attach the config.log to your bug report:\n" "!!! /var/tmp/portage/php-5.0.3-r1/work/php-5.0.3/config.log\n" "\n" "!!! ERROR: dev-php/php-5.0.3-r1 failed.\n" "!!! Function econf, Line 485, Exitcode 0\n" "!!! econf failed\n" "!!! If you need support, post the topmost build error, NOT this status message.\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1180 msgid "Please attach any file mentioned like this to your bug report." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1184 msgid "" "Sometimes a developer might ask you to attach a diff or patch for a file. " "Standard diff files can be obtained through:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1189 msgid "Standard Diff Creation" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1189 #, no-wrap msgid "" "\n" "$ cp file file.old\n" "$ nano file\n" "$ diff -u file.old file\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1195 msgid "" "For C/C++ source files, the -p flag is added to show what function " "calls the diff applies to:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1200 msgid "Diff-ing C/C++ source" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1200 #, no-wrap msgid "" "\n" "$ cp file.c file.c.old\n" "$ nano file.c\n" "$ diff -up file.c.old file.c\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1206 msgid "" "The documentation team will require the flag combination -Nt as well " "as -u. This mainly has to do with tab expansion. You can create such " "a diff with:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1212 msgid "Documentation diffs" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1212 #, no-wrap msgid "" "\n" "$ cp file.xml file.xml.old\n" "$ nano file.xml\n" "$ diff -Nut file.xml.old file.xml\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1218 msgid "" "And your diff is created. While we're doing all this, suppose another person " "finds your bug by searching through bugzilla and is curious to keep track of " "the bug, they may do so by putting their email in the Add CC field of the " "bug as shown below. You could also keep track of other bugs by following the " "same method." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1226 msgid "/images/docs/bugzie-add-email.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1226 msgid "Adding Email To CC:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):1228 msgid "" "Email addresses must be registered with Gentoo Bugzilla. In order to CC " "multiple addresses, simply separate them with commas or spaces." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1233 msgid "" "After all this work, the bug can undergo various status markings. This is " "usually done by the Gentoo Developers and sometimes by the reporter. The " "following are the various possible states a bug may go through during its " "lifetime." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1241 msgid "" "UNCONFIRMED - You're generally not going to see this too often. This means " "that a bug reporter has opened a bug using the advanced method and is " "uncertain his or her bug is an actual bug." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1246 msgid "NEW - Bugs that are first opened are considered new." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1247 msgid "" "ASSIGNED - When the person you've assigned the bug too validates your bug, " "it will often receive ASSIGNED status while they figure out the issue. This " "lets you know that they've accepted your bug as a real bug." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1252 msgid "" "REOPENED - Someone has resolved a bug and you think the solution is not " "feasible or the problem still persists. At this point, you may re-open the " "bug. Please do not abuse this. If a developer closes the bug a second " "or third time, chances are that your bug is closed." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1258 msgid "" "RESOLVED - A firm decision has been taken on the bug. Usually goes onto " "FIXED to indicate the bug is solved and the matter closed although various " "other resolutions are possible. We'll look into those a little later." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1263 msgid "" "VERIFIED - The steps take to work the bug are correct. This is usually a QA " "thing." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1267 msgid "" "CLOSED - Basically means RIP for the bug and it's buried under the never " "ending flow of new bugs." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1273 msgid "" "Now shortly afterward, we find the error in the strace log and fix the bug " "and mark it as RESOLVED FIXED and mention that there was a change in the " "location of configuration files, and that I will update the ebuild with a " "warning about it. The bug now becomes resolved, and you are shown the " "following." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1280 msgid "/images/docs/bugzie-reso.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1280 msgid "Resolved Bug" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1282 msgid "A little below, you'll see the following:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1286 msgid "/images/docs/bugzie-options.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1286 msgid "Bug Options" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1288 msgid "" "This gives you the option of Reopening the bug if you wish to (i.e. the " "developer thinks it's resolved but it's really not to your standards). Now " "our bug is fixed! However, different resolutions can occur. Here's a small " "list:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1295 msgid "" "FIXED - The bug is fixed, follow the instructions to resolve your issue." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1298 msgid "" "INVALID - You did not do something specifically documented, causing the bug." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1302 msgid "DUPLICATE - You didn't use this guide and reported a duplicate bug." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1303 msgid "" "WORKSFORME - Developer/person assigned the bug cannot reproduce your error." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1306 msgid "" "CANTFIX - Somehow the bug cannot be solved because of certain circumstances. " "These circumstances will be noted by the person taking the bug." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1311 msgid "" "WONTFIX - This is usually applied to new ebuilds or feature requests. " "Basically the developer does not want to add a certain feature because it is " "not needed, a better alternative exists, or it's just plain broken. " "Sometimes you may be given a solution to get said issue resolved." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(li):1317 msgid "" "UPSTREAM - The bug cannot be fixed by the Gentoo development team, and have " "requested you take the problem upstream (the people that actually made the " "program) for review. Upstream has a few ways of handling bugs. These include " "mailing lists, irc channels, and even bug reporting systems. If you're not " "sure how to contact them, ask in the bug and someone will point you to the " "right direction." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1327 msgid "" "Sometimes, before the bug can be resolved, a developer may request that you " "test an updated ebulid. In the next chapter we'll take a look at testing " "ebuilds." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):1338 msgid "Testing Ebuilds" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):1340 msgid "Getting The Files" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1343 msgid "" "Let's say that you reported a bug for the foobar2 compile fix from earlier. " "Now developers might find out what the problem is and might need you to test " "the ebuild for them to be sure it works for you as well:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:link):1349 msgid "/images/docs/bugzie-ebuild-request.png" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(figure:caption):1349 msgid "Ebuild Test Request" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1351 msgid "" "Some rather confusing vocabulary is used here. First off, let's see what an " "overlay is. An overlay is a special directory like /usr/portage, the difference being that when you emerge sync, files " "contained within it will not be deleted. Luckily, a special /usr/local/" "portage directory is created for that purpose. Let's go ahead and set " "our portage overlay in/etc/make.conf. Open make.conf up in your " "favorite editor and add this towards the end." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1361 msgid "Setting Up PORTDIR_OVERLAY" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1361 #, no-wrap msgid "" "\n" "PORTDIR_OVERLAY=\"/usr/local/portage\"\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1365 msgid "" "Now we'll want to create the appropriate directories to put our test ebuild " "files in. In this case, we're supposed to put them in sys-apps/foobar2. " "You'll notice that the second comment asks for a files " "directory for the patch. This directory holds other required files that " "aren't included with the standard source archive (patches, init.d scripts, " "etc). This is a subdir in the package directory called files. " "Go ahead and create these directories:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1375 msgid "Setting Up The Category And Package Directories" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1375 #, no-wrap msgid "" "\n" "# mkdir -p /usr/local/portage/sys-apps/foobar2/files\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(note):1379 msgid "" "The -p in mkdir creates not only the directory you want but also any missing " "parent directories as well (sys-apps and foobar2 in this case)." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1384 msgid "" "Ok now, we can go ahead and download the files. First, download the ebuild " "into /usr/local/portage/sys-apps/foobar2, and then add the " "patch to /usr/local/portage/sys-apps/foobar2/files. Now that we " "have the files, we can begin working on testing the ebuild." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(title):1394 msgid "Testing The ebuild" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1397 msgid "" "The process to create an ebuild that can be used by emerge is fairly simple. " "You must create a Manifest file for the ebuild. This can be done with the " "ebuild command. Run it as shown." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1403 msgid "Creating the Manifest file" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1403 #, no-wrap msgid "" "\n" "# ebuild foobar2-1.0.ebuild manifest\n" ">>> Creating Manifest for /usr/local/portage/sys-apps/foobar2\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1408 msgid "Now let's test to see if it works as it should." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1412 msgid "Testing With emerge -pv" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1412 #, no-wrap msgid "" "\n" "# emerge -pv foobar2\n" "\n" "These are the packages that I would merge, in order:\n" "\n" "Calculating dependencies ...done!\n" "[ebuild N ] sys-apps/foobar2-1.0 0 kB [1]\n" "\n" "Total size of downloads: 0 kB\n" "Portage overlays:\n" " [1] /usr/local/portage\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1425 msgid "" "It does seem to have worked! You'll notice the [1] next to the [ebuild] " "line. That points to /usr/local/portage, which is the overlay " "we created earlier. Now we go ahead and emerge the package." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre:caption):1431 msgid "Emerge Result" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(pre):1431 #, no-wrap msgid "" "\n" "# emerge foobar2\n" " Calculating dependencies ...done!\n" "(compile info snipped)\n" ">>> Unpacking foobar2-1.0.tar.bz2 to /var/tmp/portage/foobar2-1.0/work\n" " * Applying foobar2-1.0-Makefile.patch ... [ ok ]\n" "(compile info snipped)\n" ">>> Merging sys-apps/foobar2-1.0 to /\n" ">>> chris +sandbox(preinst)\n" "--- /usr/\n" "--- /usr/bin/\n" ">>> /usr/bin/foobar2\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1445 msgid "" "In the first section we see that the emerge started off as it should. The " "second section shows our patch being applied successfully by the \"[ ok ]\" " "status message to the right. The last section tells us the program compiled " "ok. The patch works! Now we can go and let the developer know that their " "patch works fine, and that they can commit the fix to portage." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(p):1459 msgid "" "This concludes the howto on working with Bugzilla. I hope you find this " "useful. If you have any questions, comments, or ideas regarding this " "document, please send them to me at chriswhite@gentoo.org. " "Special thanks go to moreon for his notes on -g flags and compile errors, " "the people at #gentoo-bugs for helping out with bug-wrangling, Griffon26 for " "his notes on maintainer-needed, robbat2 for general suggestions and fox2mike " "for fixing up the doc and adding stuff as needed." msgstr "" #. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL #: ../../gentoo/xml/htdocs/doc/en//bugzilla-howto.xml(None):0 msgid "translator-credits" msgstr ""