<!-- common, language independant entities -->
<!entity % commondata SYSTEM "common.ent" > %commondata;
<!-- CVS revision of this document -->
- <!entity cvs-rev "$Revision: 1.87 $">
+ <!entity cvs-rev "$Revision: 1.88 $">
<!-- if you are translating this document, please notate the RCS
revision of the developers reference here -->
Changes that you make to the package need to be recorded in the
<file>debian/changelog</file>. These changes should provide a concise
description of what was changed, why (if it's in doubt), and note if
-any bugs were closed. They also record when the packages was
+any bugs were closed. They also record when the package was
completed. This file will be installed in
<file>/usr/share/doc/<var>package</var>/changelog.Debian.gz</file>, or
<file>/usr/share/doc/<var>package</var>/changelog.gz</file> for native
The <file>debian/changelog</file> file conform to a certain structure,
with a number of different fields. One field of note, the
<em>distribution</em>, is described in <ref id="upload-dist">. More
-information about the structure structure of this file can be found in
+information about the structure of this file can be found in
the Debian Policy section titled "<file>debian/changelog</file>".
<p>
Changelog entries can be used to automatically close Debian bugs when
the package is installed into the archive. See <ref
id="upload-bugfix">.
<p>
-It is conventional that the changelog entry notating that the package
+It is conventional that the changelog entry notating of a package that
contains a new upstream version of the software looks like this:
<example>
* new upstream version
<p>
<em>Note:</em> Do not upload to <tt>ftp-master</tt> packages
containing software that is patent-restricted by the United States
-government, any cryptographic packages which belong in
+government, nor any cryptographic packages which belong to
<em>contrib</em> or <em>non-free</em>. If you can't upload it to
<tt>ftp-master</tt>, then neither can you upload it to the overseas
upload queues on <tt>chiark</tt> or <tt>erlangen</tt>. Uploads of
<package>dput</package> useful
when uploading packages. These handy program are distributed with
defaults for uploading via <prgn>ftp</prgn> to <tt>ftp-master</tt>,
-<tt>chiark</tt>, and <tt>erlangen</tt>. It can also be configured to
+<tt>chiark</tt>, and <tt>erlangen</tt>. They can also be configured to
use <prgn>ssh</prgn> or <prgn>rsync</prgn>. See <manref name="dupload"
section="1">, <manref name="dupload" section="5"> and <manref name="dput"
section="1"> for more information.
outside the U.S. Therefore, any cryptographic software which belongs
in the <em>main</em> section of the Debian archive and does not depend
on any package outside of <em>main</em> (e.g., does not depend on
-anything in <em>non-US/main</em>) can be uploaded to ftp-master or its
-queues, described above.
+anything in <em>non-US/main</em>) can be uploaded to <tt>ftp-master</tt>
+or its queues, described above.
<p>
Debian policy does not prevent upload to non-US by U.S. residents or
citizens, but care should be taken in doing so. It is recommended that
<p>
<package>yada</package> is another packaging helper tool. It uses a
<file>debian/packages</file> file to auto-generate
-<file>debian/rules</file> other necessary files in the
+<file>debian/rules</file> and other necessary files in the
<file>debian/</file> subdirectory.
<p>
Note that <package>yada</package> is called "essentially unmaintained"
By "base system", we mean the bare minimum of packages required to
operate and install the rest of the system.
<p>
-Having a system link this can be useful in many ways. For instance,
+Having a system like this can be useful in many ways. For instance,
you can <prgn>chroot</prgn> into it if you want to test your build
depends. Or, you can test how your package behaves when installed
into a bare base system.
~ianmdlvl / developers-reference.git / blobdiff