X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=resources.dbk;h=57b3824f18faf2c02783c0a0f65be812ea79f1bd;hp=78aaab720c3e02879b2f103e214b734f17e0d16f;hb=917680c03685a473f8fc55f8aeb2238991b48101;hpb=c860a39ea13f7d552fc940a546b01be70c09b3a0 diff --git a/resources.dbk b/resources.dbk index 78aaab7..57b3824 100644 --- a/resources.dbk +++ b/resources.dbk @@ -152,10 +152,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. @@ -275,8 +273,8 @@ 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. @@ -337,18 +335,13 @@ Send mail to &email-debian-devel; if you have any questions. 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 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. -
@@ -431,9 +424,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: @@ -533,32 +525,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 +556,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 @@ -638,9 +636,10 @@ 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 each day after the new packages +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 . @@ -687,8 +686,8 @@ place in parallel with testing.
More information about the testing distribution -Packages are usually installed into the `testing' distribution after they have -undergone some degree of testing in unstable. +Packages are usually installed into the testing distribution +after they have undergone some degree of testing in unstable. For more details, please see the information about @@ -700,7 +699,8 @@ the testing distribution. Experimental The experimental distribution is a special distribution. -It is not a full distribution in the same sense as `stable' and `unstable' are. +It is not a full distribution in the same sense as stable, +testing and unstable are. Instead, it is meant to be a temporary staging area for highly experimental software where there's a good chance that the software could break your system, or software that's just too unstable even for the unstable @@ -753,9 +753,10 @@ 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. +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.
@@ -765,22 +766,29 @@ please consider using the option -v to Release code names Every released Debian distribution has a code name: Debian -1.1 is called `buzz'; Debian 1.2, `rex'; 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. 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 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 date. +1.1 is called buzz; Debian 1.2, rex; +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; 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 +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 +date. Since Debian has an open development model (i.e., everyone can participate and -follow the development) even the `unstable' and `testing' distributions are -distributed to the Internet through the Debian FTP and HTTP server network. -Thus, if we had called the directory which contains the release candidate -version `testing', then we would have to rename it to `stable' when the version +follow the development) even the unstable and +testing distributions are distributed to the Internet through the +Debian FTP and HTTP server network. Thus, if we had called the directory which +contains the release candidate version testing, then we +would have to rename it to stable when the version is released, which would cause all FTP mirrors to re-retrieve the whole distribution (which is quite large). @@ -875,11 +883,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 -to `stable', the announcement is sent to +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 &email-debian-devel-changes; -instead. +Distribution: set to unstable or +experimental, the announcement will be posted to +&email-debian-devel-changes; instead. Though ftp-master is restricted, a copy of the installation is available to all @@ -929,7 +937,7 @@ 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, @@ -962,28 +970,30 @@ a given package at the URL
-
-The <command>madison</command> utility +
+The <command>dak ls</command> utility -madison is a command-line utility that is available on -&ftp-master-host;, and on the mirror on -&ftp-master-mirror;. It uses a single argument corresponding -to a package name. In result it displays which version of the package is -available for each architecture and distribution combination. An example will -explain it better. +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: -$ madison libdbd-mysql-perl -libdbd-mysql-perl | 1.2202-4 | stable | source, alpha, arm, i386, m68k, powerpc, sparc -libdbd-mysql-perl | 1.2216-2 | testing | source, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc -libdbd-mysql-perl | 1.2216-2.0.1 | testing | alpha -libdbd-mysql-perl | 1.2219-1 | unstable | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc +$ dak ls evince +evince | 0.1.5-2sarge1 | oldstable | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc +evince | 0.4.0-5 | etch-m68k | source, m68k +evince | 0.4.0-5 | stable | source, alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc +evince | 2.20.2-1 | testing | source +evince | 2.20.2-1+b1 | testing | alpha, amd64, arm, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc +evince | 2.22.2-1 | unstable | source, alpha, amd64, arm, armel, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc In this example, you can see that the version in unstable differs from the version in testing and that there has -been a binary-only NMU of the package for the alpha architecture. Each version -of the package has been recompiled on most of the architectures. +been a binary-only NMU of the package for all architectures. Each version +of the package has been recompiled on all architectures.
@@ -1040,6 +1050,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 @@ -1064,8 +1083,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. @@ -1231,6 +1253,11 @@ disparity, etc.) +buildd: build failures notifications from build daemons + + + + default: all the other mails (those which aren't automatic) @@ -1503,10 +1530,10 @@ 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 repositories etc. All these tools are managed via a web interface. @@ -1545,6 +1572,14 @@ in .
+
+Gandi.net Hosting Discount + +As of November 2008, Gandi.net offers a discount rate on their VPS +hosting for Debian Developers. See +. + +