X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=resources.dbk;h=61d8748b3361d541752dcd3abc5c51e93185ae74;hp=a49dbc276e9c3d09aa7685d220ce69db83144926;hb=9afdf8bcc6795a93b50467b46c13f93665ce9624;hpb=7347b8fe6bde56036f349496304bca972f7035ee diff --git a/resources.dbk b/resources.dbk index a49dbc2..61d8748 100644 --- a/resources.dbk +++ b/resources.dbk @@ -238,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. @@ -331,7 +332,7 @@ 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 (cvs.alioth.debian.org/cvs.debian.org), Subversion (svn.debian.org), Arch (tla/baz, both on arch.debian.org), Bazaar @@ -534,12 +535,12 @@ Debian decided to build some ports based on other Unix kernels, like architectures. Debian 2.1 shipped for the i386, m68k, alpha, and sparc architectures. Since then Debian has grown hugely. -Debian 5 supports a total of twelve architectures: alpha, -amd64, arm, -armel, hppa, -i386, ia64, mips, +Debian 6 supports a total of nine Linux architectures (amd64, +armel, i386, +ia64, mips, mipsel, powerpc, -s390, sparc. +s390, sparc) and two kFreeBSD architectures +(kfreebsd-i386 and kfreebsd-amd64). Information for developers and users about the specific ports are available at @@ -562,26 +563,26 @@ file: 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} +.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,lzma} debian +debian.tar.{gz,bz2,xz} debian tarball; with format “3.0 (native)”, it has only -a single .tar.{gz,bz2,lzma} tarball. +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,bz2,lzma} file which contains the sources of +.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,lzma} file stores the so-called +.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,lzma} contains the changes +or the debian.tar.{gz,bz2,xz} contains the changes made by the Debian maintainer. @@ -636,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 @@ -655,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 @@ -669,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. @@ -738,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. @@ -762,8 +763,9 @@ 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; Debian 5.0, lenny -and the next release will be called squeeze. +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 @@ -848,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 @@ -967,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 @@ -1027,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. @@ -1036,7 +1038,7 @@ 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).