X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=resources.dbk;h=e577d6796a6b7992ee3ef87afd46123297897972;hp=45aeaf1b97d66e8e9d0d7ebb38657e218fbe713c;hb=960bc86f848f69ddc72409dbfbe09a78ea340e8b;hpb=c0e2a26f7817b5396ee5267d2e678c4f95593b76 diff --git a/resources.dbk b/resources.dbk index 45aeaf1..e577d67 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 @@ -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 @@ -261,9 +260,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 +271,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 +331,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 +355,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 +422,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 +451,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 +485,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 +523,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 5 supports a total of twelve architectures: alpha, +amd64, arm, +armel, hppa, +i386, ia64, mips, +mipsel, powerpc, +s390, sparc. Information for developers and users about the specific ports are available at @@ -573,20 +554,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,lzma} upstream tarball, +multiple optional .orig-component.tar.{gz,bz2,lzma} +additional upstream tarballs and a mandatory +debian.tar.{gz,bz2,lzma} debian +tarball; +with format “3.0 (native)”, it has only +a single .tar.{gz,bz2,lzma} 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,lzma} 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,lzma} 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,lzma} contains the changes +made by the Debian maintainer. The .dsc file lists all the files in the source package @@ -640,9 +636,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 +655,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 @@ -754,12 +750,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 +762,13 @@ 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 +and the next release will be called squeeze. +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 +794,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 @@ -873,7 +864,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 +874,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 +910,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 +923,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 +967,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 @@ -1051,6 +1042,15 @@ 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 +1075,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 +1128,14 @@ example Ubuntu). + +derivatives-bugs + + +Bugs reports and comments from derivative distributions (for example Ubuntu). + + +
The PTS email interface @@ -1224,6 +1235,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 +1259,11 @@ disparity, etc.) +buildd: build failures notifications from build daemons + + + + default: all the other mails (those which aren't automatic) @@ -1338,7 +1360,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 +1378,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 +1478,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 +1536,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 +1578,14 @@ in .
+
+Gandi.net Hosting Discount + +As of November 2008, Gandi.net offers a discount rate on their VPS +hosting for Debian Developers. See +. + +