X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=resources.dbk;h=4563a88e642812a6a1831da1c030faf6c12b9591;hb=6f7c41c426675060d3018aca215bc15ad5ba79ab;hp=45aeaf1b97d66e8e9d0d7ebb38657e218fbe713c;hpb=c0e2a26f7817b5396ee5267d2e678c4f95593b76;p=developers-reference.git
diff --git a/resources.dbk b/resources.dbk
index 45aeaf1..4563a88 100644
--- a/resources.dbk
+++ b/resources.dbk
@@ -141,7 +141,8 @@ similarly named channels for speakers of other languages.
The main channel for Debian development is #debian-devel.
-It is a very active channel since usually over 150 people are always logged in.
+It is a very active channel; it will typically have a minimum of 150 people
+at any time of day.
It's a channel for people who work on Debian, it's not a support channel
(there's #debian for that). It is however open to anyone
who wants to lurk (and learn). Its topic is commonly full of interesting
@@ -152,10 +153,8 @@ Since #debian-devel is an open channel, you should not
speak there of issues that are discussed in
&email-debian-private;. There's another channel for this
purpose, it's called #debian-private and it's protected by
-a key. This key is available in the archives of debian-private in
-master.debian.org:&file-debian-private-archive;,
-just zgrep for #debian-private in all
-the files.
+a key. This key is available at
+master.debian.org:&file-debian-private-key;.
There are other additional channels dedicated to specific subjects.
@@ -166,7 +165,7 @@ talk about documentation, like the document you are reading. Other channels
are dedicated to an architecture or a set of packages:
#debian-kde, #debian-dpkg,
#debian-jr, #debian-edu,
-#debian-oo (OpenOffice package) ...
+#debian-oo (OpenOffice.org package)...
Some non-English developers' channels exist as well, for example
@@ -185,7 +184,7 @@ signed mail where you tell what your nick is. Put cloak somewhere in the
Subject: header. The nick should be registered: Nick Setup Page. The
mail needs to be signed by a key in the Debian keyring. Please see Freenodes
+url="http://freenode.net/faq.shtml#projectcloak">Freenode
documentation for more information about cloaks.
@@ -223,7 +222,7 @@ volunteers.
Please take care to protect your Debian passwords and SSH keys installed on
Debian machines. Avoid login or upload methods which send passwords over the
-Internet in the clear, such as telnet, FTP, POP etc.
+Internet in the clear, such as Telnet, FTP, POP etc.
Please do not put any material that doesn't relate to Debian on the Debian
@@ -239,7 +238,8 @@ etc.
If you have a problem with the operation of a Debian server, and you think that
the system operators need to be notified of this problem, you can check
the list of open issues in the DSA queue of our request tracker at (you can login with user "guest" and password "readonly").
+url="&url-rt;" /> (you can login with user "debian", its password is available at
+master.debian.org:&file-debian-rt-password;).
To report a new problem, simply send a mail to &email-rt-dsa; and make
sure to put the string "Debian RT" somewhere in the subject.
@@ -261,9 +261,6 @@ mirrored to another server.
the Bug Tracking System (BTS).
-It is restricted; a mirror is available on merkel.
-
-
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
&email-debian-devel; before implementing anything, however, to
@@ -275,17 +272,17 @@ reduce unnecessary duplication of effort or wasted processing time.
The ftp-master server
The &ftp-master-host; server holds the canonical copy of
-the Debian archive. Generally, package uploads go to this server; see
-.
+the Debian archive. Generally, package uploaded to &ftp-upload-host;
+end up on this server, see .
-It is restricted; a mirror is available on merkel.
+It is restricted; a mirror is available on &ftp-master-mirror;.
Problems with the Debian FTP archive generally need to be reported as bugs
against the &ftp-debian-org;
pseudo-package or an email to &email-ftpmaster;, but also see
-the procedures in .
+the procedures in .
@@ -335,20 +332,15 @@ Send mail to &email-debian-devel; if you have any questions.
The VCS servers
If you need to use a Version Control System for any of your Debian work,
-you can use one the existing repositories hosted on Alioth or you can
+you can use one of the existing repositories hosted on Alioth or you can
request a new project and ask for the VCS repository of your choice.
-Alioth supports CVS (alioth.debian.org), Subversion
+Alioth supports CVS (cvs.alioth.debian.org/cvs.debian.org), Subversion
(svn.debian.org), Arch (tla/baz, both on arch.debian.org), Bazaar
(bzr.debian.org), Darcs (darcs.debian.org), Mercurial (hg.debian.org) and Git
(git.debian.org). Checkout if you plan
to maintain packages in a VCS repository. See for
information on the services provided by Alioth.
-
-Historically, Debian first used cvs.debian.org to host
-CVS repositories. But that service is deprecated in favor of Alioth.
-Only a few projects are still using it.
-
@@ -364,7 +356,7 @@ Executing shell in chroot: /org/vore.debian.org/chroots/user/unstable
In all chroots, the normal user home directories are available. You can find
out which chroots are available via
-&url-devel-machines;.
+.
@@ -431,9 +423,8 @@ url="&url-debian-db-mail-gw;">.
The Debian archive
The &debian-formal; distribution consists of a lot of packages
-(.deb's, currently around
-&number-of-pkgs;) and a few additional files (such as
-documentation and installation disk images).
+(currently around &number-of-pkgs; source packages) and a few additional
+files (such as documentation and installation disk images).
Here is an example directory tree of a complete Debian archive:
@@ -461,13 +452,13 @@ distributions is arranged in an identical manner. What we describe below for
In each of the areas, there is a directory for the source packages
(source) and a directory for each supported architecture
-(binary-i386, binary-m68k, etc.).
+(binary-i386, binary-amd64, etc.).
The main area contains additional directories which hold
the disk images and some essential pieces of documentation required for
installing the Debian distribution on a specific architecture
-(disks-i386, disks-m68k, etc.).
+(disks-i386, disks-amd64, etc.).
Sections
@@ -495,7 +486,7 @@ non-free packages.
Packages which do not conform to the DFSG are placed in the
non-free section. These packages are not considered as
-part of the Debian distribution, though we support their use, and we provide
+part of the Debian distribution, though we enable their use, and we provide
infrastructure (such as our bug-tracking system and mailing lists) for non-free
software packages.
@@ -533,32 +524,23 @@ Nowadays, these exist only in the Section header fields of packages.
In the first days, the Linux kernel was only available for Intel i386 (or
greater) platforms, and so was Debian. But as Linux became more and more
-popular, the kernel was ported to other architectures, too.
+popular, the kernel was ported to other architectures and Debian started
+to support them. And as if supporting so much hardware was not enough,
+Debian decided to build some ports based on other Unix kernels, like
+hurd and kfreebsd.
-The Linux 2.0 kernel supports Intel x86, DEC Alpha, SPARC, Motorola 680x0 (like
-Atari, Amiga and Macintoshes), MIPS, and PowerPC. The Linux 2.2 kernel
-supports even more architectures, including ARM and UltraSPARC. Since Linux
-supports these platforms, Debian decided that it should, too. Therefore,
-Debian has ports underway; in fact, we also have ports underway to non-Linux
-kernels. Aside from i386 (our name for Intel x86), there
-is m68k, alpha,
-powerpc, sparc,
-hurd-i386, arm,
-ia64, hppa,
-s390, mips,
-mipsel and sh as of this writing.
-
-
-&debian-formal; 1.3 is only available as i386. Debian
+&debian-formal; 1.3 was only available as i386. Debian
2.0 shipped for i386 and m68k
-architectures. Debian 2.1 ships for the i386,
+architectures. Debian 2.1 shipped for the i386,
m68k, alpha, and
-sparc architectures. Debian 2.2 added support for the
-powerpc and arm architectures.
-Debian 3.0 added support of five new architectures: ia64,
-hppa, s390, mips
-and mipsel.
+sparc architectures. Since then Debian has grown hugely.
+Debian 6 supports a total of nine Linux architectures (amd64,
+armel, i386,
+ia64, mips,
+mipsel, powerpc,
+s390, sparc) and two kFreeBSD architectures
+(kfreebsd-i386 and kfreebsd-amd64).
Information for developers and users about the specific ports are available at
@@ -573,20 +555,35 @@ There are two types of Debian packages, namely source and
binary packages.
-Source packages consist of either two or three files: a
-.dsc file, and either a .tar.gz file
-or both an .orig.tar.gz and a
-.diff.gz file.
+Depending on the format of the source package, it will consist
+of one or more files in addition to the mandatory .dsc
+file:
+
+with format â1.0â, it has either a .tar.gz
+file or both an .orig.tar.gz and a
+.diff.gz file;
+with format â3.0 (quilt)â, it has a mandatory
+.orig.tar.{gz,bz2,xz} upstream tarball,
+multiple optional .orig-component.tar.{gz,bz2,xz}
+additional upstream tarballs and a mandatory
+debian.tar.{gz,bz2,xz} debian
+tarball;
+with format â3.0 (native)â, it has only
+a single .tar.{gz,bz2,xz} tarball.
+
-If a package is developed specially for Debian and is not distributed outside
-of Debian, there is just one .tar.gz file which contains
-the sources of the program. If a package is distributed elsewhere too, the
-.orig.tar.gz file stores the so-called upstream
-source code, that is the source code that's distributed by the
-upstream maintainer (often the author of the software).
-In this case, the .diff.gz contains the changes made by
-the Debian maintainer.
+If a package is developed specially for Debian and is not distributed
+outside of Debian, there is just one
+.tar.{gz,bz2,xz} file which contains the sources of
+the program, it's called a ânativeâ source package. If a package is
+distributed elsewhere too, the
+.orig.tar.{gz,bz2,xz} file stores the so-called
+upstream source code, that is the source code that's
+distributed by the upstream maintainer (often the
+author of the software). In this case, the .diff.gz
+or the debian.tar.{gz,bz2,xz} contains the changes
+made by the Debian maintainer.
The .dsc file lists all the files in the source package
@@ -630,7 +627,7 @@ development process of the Debian project.
Active development is done in the unstable distribution
(that's why this distribution is sometimes called the development
-distribution). Every Debian developer can update his or her
+distribution). Every Debian developer can update their
packages in this distribution at any time. Thus, the contents of this
distribution change from day to day. Since no special effort is made to make
sure everything in this distribution is working properly, it is sometimes
@@ -640,9 +637,9 @@ literally unstable.
The testing distribution is generated
automatically by taking packages from unstable if they
satisfy certain criteria. Those criteria should ensure a good quality for
-packages within testing. The update to testing
- is launched twice each day, right after the new packages
-have been installed. See .
+packages within testing. The update to
+testing is launched twice each day, right after the new
+packages have been installed. See .
After a period of development, once the release manager deems fit, the
@@ -659,7 +656,7 @@ the Release Team, the distribution is released. Releasing means that
new copy is created for the new testing, and the previous
stable is renamed to oldstable and
stays there until it is finally archived. On archiving, the contents are moved
-to &archive-host;).
+to &archive-host;.
This development cycle is based on the assumption that the
@@ -673,8 +670,8 @@ additions to stable in the
proposed-updates directory. Those packages in
proposed-updates that pass muster are periodically moved
as a batch into the stable distribution and the revision level of the stable
-distribution is incremented (e.g., â3.0â becomes â3.0r1â, â2.2r4â
-becomes â2.2r5â, and so forth). Please refer to
+distribution is incremented (e.g., â6.0â becomes â6.0.1â, â5.0.7â
+becomes â5.0.8â, and so forth). Please refer to
uploads to the stable
distribution for details.
@@ -742,7 +739,7 @@ with a few warnings in the description, but that isn't recommended because
packages from unstable are expected to propagate to
testing and thus to stable. You
should not be afraid to use experimental since it does not
-cause any pain to the ftpmasters, the experimental packages are automatically
+cause any pain to the ftpmasters, the experimental packages are periodically
removed once you upload the package in unstable with a
higher version number.
@@ -754,12 +751,6 @@ New software which isn't likely to damage your system can go directly into
An alternative to experimental is to use your personal web
space on people.debian.org.
-
-When uploading to unstable a package which had bugs fixed
-in experimental, please consider using the option
--v to dpkg-buildpackage to finally get
-them closed.
-
@@ -772,12 +763,14 @@ Every released Debian distribution has a code name: Debian
Debian 1.3, bo; Debian 2.0, hamm;
Debian 2.1, slink; Debian 2.2, potato;
Debian 3.0, woody; Debian 3.1, sarge;
-Debian 4.0, etch and Debian 5.0 will be called
-lenny. There is also a ``pseudo-distribution'', called
+Debian 4.0, etch; Debian 5.0, lenny;
+Debian 6.0, squeeze
+and the next release will be called wheezy.
+There is also a ``pseudo-distribution'', called
sid, which is the current unstable
distribution; since packages are moved from unstable to
testing as they approach stability, sid
-itself is never released. As well as the usual contents of a Debian
+itself is never released. As well as the usual contents of a Debian
distribution, sid contains packages for architectures which
are not yet officially supported or released by Debian. These architectures
are planned to be integrated into the mainstream distribution at some future
@@ -803,7 +796,7 @@ was 1.1, and not 1.0.)
Thus, the names of the distribution directories in the archive are determined
-by their code names and not their release status (e.g., `slink'). These names
+by their code names and not their release status (e.g., `squeeze'). These names
stay the same during the development period and after the release; symbolic
links, which can be changed easily, indicate the currently released stable
distribution. That's why the real distribution directories use the
@@ -857,10 +850,10 @@ by a daemon called queued,
signed *.changes-files are moved together with their
corresponding files to the unchecked directory. This
directory is not visible for most Developers, as ftp-master is restricted; it
-is scanned every 15 minutes by the katie script, which
-verifies the integrity of the uploaded packages and their cryptographic
+is scanned every 15 minutes by the dak process-upload script,
+which verifies the integrity of the uploaded packages and their cryptographic
signatures. If the package is considered ready to be installed, it is moved
-into the accepted directory. If this is the first upload
+into the done directory. If this is the first upload
of the package (or it has new binary packages), it is moved to the
new directory, where it waits for approval by the
ftpmasters. If the package contains files to be installed by hand it is moved
@@ -873,7 +866,7 @@ Once the package is accepted, the system sends a confirmation mail to the
maintainer and closes all the bugs marked as fixed by the upload, and the
auto-builders may start recompiling it. The package is now publicly accessible
at until it is really
-installed in the Debian archive. This happens only once a day (and is also
+installed in the Debian archive. This happens four times a day (and is also
called the `dinstall run' for historical reasons); the package is then removed
from incoming and installed in the pool along with all the other packages.
Once all the other updates (generating new Packages and
@@ -883,11 +876,11 @@ script is called to ask all the primary mirrors to update themselves.
The archive maintenance software will also send the OpenPGP/GnuPG signed
.changes file that you uploaded to the appropriate mailing
-lists. If a package is released with the Distribution: set
+lists. If a package is released with the Distribution set
to stable, the announcement is sent to
&email-debian-changes;. If a package is released with
-Distribution: set to unstable or
-experimental, the announcement will be posted to
+Distribution set to unstable or
+experimental, the announcement will be posted to
&email-debian-devel-changes; instead.
@@ -919,7 +912,7 @@ one of those directories will be moved to the real unchecked
directory after the corresponding number of days.
This is done by a script which is run each day and which moves the
packages between the directories. Those which are in "1-day" are
-installed in unchecked while the others are moved to the
+installed in unchecked while the others are moved to the
adjacent directory (for example, a package in 5-day will
be moved to 4-day). This feature is particularly useful
for people who are doing non-maintainer uploads. Instead of
@@ -932,13 +925,13 @@ the NMU.
The use of that delayed feature can be simplified with a bit
-of integration with your upload tool. For instance, if you use
+of integration with your upload tool. For instance, if you use
dupload (see ), you can add this
snippet to your configuration file:
$delay = ($ENV{DELAY} || 7);
$cfg{'delayed'} = {
- fqdn => "&ftp-master-host;",
+ fqdn => "&ftp-upload-host;",
login => "yourdebianlogin",
incoming => "/org/&ftp-debian-org;/incoming/DELAYED/$delay-day/",
dinstall_runs => 1,
@@ -976,10 +969,10 @@ a given package at the URL
dak ls is part of the dak suite of tools, listing
available package versions for all known distributions and architectures.
-The dak tool is available on &ftp-master-host;
-, and on the mirror on &ftp-master-mirror;.
-It uses a single argument corresponding to a package name. An example will
-explain it better:
+The dak tool is available on
+&ftp-master-host;, and on the mirror on
+&ftp-master-mirror;. It uses a single argument
+corresponding to a package name. An example will explain it better:
$ dak ls evince
@@ -1036,7 +1029,7 @@ report status changes.
upload-source
-The email notification from katie when an uploaded source
+The email notification from dak when an uploaded source
package is accepted.
@@ -1045,12 +1038,21 @@ package is accepted.
katie-other
-Other warning and error emails from katie (such as an
+Other warning and error emails from dak (such as an
override disparity for the section and/or the priority field).
+buildd
+
+
+Build failures notifications sent by the network of build daemons, they contain
+a pointer to the build logs for analysis.
+
+
+
+default
@@ -1075,8 +1077,11 @@ aliases.
summary
-Regular summary emails about the package's status. Currently, only progression
-in testing is sent.
+Regular summary emails about the package's status, including progression
+into testing,
+DEHS notifications of
+new upstream versions, and a notification if the package is removed or
+orphaned.
@@ -1125,6 +1130,14 @@ example Ubuntu).
+
+derivatives-bugs
+
+
+Bugs reports and comments from derivative distributions (for example Ubuntu).
+
+
+The PTS email interface
@@ -1224,6 +1237,12 @@ distributions
+derivatives-bugs: bugs reports and comments from derivative
+distributions
+
+
+
+upload-source: announce of a new source upload that has been
accepted
@@ -1242,6 +1261,11 @@ disparity, etc.)
+buildd: build failures notifications from build daemons
+
+
+
+default: all the other mails (those which aren't automatic)
@@ -1338,7 +1362,7 @@ Once you set up the VCS repository to generate commit notifications, you just
have to make sure it sends a copy of those mails to
sourcepackage_cvs@&pts-host;.
Only the people who accept the cvs keyword will receive
-these notifications. Note that the mail need to be sent from a
+these notifications. Note that the mail needs to be sent from a
debian.org machine, otherwise you'll have to add
the X-PTS-Approved: 1 header.
@@ -1356,7 +1380,7 @@ url="http://&pts-host;/"> that puts together a lot of
information about each source package. It features many useful links (BTS, QA
stats, contact information, DDTP translation status, buildd logs) and gathers
much more information from various places (30 latest changelog entries, testing
-status, ...). It's a very useful tool if you want to know what's going on with
+status, etc.). It's a very useful tool if you want to know what's going on with
a specific source package. Furthermore there's a form that allows easy
subscription to the PTS via email.
@@ -1456,7 +1480,7 @@ item.
Here are a few examples of valid mails used to generate news items in the PTS.
-The first one adds a link to the cvsweb interface of debian-cd in the Static
+The first one adds a link to the viewsvn interface of debian-cd in the Static
information section:
@@ -1514,12 +1538,12 @@ responsibility.
-Debian's GForge installation: Alioth
+Debian's FusionForge installation: Alioth
Alioth is a Debian service based on a slightly modified version of the
-GForge software (which evolved from SourceForge). This software offers
+FusionForge software (which evolved from SourceForge and GForge). This software offers
developers access to easy-to-use tools such as bug trackers, patch
-manager, project/task managers, file hosting services, mailing lists, CVS
+manager, project/task managers, file hosting services, mailing lists, VCS
repositories etc. All these tools are managed via a web interface.
@@ -1556,6 +1580,14 @@ in .
+
+Gandi.net Hosting Discount
+
+As of November 2008, Gandi.net offers a discount rate on their VPS
+hosting for Debian Developers. See
+.
+
+