|
|
148.
|
|
|
Introduction
|
|
|
|
|
紹介
|
|
Translated and reviewed by
Kentaro Kazuhama
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:6
../ubuntu-packaging-guide/security-and-stable-release-updates.rst:9
|
|
|
149.
|
|
|
If you followed the instructions to :doc:`get set up with Ubuntu Development<./getting-set-up>`, you should be all set and ready to go.
|
|
|
|
|
:doc:`get set up with Ubuntu Development<./getting-set-up>` をまだ読んでいないなら、まずはそちらで設定を行ってから先に読み進めてください。
|
|
Translated by
Mitsuya Shibata
|
|
Reviewed by
Kentaro Kazuhama
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:8
|
|
|
150.
|
|
|
As you can see in the image above, there is no surprises in the process of fixing bugs in Ubuntu: you found a problem, you get the code, work on the fix, test it, push your changes to Launchpad and ask for it to be reviewed and merged. In this guide we will go through all the necessary steps one by one.
|
|
|
|
|
上図からもわかる通り、Ubuntuにおけるバグ修正の手順に特別な意外性はありません：問題を見つけたら、ソースコードを取得し、問題を修正し、テストし、変更点をLaunchpadに報告し、レビューとマージ（取り込み）のための依頼をするだけです。このガイドでは、必要なすべての手順について、一つずつ説明します。
|
|
Translated by
Mitsuya Shibata
|
|
Reviewed by
Kentaro Kazuhama
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:13
|
|
|
151.
|
|
|
Finding the problem
|
|
|
|
|
問題を見つける
|
|
Translated by
Shushi Kurose
|
|
Reviewed by
Mitsuya Shibata
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:20
|
|
|
152.
|
|
|
There are a lot of different ways to find things to work on. It might be a bug report you are encountering yourself (which gives you a good opportunity to test the fix), or a problem you noted elsewhere, maybe in a bug report.
|
|
|
|
|
問題を見つける方法はいくつか存在します。それはあなた自身が遭遇した不具合かもしれませんし（その場合、修正点に対してテストを行う良い機械でしょう）、どこか別の場所で発生した問題をバグレポートの中から見つけるということもあります。
|
|
Translated and reviewed by
Kentaro Kazuhama
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:22
|
|
|
153.
|
|
|
Take a look at `the bitesize bugs`_ in Launchpad, and that might give you an idea of something to work on. It might also interest you to look at the bugs `triaged`_ by the Ubuntu One Hundred Papercuts team.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:26
|
|
|
154.
|
|
|
Figuring out what to fix
|
|
|
|
|
何を修正するか理解する
|
|
Translated by
Shushi Kurose
|
|
Reviewed by
Mitsuya Shibata
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:35
|
|
|
155.
|
|
|
If you don't know the source package containing the code that has the problem, but you do know the path to the affected program on your system, you can discover the source package that you'll need to work on.
|
|
|
|
|
コンピューター上で問題のあるプログラムのパスが分かっているのに問題のあるコードを含んだソースパッケージがわからない場合、作業を行う必要のあるソースパッケージを探し出すことができます。
|
|
Translated by
Shushi Kurose
|
|
Reviewed by
Mitsuya Shibata
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:37
|
|
|
156.
|
|
|
Let's say you've found a bug in Bumprace, a racing game. The Bumprace application can be started by running ``/usr/bin/bumprace`` on the command line. To find the binary package containing this application, use this command::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:41
|
|
|
157.
|
|
|
This would print out::
|
|
|
|
|
このように出力されます::
|
|
Translated by
Shushi Kurose
|
|
Reviewed by
Mitsuya Shibata
|
|
|
|
Located in
../ubuntu-packaging-guide/fixing-a-bug.rst:47
|
