X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=resources.dbk;h=8bab31baa86267f0ce8231e3b9fbece1ccccf483;hb=3f2c4a8b484f5bec54e2ef45cd38c0bcf49eb691;hp=6ecfbd995c66bb4d2083c1b173fdc27b0e302b72;hpb=ce95311f7724b08245d0a902caffc4690e0ed532;p=developers-reference.git diff --git a/resources.dbk b/resources.dbk index 6ecfbd9..8bab31b 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. @@ -275,8 +274,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 +336,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 +425,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: @@ -495,7 +488,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 +526,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. - - -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. +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. -&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 +557,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 @@ -939,7 +938,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, @@ -1052,6 +1051,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 @@ -1076,8 +1084,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. @@ -1243,6 +1254,11 @@ disparity, etc.) +buildd: build failures notifications from build daemons + + + + default: all the other mails (those which aren't automatic) @@ -1339,7 +1355,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. @@ -1515,10 +1531,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.