<!-- common, language independant entities -->
<!entity % commondata SYSTEM "common.ent" > %commondata;
<!-- CVS revision of this document -->
- <!entity cvs-rev "$Revision: 1.40 $">
+ <!entity cvs-rev "$Revision: 1.41 $">
<!-- if you are translating this document, please notate the RCS
revision of the developers reference here -->
The resources discussed in this reference include the mailing lists
and servers (<ref id="servers">); a discussion of the structure of the
Debian archive (<ref id="archive">); explanation of the different
-servers which accept package uploads (<ref id="upload-master">); and a
+servers which accept package uploads (<ref id="upload-ftp-master">); and a
discussion of resources which can help maintainers with the quality of
their packages (<ref id="tools">).
<p>
maintainers before we can give them accounts on our servers and
letting them upload packages.
<p>
-Registration requires that the following information be sent to
-&email-new-maintainer; as part of the registration application:
+Registration requires that the following information be sent in
+appropriate steps described at <url id="&url-newmaint-checklist;"
+ name="Checklist for applicants">
+after the initial contact to &email-new-maintainer:
+
<list>
<item>
Your name.
available on public key servers, send a message to
&email-new-maintainer; to register as an offical Debian developer so
that you will be able to upload your packages. This message must
-contain all the information discussed above. The message must also
-contain your public key (extracted using <tt>gpg --armor --export
-<var>user_id</var></tt> in the case of <prgn>gpg</prgn>) for the
-database of keys which is distributed from
-<url id="&url-debian-keyring;"> and the <package>debian-keyring</package>
-package. Please be sure to sign your request message with your chosen
-public key.
+contain your name and your valid e-mail address. All the information
+discussed above is required after your Application Manager is
+assigned. Application Manager is your agent in the registration
+process, and you can always ask him about the status of your
+application. You can check the <url id="&url-newmaint-db;"
+name="Application StatusBoard"> as well.
+ <p>
+For more details, please consult <url id="&url-newmaint;" name="New
+Maintainer's Corner"> at the Debian web site.
<p>
Once this information is received and processed, you should be
contacted with information about your new Debian maintainer account.
Read the documentation that comes with your software; read the <url
id="&url-pgp-faq;" name="PGP FAQ">.
<p>
-If you add or remove signatures from your public key, or add or remove
-user identities, you need to update the key servers and mail your
-public key to &email-debian-keyring;. The same key extraction
-routines discussed in <ref id="registering"> apply.
+If you add signatures to your public key, or add user identities, you
+can update the debian keyring by sending your key to the key server at
+<tt>&keyserver-host;</tt>. If you need to add a completely new key,
+or remove an old key, send mail to &email-debian-keyring;. The same
+key extraction routines discussed in <ref id="registering"> apply.
<p>
You can find a more in-depth discussion of Debian key maintenance in
the documentation for the <package>debian-keyring</package> package.
&email-debian-policy;, &email-debian-user;, &email-debian-private;,
&email-debian-announce;, and &email-debian-devel-announce;. All
developers are expected to be subscribed to at least
-&email-debian-private and &email-debian-devel-announce;. There are
+&email-debian-private; and &email-debian-devel-announce;. There are
other mailing lists are available for a variety of special topics; see
<url id="&url-debian-lists-subscribe;"> for a list. Cross-posting
(sending the same message to multiple lists) is discouraged.
posting messages.
<p>
Online archives of mailing lists are available at <url
-id="&url-debian-list-archives;">.
+id="&url-lists-archives;">.
<sect id="server-machines">Debian servers
<p>
If you have a problem with the operation of Debian server, and you
think that the system operators need to be notified of this problem,
-please find the contact address for the particular role at <url
-id="&url-debian-contacts;">. If you have a non-operating problems
+please find the contact address for the particular machine at <url
+id="&url-devel-machines;">. If you have a non-operating problems
(such as packages to be remove, suggestions for the web site, etc.),
generally you'll report a bug against a ``pseudo-package''. See <ref
id="submit-bug"> for information on how to submit bugs.
<sect1 id="servers-master">The master server
<p>
-The master server, <tt>master.debian.org</tt>, holds the canonical copy
-of the Debian archive (excluding the non-U.S. packages). Generally,
-package uploads go to this server; see <ref id="upload">.
- <p>
<tt>master.debian.org</tt> is the canonical location for the Bug
Tracking System (BTS). If you plan on doing some statistical analysis
or processing of Debian bugs, this would be the place to do it.
<p>
If you find a problem with <tt>master.debian.org</tt> such as disk
full, suspicious activity, or whatever, send an email to
-&email-debian-admin;. Problems with the Debian FTP archive generally
-need to be reported as bugs against the
-<package>ftp.debian.org</package> pseudo-package or an email to
-&email-ftpmaster;, but also see the procedures in <ref
-id="archive-manip">.
+&email-debian-admin;.
+
+ <sect1 id="servers-ftp-master">The ftp-master server
+ <p>
+The ftp-master server, <tt>ftp-master.debian.org</tt> (or
+<tt>auric.debian.org</tt>), holds the canonical copy of the Debian
+archive (excluding the non-U.S. packages). Generally, package uploads
+go to this server; see <ref id="upload">.
+ <p>
+Problems with the Debian FTP archive generally need to be reported as
+bugs against the <package>ftp.debian.org</package> pseudo-package or
+an email to &email-ftpmaster;, but also see the procedures in
+<ref id="archive-manip">.
- <sect1 id="servers-www">The WWW servers
+ <sect1 id="servers-www">The WWW server
<p>
The main web server, <tt>www.debian.org</tt>, is also known as
<tt>va.debian.org</tt>. All developers are given accounts on this
If you have some Debian-specific information which you want to serve
up on the web, you can do do this by putting material in the
<file>public_html</file> directory under your home directory. You can
-do this on either <tt>va.debian.org</tt> or
-<tt>master.debian.org</tt>. Any material you put in those areas are
-accessible via the URLs
-<tt>http://www.debian.org/~<var>user-id</var>/</tt> and
-<tt>http://master.debian.org/~<var>user-id</var>/</tt>, respectively.
-Generally, you'll want to use <tt>va</tt>, for the
-<tt>www.debian.org</tt> address, although in some cases you may need
-to put it on <tt>master</tt>. Please do not put any material on
-Debian servers not relating to Debian, unless you have prior
-permission. Send mail to &email-debian-devel; if you have any
-questions.
+do this on <tt>va.debian.org</tt>. Any material you put in those areas
+are accessible via the URL
+<tt>http://www.debian.org/~<var>user-id</var>/</tt>.
+If necessary, you can use other Debian machines for this; the procedure
+is analogous to the above. Please do not put any material on Debian
+servers not relating to Debian, unless you have prior permission.
+Send mail to &email-debian-devel; if you have any questions.
<p>
If you find a problem with the Debian web server, you should generally
submit a bug against the pseudo-package,
<package>www.debian.org</package>. First check whether or not someone
-else has already reported the problem on the <url
-id="&url-bts;db/pa/lwww.debian.org.html" name="Bug Tracking System">.
+else has already reported the problem on the
+<url id="http://bugs.debian.org/www.debian.org" name="Bug Tracking System">.
<sect1 id="servers-cvs">The CVS server
Note that mirrors are generally run by third-parties who are
interested in helping Debian. As such, developers generally do not
have accounts on these machines.
- <p>
-Please do not mirror off of <tt>master.debian.org</tt>. This host
-already has too much load. Check the sites above for information, or
-email <email>debian-devel@lists.debian.org</email>.
<sect id="other-machines">Other Debian Machines
<p>
If you want to create a new package for the Debian distribution, you
should first check the <url id="&url-wnpp;" name="Work-Needing and
-Prospective Packages (WNPP)"> list. Checking the WNPP ensures that no
-one is already working on packaging that software, and that effort is
+Prospective Packages (WNPP)"> list. Checking the WNPP list ensures that
+no one is already working on packaging that software, and that effort is
not duplicated. Read the <url id="&url-wnpp;" name="WNPP web pages"> for
more information.
<p>
-There are a number of reasons why we ask maintainers to follow these
-steps:
+There are a number of reasons why we ask maintainers to announce their
+intentions:
<list compact>
<item>
It helps the (potentially new) maintainer to tap into the experience
on it already.
<item>
It lets other people thinking about working on the package know that
-there already is a volunteer, and efforts may be shared. The ``intent
-to package'' message to &email-debian-devel@; will be picked up the
-the WNPP maintainer, and your intention will be published in
-subsequent versions of the WNPP document.
+there already is a volunteer, and efforts may be shared.
<item>
It lets the rest of the maintainers know more about the package than
-the one line description and the changelog entry ``Initial version''
-that generally gets posted to <tt>debian-devel-changes</tt> by
-default.
+the one line description and the usual changelog entry ``Initial release''
+that gets posted to <tt>debian-devel-changes</tt>.
<item>
It is helpful to the people who live off unstable (and form our first
line of testers); we should encourage these people.
</list>
- <sect1 id="upload-master">Uploading to <tt>master</tt>
+ <sect1 id="upload-ftp-master">Uploading to <tt>ftp-master</tt>
<p>
To upload a package, you need a personal account on
-<ftpsite>master.debian.org</ftpsite>. All maintainers should already
-have this account, see <ref id="servers-master">. You can use either
-<prgn>scp</prgn> or <prgn>ftp</prgn> to transfer the files. In either
-case, the files need to be placed into
-<ftppath>&master-upload-dir</ftppath>. (You cannot upload to Incoming
-on master using anonymous FTP -- you must use your user-name and
-password.)
+<ftpsite>ftp-master.debian.org</ftpsite>, which you should have as an
+official maintainer. If you use <prgn>scp</prgn> or <prgn>rsync</prgn>
+to transfer the files, place them into <ftppath>&us-upload-dir;</ftppath>;
+if you use anonymous FTP to upload, place them into
+<ftppath>/pub/UploadQueue/</ftppath>.
<p>
<em>Note:</em> Do not upload packages containing software that is
-export-controlled by the United States government to <tt>master</tt>,
+export-controlled by the United States government to <tt>ftp-master</tt>,
nor to the overseas upload queues on <tt>chiark</tt> or
<tt>erlangen</tt>. This prohibition covers almost all cryptographic
software, and even sometimes software that contains ``hooks'' to
<p>
You may also find the Debian package <package>dupload</package> useful
when uploading packages. This handy program is distributed with
-defaults for uploading via <prgn>ftp</prgn> to <tt>master</tt>,
+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
-use <prgn>ssh</prgn>. See <manref name="dupload" section="1"> and
-<manref name="dupload" section="5"> for more information.
+use <prgn>ssh</prgn> or <prgn>rsync</prgn>. See <manref name="dupload"
+section="1"> and <manref name="dupload" section="5"> for more information.
<p>
After uploading your package, you can check how dinstall will
process it by running dinstall on your changes file:
-<example>~maor/dinstall/dinstall -n foo.changes</example>
+<example>/org/ftp.debian.org/scripts/dinstall/dinstall -n foo.changes</example>
- <sect1 id="upload-non-us">Uploading to <tt>pandora</tt> (non-us)
+ <sect1 id="upload-non-us">Uploading to <tt>non-us</tt> (pandora)
<p>
As discussed above, export controlled software should not be uploaded
-to <tt>master</tt>. Instead, use non-anonymous FTP or
-<prgn>scp</prgn> to copy the package to
-<ftpsite>pandora.debian.org</ftpsite>, placing the files in
-<ftppath>&non-us-upload-dir</ftppath>. By default, you can use your
-same account which works on <tt>master</tt>.
+to <tt>ftp-master</tt>. Instead, use <prgn>scp</prgn> or non-anonymous
+FTP to copy the package to <ftpsite>non-us.debian.org</ftpsite>, placing
+the files in <ftppath>&non-us-upload-dir;</ftppath>. By default, you can
+use the same account/password that works on <tt>ftp-master</tt>.
<p>
The program <prgn>dupload</prgn> comes with support for uploading to
-<tt>pandora</tt>; please refer to the documentation that comes with
+<tt>non-us</tt>; please refer to the documentation that comes with
the program for details.
<p>
-Just as for an upload to master, you can check your upload with :
-<example>/org/non-us.debian.org/scripts/dinstall/dinstall -n foo.changes
+Similar to the way it's done on <tt>ftp-master</tt>, you can check your
+upload with:
+<example>
+/org/non-us.debian.org/scripts/dinstall/dinstall -n foo.changes
</example>
<sect1>Uploads via <tt>chiark</tt>
<p>
-If you have a slow network connection to <tt>master</tt>, there are
+If you have a slow network connection to <tt>ftp-master</tt>, there are
alternatives. One is to upload files to <tt>Incoming</tt> via a
upload queue in Europe on <tt>chiark</tt>. For details connect to
<url id="&url-chiark-readme;">.
<p>
<em>Note:</em> Do not upload packages containing software that is
export-controlled by the United States government to the queue on
-<tt>chiark</tt>. Since this upload queue goes to <tt>master</tt>, the
-prescription found in <ref id="upload-master"> applies here as well.
+<tt>chiark</tt>. Since this upload queue goes to <tt>ftp-master</tt>, the
+prescription found in <ref id="upload-ftp-master"> applies here as well.
<p>
The program <prgn>dupload</prgn> comes with support for uploading to
<tt>chiark</tt>; please refer to the documentation that comes with the
via anonymous FTP to <url id="&url-upload-erlangen;">.
<p>
The upload must be a complete Debian upload, as you would put it into
-<tt>master</tt>'s <tt>Incoming</tt>, i.e., a <tt>.changes</tt> files
+<tt>ftp-master</tt>'s <tt>Incoming</tt>, i.e., a <tt>.changes</tt> files
along with the other files mentioned in the <tt>.changes</tt>. The
queue daemon also checks that the <tt>.changes</tt> is correctly
PGP-signed by a Debian developer, so that no bogus files can find
-their way to <tt>master</tt> via the queue. Please also make sure that
+their way to <tt>ftp-master</tt> via the queue. Please also make sure that
the <tt>Maintainer</tt> field in the <tt>.changes</tt> contains
<em>your</em> e-mail address. The address found there is used for all
-replies, just as on <tt>master</tt>.
+replies, just as on <tt>ftp-master</tt>.
<p>
There's no need to move your files into a second directory after the
upload as on <tt>chiark</tt>. And, in any case, you should get some
mail reply from the queue daemon what happened to your
-upload. Hopefully it should have been moved to <tt>master</tt>, but in
+upload. Hopefully it should have been moved to <tt>ftp-master</tt>, but in
case of errors you're notified, too.
<p>
<em>Note:</em> Do not upload packages containing software that is
export-controlled by the United States government to the queue on
-<tt>erlangen</tt>. Since this upload queue goes to <tt>master</tt>, the
-prescription found in <ref id="upload-master"> applies here as well.
+<tt>erlangen</tt>. Since this upload queue goes to <tt>ftp-master</tt>, the
+prescription found in <ref id="upload-ftp-master"> applies here as well.
<p>
The program <prgn>dupload</prgn> comes with support for uploading to
<tt>erlangen</tt>; please refer to the documentation that comes with
<sect1>Other Upload Queues
<p>
Another upload queue is available which is based in the US, and is a
-good backup when there are problems reaching <tt>master</tt>. You can
+good backup when there are problems reaching <tt>ftp-master</tt>. You can
upload files, just as in <tt>erlangen</tt>, to <url
id="&url-upload-samosa;">.
<p>
~ianmdlvl / developers-reference.git / blobdiff