X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=resources.dbk;h=4fa5909ab7bf9b02db782bb5f535fbcaef8e88ce;hp=57b3824f18faf2c02783c0a0f65be812ea79f1bd;hb=refs%2Fheads%2Fmaster;hpb=917680c03685a473f8fc55f8aeb2238991b48101 diff --git a/resources.dbk b/resources.dbk index 57b3824..4fa5909 100644 --- a/resources.dbk +++ b/resources.dbk @@ -4,7 +4,7 @@ %commondata; ]> -Resources for Debian Developers +Resources for Debian Developers and Debian Maintainers In this chapter you will find a very brief road map of the Debian mailing lists, the Debian machines which may be available to you as a developer, and @@ -15,7 +15,7 @@ all the other resources that are available to help you in your maintainer work. Much of the conversation between Debian developers (and users) is managed through a wide array of mailing lists we host at &lists-host;. +url="https://&lists-host;/">&lists-host;. To find out more on how to subscribe or unsubscribe, how to post and how not to post, where to find old posts and how to search them, how to contact the list maintainers and see various other information about the mailing lists, please @@ -78,7 +78,7 @@ issues related to the project. There are other mailing lists available for a variety of special topics; see - for a list. + for a list. @@ -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 @@ -164,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 @@ -181,9 +182,9 @@ June 2006. To get a cloak on freenode, you send Jörg Jaspert <joerg@debian.org> a 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 +url="https://freenode.net/faq.shtml#nicksetup">Nick Setup Page. The mail needs to be signed by a key in the Debian keyring. Please see Freenodes +url="https://freenode.net/faq.shtml#projectcloak">Freenode documentation for more information about cloaks. @@ -221,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 @@ -236,10 +237,16 @@ 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"). -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. +the list of open issues in the DSA (Debian System Administration) Team's queue +of our request tracker at (you can login with user +"debian", its password is available at +master.debian.org:&file-debian-rt-password;). To report a +new problem in the request tracker, simply send a mail to &email-rt-dsa; and +make sure to put the string "Debian RT" somewhere in the subject. To contact +the DSA team by email, use dsa@debian.org for anything that +contains private or privileged information and should not be made public, and +debian-admin@lists.debian.org otherwise. The DSA team is also +present on the #debian-admin IRC channel on OFTC. If you have a problem with a certain service, not related to the system @@ -259,9 +266,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 @@ -277,13 +281,13 @@ 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 . @@ -298,7 +302,7 @@ If you find a problem with the Debian web server, you should generally submit a bug against the pseudo-package, www.debian.org. Remember to check whether or not someone else has already reported the problem to the Bug Tracking System. +url="https://&bugs-host;/&www-debian-org;">Bug Tracking System. @@ -313,7 +317,7 @@ If you have some Debian-specific information which you want to serve on the web, you can do this by putting material in the public_html directory under your home directory on people.debian.org. This will be accessible at the URL -http://people.debian.org/~your-user-id/. +https://people.debian.org/~your-user-id/. You should only use this particular location because it will be backed up, @@ -333,7 +337,8 @@ 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 +(e.g. inside the collab-maint project) 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 @@ -357,7 +362,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;. +. @@ -453,13 +458,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 @@ -487,7 +492,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. @@ -531,17 +536,17 @@ Debian decided to build some ports based on other Unix kernels, like hurd and kfreebsd. -&debian-formal; 1.3 was only available as i386. Debian +Debian GNU/Linux 1.3 was only available as i386. Debian 2.0 shipped for i386 and m68k 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 @@ -564,31 +569,32 @@ 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. The .dsc file lists all the files in the source package -together with checksums (md5sums) and some additional info +together with checksums (md5sums, sha1sums, +sha256sums) and some additional info about the package (maintainer, version, etc.).
@@ -628,7 +634,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 @@ -638,9 +644,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 @@ -657,7 +663,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 @@ -671,8 +677,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. @@ -740,7 +746,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. @@ -752,12 +758,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. - @@ -770,13 +770,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; Debian 5.0, lenny -and the next release will be called squeeze. +Debian 4.0, etch; Debian 5.0, lenny; +Debian 6.0, squeeze; Debian 7.0, wheezy; +and the next release will be called jessie. 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 @@ -802,7 +803,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 @@ -856,10 +857,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 @@ -872,7 +873,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 @@ -882,12 +883,12 @@ 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 -&email-debian-devel-changes; instead. +Distribution set to unstable or +experimental, the announcement will be posted to +&email-debian-devel-changes; or &email-debian-experimental-changes; instead. Though ftp-master is restricted, a copy of the installation is available to all @@ -918,7 +919,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 @@ -931,7 +932,7 @@ 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: @@ -958,7 +959,7 @@ easily upload a package in one of the delayed directories: On the web Each package has several dedicated web pages. -http://&packages-host;/package-name +https://&packages-host;/package-name displays each version of the package available in the various distributions. Each version links to a page which provides information, including the package description, the dependencies, and package download links. @@ -966,7 +967,7 @@ description, the dependencies, and package download links. The bug tracking system tracks bugs for each package. You can view the bugs of a given package at the URL -http://&bugs-host;/package-name. +https://&bugs-host;/package-name. @@ -975,10 +976,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 @@ -1035,7 +1036,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. @@ -1044,7 +1045,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). @@ -1136,6 +1137,14 @@ example Ubuntu). + +derivatives-bugs + + +Bugs reports and comments from derivative distributions (for example Ubuntu). + + +
The PTS email interface @@ -1235,6 +1244,12 @@ distributions +derivatives-bugs: bugs reports and comments from derivative +distributions + + + + upload-source: announce of a new source upload that has been accepted @@ -1354,7 +1369,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. @@ -1368,18 +1383,18 @@ See for an example on how to do it. The PTS web interface The PTS has a web interface at that puts together a lot of +url="https://&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. You can jump directly to the web page concerning a specific source package with a URL like -http://&pts-host;/sourcepackage. +https://&pts-host;/sourcepackage. This web interface has been designed like a portal for the development of @@ -1472,7 +1487,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: @@ -1535,7 +1550,7 @@ responsibility. Alioth is a Debian service based on a slightly modified version of the 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. @@ -1562,25 +1577,11 @@ For more information please visit the following links:
-Goodies for Developers -
-LWN Subscriptions +Goodies for Debian Developers and Debian Maintainers -Since October of 2002, HP has sponsored a subscription to LWN for all -interested Debian developers. Details on how to get access to this benefit are -in . +Benefits available to Debian Developers and Debian Maintainers are documented on . -
-
-Gandi.net Hosting Discount - -As of November 2008, Gandi.net offers a discount rate on their VPS -hosting for Debian Developers. See -. - -
-