In this chapter you will find a very brief road map of the Debian mailing lists, the main Debian servers, and other Debian machines which may be available to you as a developer.
The mailing list server is at lists.debian.org. Mail
debian-foo-REQUEST@lists.debian.org, where
debian-foo is the name of the list, with the word
subscribe in the Subject to subscribe to the list or
unsubscribe to unsubscribe. More detailed instructions on how to
subscribe and unsubscribe to the mailing lists can be found at http://www.debian.org/MailingLists/subscribe
,
ftp://ftp.debian.org/debian/doc/mailing-lists.txt
or locally in /usr/doc/debian/mailing-lists.txt
if you have the
doc-debian
package installed.
When replying to messages on the mailing list, please do not send a carbon copy (CC) to the original poster unless they explicitly request to be copied. Anyone who posts to a mailing list should read it to see the responses.
The following are the core Debian mailing lists: debian-devel@lists.debian.org
,
debian-policy@lists.debian.org
,
debian-policy@lists.debian.org
,
debian-private@lists.debian.org
,
debian-announce@lists.debian.org
,
and debian-devel-announce@lists.debian.org
.
All developers are expected to be subscribed to at least debian-private@lists.debian.org
and debian-devel-announce@lists.debian.org
.
There are other mailing lists are available for a variety of special topics;
see http://www.debian.org/MailingLists/subscribe
for a list. Cross-posting (sending the same message to multiple lists) is
discouraged.
debian-private@lists.debian.org
is a special mailing lists for private discussions amongst Debian developers.
It is meant to be used for posts which for whatever reason should not be
published publically. As such, it is a low volume list, and users are urged
not to use debian-private@lists.debian.org
unless it is really necessary. Moreover, do not forward email from
that list to anyone.
debian-email@lists.debian.org
is a special mailing list used as a grab-bag for Debian related correspondence
such as contacting upstream authors about licenses, bugs, etc. or discussing
the project with others where it might be useful to have the discussion
archived somewhere.
As ever on the net, please trim down the quoting of articles you're replying to. In general, please adhere to the usual conventions for posting messages.
Online archives of mailing lists are available at http://www.debian.org/Lists-Archives/
.
Debian servers are well known servers which serve critical functions in the Debian project. Every developer should know what these servers are and what they do.
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 http://www.debian.org/devel/maintainer_contacts
.
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 Submitting
Bugs, Section 10.2 for information on how to submit bugs.
The master server, master.debian.org, holds the canonical copy of the Debian archive (excluding the non-U.S. packages). Generally, package uploads go to this server; see Package uploads, Chapter 6.
master.debian.org 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. Please describe your plans on
debian-devel@lists.debian.org
before implementing anything, however, to reduce unnecessary duplication of
effort or wasted processing time.
All Debian developers have accounts on master.debian.org. Please take care to protect your password to this machine. Try to avoid login or upload methods which send passwords over the Internet in the clear.
If you find a problem with master.debian.org such as disk full,
suspicious activity, or whatever, send an email to debian-admin@debian.org
.
Problems with the Debian FTP archive generally need to be reported as bugs
against the ftp.debian.org
pseudo-package or an email to ftpmaster@debian.org
, but also
see the procedures in Moving, Removing,
Renaming, Adopting, and Orphaning Packages, Chapter 9.
The main web server, www.debian.org, is also known as va.debian.org. All developers are given accounts on this machine.
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 public_html
directory under your home directory. You can do this on either
va.debian.org or master.debian.org. Any material you
put in those areas are accessible via the URLs
http://www.debian.org/~user-id/ and
http://master.debian.org/~user-id/, respectively.
Generally, you'll want to use va, for the
www.debian.org address, although in some cases you may need to put
it on master. Please do not put any material on Debian servers
not relating to Debian, unless you have prior permission. Send mail to
debian-devel@lists.debian.org
if you have any questions.
If you find a problem with the Debian web server, you should generally submit a
bug against the pseudo-package, www.debian.org
. First check
whether or not someone else has already reported the problem on the Bug Tracking
System
.
cvs.debian.org is also known as va.debian.org, discussed above. If you need the use of a publically accessible CVS server, for instance, to help coordinate work on a package between many different developers, you can request a CVS area on the server.
Generally, cvs.debian.org offers a combination of local CVS
access, anonymous client-server read-only access, and full client-server access
through ssh
. Also, the CVS area can be accessed read-only via the
Web at http://cvs.debian.org/cgi-bin/cvsweb
.
To request a CVS area, send a request via email to debian-admin@debian.org
.
Include the name of the requested CVS area, what va.debian.org
user account should own the CVS root area, and why you need it.
The web and FTP servers have several mirrors available. Please do not put heavy load on the canonical FTP or web servers. Ideally, the canonical servers only mirror out to a first tier of mirrors, and all user access is to the mirrors. This allows Debian to better spread its bandwidth requirements over several servers and networks. Note that newer push mirroring techniques ensure that mirrors are as up-to-date as they can be.
The main web page listing the available public FTP (and, usually, HTTP) servers
can be found at http://www.debian.org/distrib/ftplist
.
More information concerning Debian mirrors can be found at http://www.debian.org/mirror/
.
This useful page includes information and tools which can be helpful if you are
interested in setting up your own mirror, either for internal or public access.
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.
Please do not mirror off of master.debian.org. This host already
has too much load. Check the sites above for information, or email debian-devel@lists.debian.org
.
There are other Debian machines which may be made available to you. You can use these for Debian-related purposes as you see fit. Please be kind to system administrators, and do not use up tons and tons of disk space, network bandwidth, or CPU without first getting the approval of the local maintainers. Usually these machines are run by volunteers. Generally, these machines are for porting activities.
Aside from the servers mentioned in Debian servers, Section 4.2, there
is a list of machines available to Debian developers at http://www.debian.org/devel/machines
.
aph@debian.org
schwarz@debian.org
ijackson@gnu.ai.mit.edu