Browsing Japanese translation

Don't show this notice anymore
Before translating, be sure to go through Ubuntu Translators instructions and Japanese guidelines.
110 of 115 results
For the Ubuntu ``hello`` package, the ``control`` file looks something like this:
(no translation yet)
Located in ../ubuntu-packaging-guide/debian-dir-overview.rst:75
When a source package is producing multiple binary packages ``dh`` will install the files into ``debian/tmp`` rather than directly into ``debian/<package>``. Files installed into ``debian/tmp`` can then be moved into separate binary packages using multiple ``$package_name.install`` files. This is often done to split large amounts of architecture independent data out of architecture dependent packages and into ``Architecture: all`` packages. In this case, only the name of the files (or directories) to be installed are needed without the installation directory. For example, ``foo.install`` containing only the architecture dependent files might look like::
(no translation yet)
Located in ../ubuntu-packaging-guide/debian-dir-overview.rst:268
``1.0`` for packages wishing to explicitly declare the default format
(no translation yet)
Located in ../ubuntu-packaging-guide/debian-dir-overview.rst:346
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.
(no translation yet)
Located in ../ubuntu-packaging-guide/fixing-a-bug.rst:8
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.
(no translation yet)
Located in ../ubuntu-packaging-guide/fixing-a-bug.rst:13
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.
(no translation yet)
Located in ../ubuntu-packaging-guide/fixing-a-bug.rst:22
`Harvest <>`_ is where we keep track of various TODO lists regarding Ubuntu development. It lists bugs that were fixed upstream or in Debian already, lists small bugs (we call them 'bitesize'), and so on. Check it out and find your first bug to work on.
(no translation yet)
Located in ../ubuntu-packaging-guide/fixing-a-bug.rst:26
Note that the part preceding the colon is the binary package name. It's often the case that the source package and binary package will have different names. This is most common when a single source package is used to build multiple different binary packages. To find the source package for a particular binary package, type::
(no translation yet)
Located in ../ubuntu-packaging-guide/fixing-a-bug.rst:52
We'll describe specifics on how to branch the code, push your fix, and request a review in the following sections.
(no translation yet)
Located in ../ubuntu-packaging-guide/fixing-a-bug.rst:83
There are entire books written about finding bugs, fixing them, testing them, etc. If you are completely new to programming, try to fix easy bugs such as obvious typos first. Try to keep changes as minimal as possible and document your change and assumptions clearly.
(no translation yet)
Located in ../ubuntu-packaging-guide/fixing-a-bug.rst:91
110 of 115 results

This translation is managed by Ubuntu Japanese Translators, assigned by Ubuntu Translators.

You are not logged in. Please log in to work on translations.

Contributors to this translation: Daniel Holbach, Kenichi Ito, Kentaro Kazuhama, Mitsuya Shibata, OKANO Takayoshi, Shushi Kurose, Yoshikazu Nojima.