<!-- if you are translating this document, please notate the CVS
revision of the developers reference here -->
<!--
<!-- if you are translating this document, please notate the CVS
revision of the developers reference here -->
<!--
may want to subscribe to &email-debian-vote;.
<p>
The list of all the proposals (past and current) is available on the
may want to subscribe to &email-debian-vote;.
<p>
The list of all the proposals (past and current) is available on the
<p>
&email-debian-private; is a special mailing list for private
discussions amongst Debian developers. It is meant to be used for
<p>
&email-debian-private; is a special mailing list for private
discussions amongst Debian developers. It is meant to be used for
As such, it is a low volume list, and users are urged not to use
&email-debian-private; unless it is really necessary. Moreover, do
<em>not</em> forward email from that list to anyone. Archives of this
As such, it is a low volume list, and users are urged not to use
&email-debian-private; unless it is really necessary. Moreover, do
<em>not</em> forward email from that list to anyone. Archives of this
<em>#debian-bugs</em> is used for coordinating bug squash parties.
<em>#debian-boot</em> is used to coordinate the work on the boot
floppies (i.e. the installer). <em>#debian-doc</em> is
<em>#debian-bugs</em> is used for coordinating bug squash parties.
<em>#debian-boot</em> is used to coordinate the work on the boot
floppies (i.e. the installer). <em>#debian-doc</em> is
-Some non-english channels exist, for example <em>#debian-devel-fr</em> for
-french speaking people interested in Debian's development.
+Some non-English channels exist, for example <em>#debian-devel-fr</em> for
+French speaking people interested in Debian's development.
<sect1 id="servers-cvs">The CVS server
<p>
<tt>cvs.debian.org</tt> is also known as <tt>klecker.debian.org</tt>,
<sect1 id="servers-cvs">The CVS server
<p>
<tt>cvs.debian.org</tt> is also known as <tt>klecker.debian.org</tt>,
server, for instance, to help coordinate work on a package between
many different developers, you can request a CVS area on the server.
<p>
server, for instance, to help coordinate work on a package between
many different developers, you can request a CVS area on the server.
<p>
ships for the <em>i386</em>, <em>m68k</em>, <em>alpha</em>, and
<em>sparc</em> architectures. Debian 2.2 added support for the
<em>powerpc</em> and <em>arm</em> architectures. Debian 3.0 adds
ships for the <em>i386</em>, <em>m68k</em>, <em>alpha</em>, and
<em>sparc</em> architectures. Debian 2.2 added support for the
<em>powerpc</em> and <em>arm</em> architectures. Debian 3.0 adds
<em>s390</em>, <em>mips</em> and <em>mipsel</em>.
<p>
Information for developers or uses about the specific ports are
<em>s390</em>, <em>mips</em> and <em>mipsel</em>.
<p>
Information for developers or uses about the specific ports are
<p>
Once the package is accepted the system sends a confirmation
mail to the maintainer, closes all the bugs marked as fixed by the upload
<p>
Once the package is accepted the system sends a confirmation
mail to the maintainer, closes all the bugs marked as fixed by the upload
accessible at <url id="&url-incoming;"> (there is no
such URL for packages in the non-US archive) until it is really installed
in the Debian archive. This happens only once a day, the package
accessible at <url id="&url-incoming;"> (there is no
such URL for packages in the non-US archive) until it is really installed
in the Debian archive. This happens only once a day, the package
<sect1 id="delayed-incoming">Delayed incoming
<p>
The <file>unchecked</file> directory has a special <file>DELAYED</file>
<sect1 id="delayed-incoming">Delayed incoming
<p>
The <file>unchecked</file> directory has a special <file>DELAYED</file>
called <file>1-day</file> to <file>9-day</file>. Packages which are uploaded in
one of those directories will be moved in the real unchecked
directory after the corresponding number of days.
called <file>1-day</file> to <file>9-day</file>. Packages which are uploaded in
one of those directories will be moved in the real unchecked
directory after the corresponding number of days.
the <em>testing</em> distribution, but they do so in an intelligent manner
trying to avoid any inconsistency and trying to use only
non-buggy packages.
the <em>testing</em> distribution, but they do so in an intelligent manner
trying to avoid any inconsistency and trying to use only
non-buggy packages.
is 10 days for low urgency, 5 days for medium urgency and 2 days for high
urgency. Those delays may be doubled during a freeze;
<item>
is 10 days for low urgency, 5 days for medium urgency and 2 days for high
urgency. Those delays may be doubled during a freeze;
<item>
Tells you the keywords that you are accepting. Each mail sent through
the Package Tracking System is associated to a keyword and you receive
only the mails associated to keywords that you are accepting. Here is
Tells you the keywords that you are accepting. Each mail sent through
the Package Tracking System is associated to a keyword and you receive
only the mails associated to keywords that you are accepting. Here is
- <item><tt>bts</tt> : mails coming from the Debian Bug Tracking System
- <item><tt>bts-control</tt> : reply to mails sent to
+ <item><tt>bts</tt>: mails coming from the Debian Bug Tracking System
+ <item><tt>bts-control</tt>: reply to mails sent to
- <item><tt>summary</tt> : automatic summary mails about the state of a package
- <item><tt>cvs</tt> : notification of cvs commits
- <item><tt>upload-source</tt> : announce of a new source upload that
+ <item><tt>summary</tt>: automatic summary mails about the state of a package
+ <item><tt>cvs</tt>: notification of CVS commits
+ <item><tt>upload-source</tt>: announce of a new source upload that
- <item><tt>upload-binary</tt> : announce of a new binary-only upload (porting)
- <item><tt>katie-other</tt> : other mails from ftpmasters
+ <item><tt>upload-binary</tt>: announce of a new binary-only upload (porting)
+ <item><tt>katie-other</tt>: other mails from ftpmasters
your Debian package you may want to forward the commit notification
to the PTS so that the subscribers (possible co-maintainers) can
closely follow the package's evolution.
<p>
your Debian package you may want to forward the commit notification
to the PTS so that the subscribers (possible co-maintainers) can
closely follow the package's evolution.
<p>
notifications, you just have to make sure it sends a copy of those mails
to <tt><var>srcpackage</var>_cvs@&pts-host;</tt>. Only people who
accepts the <em>cvs</em> keyword will receive the notifications.
notifications, you just have to make sure it sends a copy of those mails
to <tt><var>srcpackage</var>_cvs@&pts-host;</tt>. Only people who
accepts the <em>cvs</em> keyword will receive the notifications.
to <tt>ftp-master</tt>. Instead, upload the package to
<ftpsite>non-us.debian.org</ftpsite>, placing the files in
&non-us-upload-dir; (again, both <ref id="dupload"> and <ref
to <tt>ftp-master</tt>. Instead, upload the package to
<ftpsite>non-us.debian.org</ftpsite>, placing the files in
&non-us-upload-dir; (again, both <ref id="dupload"> and <ref
you can use the same account/password that works on
<tt>ftp-master</tt>. If you use anonymous FTP to upload, place the
files into &upload-queue;.
you can use the same account/password that works on
<tt>ftp-master</tt>. If you use anonymous FTP to upload, place the
files into &upload-queue;.
<p>
Bug fixes to unstable by non-maintainers are also acceptable, but only
as a last resort or with permission. The following protocol should
<p>
Bug fixes to unstable by non-maintainers are also acceptable, but only
as a last resort or with permission. The following protocol should
which simply check out and attempt to auto-build packages which need
to be ported. There is also an email interface to the system, which
allows porters to ``check out'' a source package (usually one which
which simply check out and attempt to auto-build packages which need
to be ported. There is also an email interface to the system, which
allows porters to ``check out'' a source package (usually one which
<p>
<package>buildd</package> is not yet available as a package; however,
most porting efforts are either using it currently or planning to use
<p>
<package>buildd</package> is not yet available as a package; however,
most porting efforts are either using it currently or planning to use
<tt>Maintainer:</tt> field, although it can take a few hours after the
upload is done. If you do not expect to upload a new version for a while,
you can use <ref id="pkg-tracking-system"> to get the bug reports. However,
<tt>Maintainer:</tt> field, although it can take a few hours after the
upload is done. If you do not expect to upload a new version for a while,
you can use <ref id="pkg-tracking-system"> to get the bug reports. However,
to the good documentation and so on). If the same report comes up
again and again you may ask yourself if the documentation is good
enough or if the program shouldn't detect its misuse in order to
to the good documentation and so on). If the same report comes up
again and again you may ask yourself if the documentation is good
enough or if the program shouldn't detect its misuse in order to
to be brought to the upstream author.
<p>
If the bug submitter disagree with your decision to close the bug,
he may reopen it until you find an agreement on how to handle it.
If you don't find any, you may want to tag the bug <tt>wontfix</tt>
to let people know that the bug exists but that it won't be corrected.
to be brought to the upstream author.
<p>
If the bug submitter disagree with your decision to close the bug,
he may reopen it until you find an agreement on how to handle it.
If you don't find any, you may want to tag the bug <tt>wontfix</tt>
to let people know that the bug exists but that it won't be corrected.
require a decision of the technical committee by reassigning the bug
to <package>tech-ctte</package> (you may use the clone command of
the BTS if you wish to keep it reported against your package).
require a decision of the technical committee by reassigning the bug
to <package>tech-ctte</package> (you may use the clone command of
the BTS if you wish to keep it reported against your package).
the <file>changelog</file>). This is particularly useful if you
are several developers working on the same package.
<item>
the <file>changelog</file>). This is particularly useful if you
are several developers working on the same package.
<item>
distribution, you can close the bug. This can be done automatically,
read <ref id="upload-bugfix">.
</enumlist>
distribution, you can close the bug. This can be done automatically,
read <ref id="upload-bugfix">.
</enumlist>
<file>debian/patches</file> directory and to apply them on the fly at
build time. The package <package>dbs</package> provides an
implementation of such a system, you just have to build-depend on dbs to
<file>debian/patches</file> directory and to apply them on the fly at
build time. The package <package>dbs</package> provides an
implementation of such a system, you just have to build-depend on dbs to
<package>hello-dbs</package> is a simple example that demonstrates how to
use <package>dbs</package>.
<p>
<package>hello-dbs</package> is a simple example that demonstrates how to
use <package>dbs</package>.
<p>
to provide several flavors of the same software (examples are the
vim-* packages) or to make several small packages instead of a big one
(it's interesting if the user doesn't need all the packages and can thus
to provide several flavors of the same software (examples are the
vim-* packages) or to make several small packages instead of a big one
(it's interesting if the user doesn't need all the packages and can thus
<p>
The second case can be easily managed by <prgn>dh_install</prgn> (from
<package>debhelper</package>) to move files from the build directory to
<p>
The second case can be easily managed by <prgn>dh_install</prgn> (from
<package>debhelper</package>) to move files from the build directory to
-Several subsets of packages have special subpolicies and corresponding
-packaging rules and practices :
+Several subsets of packages have special sub-policies and corresponding
+packaging rules and practices:
<package>libdbd-pg-perl</package> (binary perl module) or
<package>libmldbm-perl</package> (arch independent perl module).
<item>
<package>libdbd-pg-perl</package> (binary perl module) or
<package>libmldbm-perl</package> (arch independent perl module).
<item>
&file-python-policy; (in the python package).
<item>
Emacs related packages have the <url id="&url-emacs-policy;"
&file-python-policy; (in the python package).
<item>
Emacs related packages have the <url id="&url-emacs-policy;"
-Ocaml related packages have their ocaml policy : &file-ocaml-policy; (in
-the ocaml package). A good example is the <package>camlzip</package>
+Ocaml related packages have their ocaml policy: &file-ocaml-policy; (in
+the <package>ocaml</package> package). A good example is the <package>camlzip</package>
non-interactive installations in the future.
<p>
Debconf is a great tool but it is often badly used ... many common mistakes
non-interactive installations in the future.
<p>
Debconf is a great tool but it is often badly used ... many common mistakes
<p>
For example, apart from the usual description that you adapt from the
upstream <file>README</file>, you should include the URL of the
<p>
For example, apart from the usual description that you adapt from the
upstream <file>README</file>, you should include the URL of the
by the author, you may also want to warn the user that the
package is not ready for production use.
<p>
Last but not least, since the first user impression is based on
by the author, you may also want to warn the user that the
package is not ready for production use.
<p>
Last but not least, since the first user impression is based on
New maintainers usually have certain difficulties creating Debian packages
— this is quite understandable. That is why the sponsor is there, to check
the package and verify that it is good enough for inclusion in Debian.
New maintainers usually have certain difficulties creating Debian packages
— this is quite understandable. That is why the sponsor is there, to check
the package and verify that it is good enough for inclusion in Debian.