Bugzilla/Bug report guide/ko

이 글은 여러분이 버그 보고서를 제출할 때 다른 사람들을 편하게 하기 위해 지켜야 할 여러가지 사항을 다룹니다. 항상 기억해두시고, 여러분이 제기한 문제를 원하는 대로 다룬다는 사실을 항상 기억하십시오:

Best practices

 * Reread the text before submission, the text cannot be edited afterwards. Also any text entered into a bug report will be usually e-mailed immediately to many people. Write in precise and clean language and avoid colloquial speech. Hint: Imagine you have only one chance in your life to write this very important bug report. You know that the recipient can read English, but it is not his native language.


 * Search for duplicates, before creating a new bug.


 * Stay on topic - A bug ticket is used for technical reports and chitchat should be avoided. Keep them in the support channels (forums, IRC or mailing-lists).
 * Confirm the existence of a problem only once. - It does not help solving the problem, if you and another person report it twice. But if your and the confirmer's systems differ in an obvious way and that would be helpful to know, add this information.
 * Open one bug ticket per topic - If your problem is not discussed on a bug, search for one related to your issue or create a new report. Do not hijack bugs.
 * No talk on TRACKER bugs. - Those bugs are meta bugs. If you want to add useful information, add them to a related sub bug or create a new bug.

Optional: Commercial Gentoo support
If you need commercial support with bugs, any trouble around Gentoo or a new ebuild, have a look on the list of professional Gentoo consultants.

꾸러미/이빌드
버그에 시스템 설정 정보를 항상 추가해야합니다. 이렇게 하려면 다음 내용을 새 첨부 파일로 만들어 붙여넣으십시오:

Report a build-time bug (emerge failed)

 * First write the exact version of the package in the title of the bug report e.g. sys-apps/package-2.3-r4
 * Add a short description to the title.
 * Attach the logfile in
 * If your logfile is too big to upload, compress it: and upload the build.log.xz
 * Attach the output of

Report a run-time bug
파일 및 관심 정보는 우선 순위에 따라 정렬합니다:


 * The exact version of the package in the title of the bug report e.g. sys-apps/package-2.3-r4 crashes with error: Cannot proceed...
 * Description of the problem, so that other can reproduce it:
 * How is the program run (on the console, in a terminal, as a daemon, in what runlevel etc.)
 * Any error output
 * What makes the program crash, behave wrong, not start
 * Is there a workaround?
 * What was the last working version of the package, if any?
 * What changed to make it not work?
 * Attach the output of emerge --info
 * Attach the output of emerge -pv  to quickly see what are the dependencies

Report a version bump; a newer upstream release is available since a while

 * Search Bugzilla before posting a bump request - is there already a bug open? Has the local Portage tree been synced lately; is it already in Portage?
 * Avoid Zero-day bump requests (wait at least 48 hours after the release announcement)
 * Has it actually been released by upstream sources, or is it just marked in the source tree? Some projects mark a release in the tree long time before it is officially released.
 * Be sure to mention if it compiles and runs well on your arch. Any other helpful information you provide is most welcome.
 * Add a link to the upstream website
 * Give a link or list of fixed bugs or new features (sometimes called changelog)
 * Write a title in the form app-editors/vim-12.3.5 version bump

Optional

 * Does the ebuild need changes? (changed dependencies, obsolete patch files)
 * Please note, if the new version needs no changes to the ebuild's contents
 * Test the ebuild in a local overlay before submitting attachments
 * Provide patches for proposed ebuild edits, with optional explanation of changes (file name should match the new version number, not old)
 * Provide additional files (initd, unit files) as separate attachments (as needed)
 * Do not paste files directly into comments; use attachments

Request for a new package; ebuild request
포티지 트리에 추가할 프로그램의 새 이빌드를 요청하려면 꾸러미의 관리자를 찾거나 자신이 직접 꾸러미 관리자가 돼야합니다:


 * Link to the upstream website in the bug report
 * Give a link or list of features
 * Suggest a preliminary category and package name for the ebuild in the subject line for example "media-gfx/inkscape ebuild request"
 * Provide an ebuild and patches that were tested in your local overlay (you can get help in IRC or in the forums with that)

XY 꾸러미를 안정 버전으로 처리해야 함
비 안정버전 상태에서 30일 이상이 흘렀지만 여전히 불안정하다고 표시한 꾸러미를 빌드하고 문제없이 시스템에서 돌아가는 경우에 해당합니다:


 * stable/unstable 브랜치에 대한 내용은 KEYWORDS 참조
 * 여러분이 안정 버전으로 표시하길 원하는대로 충분히 시험했습니까?
 * 어떤 버그와 관련하여 다른 버그 보고서가 있습니까?
 * 포티지 트리의 꾸러미 버전을 최소한 30일전에 등록 처리했습니까?
 * 의존 요소를 안정 버전으로 표시했습니까?

커널
커널 버그 보고서의 파일과 관심 정보는 우선 순위에 따라 정렬합니다:


 * 사용하고 있는 커널 및 버전, 사용중인 아키텍처. x86_64의 gentoo-sources-3.4.2-r2
 * 커널 설정 파일을 버그 보고서에 첨부해야합니다
 * 시스템의 모든 장치 목록을 lspci -k로 가져올 수 있습니다
 * 커널 초기화시에 나오는 또는  로그 파일을 첨부해야합니다.

다른 버그 보고
실제 양식은 없습니다. wiki.gentoo.org, forum.gentoo.org 하단의 캡차 또는 프로그램과 관련이 없는 다른 문제와 유사한 분류에 양식을 두었습니다.

추가 참조

 * Bugzilla guide
 * Contributing to Gentoo
 * Stable request
 * Gentoo Github - Helping the Gentoo project and considering sending a Pull Request via GitHub

외부 자료

 * 젠투 버그질라 사이트