X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=developers-reference.sgml;h=3b1206feb930bff99b49e0076307e098b909c228;hp=af972e7fc7ae67b7b5508c071192ec50b7277b37;hb=af4a79e2cde3500ee7977db96bf127159508ddab;hpb=eb93665f453f3dbb7e8813a722cc2c3f7099a578 diff --git a/developers-reference.sgml b/developers-reference.sgml index af972e7..3b1206f 100644 --- a/developers-reference.sgml +++ b/developers-reference.sgml @@ -4,14 +4,18 @@ %versiondata; %commondata; - - - + + + + + FIXME: "> + ]>

The procedures discussed within include how to become a maintainer (); how to upload new packages (); and how to handle bug reports ().

The resources discussed in this reference include the mailing lists -and servers (); a discussion of the structure of the -Debian archive (); explanation of the different -servers which accept package uploads (); and a -discussion of resources which can help maintainers with the quality of -their packages (). +() and servers (); a +discussion of the structure of the Debian archive (); explanation of the different servers which accept +package uploads (); and a discussion of +resources which can help maintainers with the quality of their +packages ().

It should be clear that this reference does not discuss the technical details of the Debian package nor how to generate Debian packages. @@ -89,19 +96,22 @@ generally agreed-upon best practices. Thus, it is what is called a Applying to Become a Maintainer - Getting started + Getting started

-So, you've read all the documentation, you understand what everything -in the hello example package is for, and you're about to -Debianize your favourite piece of software. How do you actually -become a Debian developer so that your work can be incorporated into -the Project? +So, you've read all the documentation, you've gone through the , +understand what everything in the hello example +package is for, and you're about to Debianize your favorite piece of +software. How do you actually become a Debian developer so that your +work can be incorporated into the Project?

Firstly, subscribe to &email-debian-devel; if you haven't already. Send the word subscribe in the Subject of an email to &email-debian-devel-req;. In case of problems, contact the list administrator at &email-listmaster;. More information on available mailing lists can be found in . +&email-debian-devel-announce; is another list which is mandatory +for anyone who wishes to follow Debian's development.

You should subscribe and lurk (that is, read without posting) for a bit before doing any coding, and you should post about your intentions @@ -118,8 +128,8 @@ should get in contact with existing Debian maintainers who are working on similar tasks. That way, you can learn from experienced developers. For example, if you are interested in packaging existing software for Debian you should try to get a sponsor. A sponsor will work together -with you on your package and upload it to the Debian archive once he -is happy with the packaging work you have done. You can find a sponsor +with you on your package and upload it to the Debian archive once they +are happy with the packaging work you have done. You can find a sponsor by mailing the &email-debian-mentors; mailing list, describing your package and yourself and asking for a sponsor (see for more information on sponsoring). On the other hand, if you are @@ -163,14 +173,14 @@ maintaining their own packages. If you can help other maintainers by providing further information on a bug or even a patch, then do so!

Registration requires that you are familiar with Debian's philosophy -and technical documentation. Furthermore, you need a GPG key which -has been signed by an existing Debian maintainer. If your GPG key +and technical documentation. Furthermore, you need a GnuPG key which +has been signed by an existing Debian maintainer. If your GnuPG key is not signed yet, you should try to meet a Debian maintainer in person to get your key signed. There's a which should help you find +name="GnuPG Key Signing Coordination page"> which should help you find a maintainer close to you (If you cannot find a Debian maintainer close to you, there's an alternative way to pass the ID check. You -can send in a photo ID signed with your GPG key. Having your GPG +can send in a photo ID signed with your GnuPG key. Having your GnuPG key signed is the preferred way, however. See the for more information about these two options.) @@ -187,11 +197,11 @@ information on maintaining your public key. Debian uses the GNU Privacy Guard (package gnupg version 1 or better) as its baseline standard. You can use some other implementation of OpenPGP as well. Note that -OpenPGP is a open standard based on .

The recommended public key algorithm for use in Debian development -work is the DSA (sometimes call ``DSS'' or ``DH/ElGamal''). Other key +work is DSA (sometimes call ``DSS'' or ``DH/ElGamal''). Other key types may be used however. Your key length must be at least 1024 bits; there is no reason to use a smaller key, and doing so would be much less secure. Your key must be signed with at least your own user @@ -207,10 +217,10 @@ on the servers if it isn't already there. Some countries restrict the use of cryptographic software by their citizens. This need not impede one's activities as a Debian package maintainer however, as it may be perfectly legal to use cryptographic -products for authentication, rather than encryption purposes (as is -the case in France). &debian-formal; does not require the use of -cryptography qua cryptography in any manner. If you live in a -country where use of cryptography even for authentication is forbidden +products for authentication, rather than encryption purposes. +&debian-formal; does not require the use of cryptography qua +cryptography in any manner. If you live in a country where use of +cryptography even for authentication is forbidden then please contact us so we can make special arrangements.

To apply as a new maintainer, you need an existing Debian maintainer @@ -220,7 +230,7 @@ registered developer, an existing developer with whom you have worked over the past months has to express his belief that you can contribute to Debian successfully.

-When you have found an advocate, have your GPG key signed and have +When you have found an advocate, have your GnuPG key signed and have already contributed to Debian for a while, you're ready to apply. You can simply register on our . After you have signed up, your advocate @@ -234,10 +244,10 @@ For more details, please consult at the Debian web site. Make sure that you are familiar with the necessary steps of the New Maintainer process before actually applying. If you are well prepared, you can save -a lot of timer later on. +a lot of time later on. - Debian Mentors + Debian mentors and sponsors

The mailing list &email-debian-mentors; has been set up for novice maintainers who seek help with initial packaging and other @@ -246,13 +256,23 @@ to that list (see for details).

Those who prefer one-on-one help (e.g., via private email) should also post to that list and an experienced developer will volunteer to help. +

+In addition, if you have some packages ready for inclusion in Debian, +but are waiting for your new maintainer application to go through, you +might be able find a sponsor to upload your package for you. Sponsors +are people who are official Debian maintainers, and who are willing to +criticize and upload your packages for you. Those who are seeking a +sponsor can request one at . +

+If you wish to be a mentor and/or sponsor, more information is +available in . Debian Developer's Duties - Maintaining Your Debian Information + Maintaining your Debian information

-There's a LDAP database containing many informations concerning all +There's a LDAP database containing information about all developers, you can access it at . You can update your password (this password is propagated to most of the machines that are accessible to you), your address, your country, the latitude and @@ -263,33 +283,52 @@ is not accessible to the public, for more details about this database, please read its online documentation that you can find at .

-You have to keep the information available there up to date. +You have to keep the information available there up-to-date. - Maintaining Your Public Key + Maintaining your public key

Be very careful with your private keys. Do not place them on any -public servers or multiuser machines, such as -master.debian.org. Back your keys up; keep a copy offline. +public servers or multiuser machines, such as the Debian servers +(see ). Back your keys up; keep a copy offline. Read the documentation that comes with your software; read the .

If you add signatures to your public key, or add user identities, you -can update the debian keyring by sending your key to the key server at +can update the Debian key ring by sending your key to the key server at &keyserver-host;. If you need to add a completely new key, or remove an old key, send mail to &email-debian-keyring;. The same key extraction routines discussed in apply.

You can find a more in-depth discussion of Debian key maintenance in -the documentation for the debian-keyring package. +the documentation of the debian-keyring package. - Going On Vacation Gracefully + + Voting +

+Even if Debian is not always a real democracy, Debian has democratic +tools and uses a democratic process to elect its leader or +to approve a general resolution. Those processes are described in +the . +

+Democratic processes work well only if everybody take part in the +vote, that's why you have to vote. To be able to vote you have to +subscribe to &email-debian-devel-announce; since call for votes are sent +there. If you want to follow the debate preceding a vote, you +may want to subscribe to &email-debian-vote;. +

+The list of all the proposals (past and current) is available on the + page. You will find +there additional information about how to make a vote proposal. + + + Going on vacation gracefully

Most developers take vacations, and usually this means that they can't work for Debian and they can't be reached by email if any problem occurs. The other developers need to know that you're on vacation so that they'll do whatever is needed when such a problem occurs. Usually this means that other developers are allowed to NMU (see ) your package if a -big problem (release critical bugs, security update, ...) occurs while +big problem (release critical bugs, security update, etc.) occurs while you're on vacation.

In order to inform the other developers, there's two things that you should do. @@ -304,7 +343,7 @@ available in the Debian LDAP database and mark yourself as ``on vacation'' (this information is only accessible to debian developers). Don't forget to remove the ``on vacation'' flag when you come back! - Coordination With Upstream Developers + Coordination with upstream developers

A big part of your job as Debian maintainer will be to stay in contact with the upstream developers. Debian users will sometimes report bugs @@ -318,14 +357,14 @@ submit patches to fix upstream bugs, and you should evaluate and forward these patches upstream.

If you need to modify the upstream sources in order to build a policy -conformant package, then you should propose a nice fix to the upstream +compliant package, then you should propose a nice fix to the upstream developers which can be included there, so that you won't have to modify the sources of the next upstream version. Whatever changes you need, always try not to fork from the upstream sources. - Managing Release Critical Bugs + Managing release-critical bugs

-Release Critical Bugs (RCB) are all bugs that have severity +Release-critical bugs (RCB) are all bugs that have severity critical, grave or serious. Those bugs can delay the Debian release and/or can justify the removal of a package at freeze time. That's why @@ -342,35 +381,8 @@ from the QA group may want to do a Non-Maintainer Upload (see usual before they do their NMU if they have seen no recent activity from you in the BTS). - Quality Assurance Effort -

-Even though there is a dedicated group of people for Quality -Assurance, QA duties are not reserved solely for them. You can -participate in this effort by keeping your packages as bug-free as -possible, and as lintian-clean (see ) as -possible. If you do not find that possible, then you should consider -orphaning some of your packages (see ). Alternatively, you may ask the help of other people -in order to catch up the backlog of bugs that you have (you can ask -for help on &email-debian-qa; or &email-debian-devel;). - - Dealing with unreachable maintainers -

-If you notice that a package is lacking maintenance, you should -make sure the maintainer is active and will continue to work on -his packages. Try contacting him yourself. -

-If you do not get a reply after a few weeks you should collect all -useful information about this maintainer. Start by logging into -the -and doing a full search to check whether the maintainer is on vacation -and when he was last seen. Collect any important package names -he maintains and any Release Critical bugs filled against them. -

-Send all this information to &email-debian-qa;, in order to let the -QA people do whatever is needed. - Retiring Gracefully + Retiring

If you choose to leave the Debian project, you should make sure you do the following steps: @@ -383,100 +395,188 @@ Send an email about how you are leaving the project to Notify the Debian key ring maintainers that you are leaving by emailing to &email-debian-keyring;. - + - Mailing Lists, Servers, and Other Machines -

+ + Resources for Debian Developers +

In this chapter you will find a very brief road map of the Debian -mailing lists, the main Debian servers, and other Debian machines -which may be available to you as a developer. +mailing lists, the Debian machines +which may be available to you as a developer, and all the other +resources that are available to help you in your maintainer work. Mailing lists

-The mailing list server is at &lists-host;. Mail +The mailing list server is at &lists-host;. +

+Online archives of mailing lists are available at . + + Core development mailing lists +

+The core Debian mailing lists that developers should use are: + + &email-debian-devel-announce;, used to announce important things to + developers. + All developers are expected to be subscribed to this list. + + &email-debian-devel;, used to discuss various development related + technical issues. + + &email-debian-policy;, where the Debian Policy is discussed and + voted on. + + &email-debian-project;, used to discuss various non-technical + issues related to the project. + + +

+There are +other mailing lists available for a variety of special topics; see + for a list. + + Subscribing and unsubscribing +

+To subscribe to or unsubscribe from any of the Debian mailing lists, email debian-foo-REQUEST@&lists-host;, where debian-foo is the name of the list, with the word subscribe in the Subject to subscribe to the list or -unsubscribe to unsubscribe. More detailed instructions on -how to subscribe and unsubscribe to the mailing lists can be found at -, -or locally in &file-mail-lists; if you have the -doc-debian package installed. +unsubscribe to unsubscribe. +

+If you prefer to use a web page to subscribe to multiple mailing lists, +there's one at . +

+You can download the current list of mailing lists and basic usage +instructions from +or install the doc-debian package and have it +locally in &file-mail-lists;. + + Basic rules for use

When replying to messages on the mailing list, please do not send a carbon copy (CC) to the original poster unless they explicitly request to be copied. Anyone who posts to a mailing list should read it to see the responses.

-The following are the core Debian mailing lists: &email-debian-devel;, -&email-debian-policy;, &email-debian-user;, &email-debian-private;, -&email-debian-announce;, and &email-debian-devel-announce;. All -developers are expected to be subscribed to at least -&email-debian-devel-announce;. There are -other mailing lists available for a variety of special topics; see - for a list. Cross-posting -(sending the same message to multiple lists) is discouraged. +Cross-posting (sending the same message to multiple lists) is discouraged. +As ever on the net, please trim down the quoting of articles you're +replying to. In general, please adhere to the usual conventions for +posting messages. Please read the for more information. + + Special lists

&email-debian-private; is a special mailing list for private discussions amongst Debian developers. It is meant to be used for -posts which for whatever reason should not be published publically. +posts which for whatever reason should not be published publicly. As such, it is a low volume list, and users are urged not to use &email-debian-private; unless it is really necessary. Moreover, do not forward email from that list to anyone. Archives of this list are not available on the web for obvious reasons, but you can see -them using your shell account master.debian.org and looking +them using your shell account on lists.debian.org and looking in the ~debian/archive/debian-private directory.

&email-debian-email; is a special mailing list used as a grab-bag for Debian related correspondence such as contacting upstream authors about licenses, bugs, etc. or discussing the project with others where it might be useful to have the discussion archived somewhere. + + IRC channels

-As ever on the net, please trim down the quoting of articles you're -replying to. In general, please adhere to the usual conventions for -posting messages. +Several IRC channels are dedicated to Debian's development. They are all +hosted on the network. +The irc.debian.org DNS entry is just an alias to +irc.openprojects.net.

-Online archives of mailing lists are available at . +The main channel #debian-devel is very active since more +than 150 persons are always logged in. 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 +always full of interesting information. Since it's an open channel, you +should not speak there of issues that are discussed in +&email-debian-private;. There's a key protected channel +#debian-private for that purpose. The 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. +

+There are other additional channels dedicated to specific subjects. +#debian-bugs is used for coordinating bug squash parties. +#debian-boot is used to coordinate the work on the boot +floppies (i.e. the installer). #debian-doc is +occasionally used to work on documentation like the one you are +reading. Other channels are dedicated to an architecture or a set of +packages: #debian-bsd, #debian-kde, +#debian-sf (SourceForge package), #debian-oo (OpenOffice +package) ... +

+Some non-English channels exist, for example #debian-devel-fr for +French speaking people interested in Debian's development. + + + Documentation +

+This document contains a lot of information very useful to Debian developers, +but it can not contain everything. Most of the other interesting documents +are linked from . +Take the time to browse all the links, you will learn many more things. - Debian servers + Debian machines +

+Debian has several computers working as servers, most of which serve +critical functions in the Debian project. Most of the machines are used +for porting activities, and they all have a permanent connection to the +Internet. +

+Most of the machines are available for individual developers to use, +as long as the developers follow the rules set forth in the +. +

+Generally speaking, you can use these machines for Debian-related purposes +as you see fit. Please be kind to system administrators, and do not use +up tons and tons of disk space, network bandwidth, or CPU without first +getting the approval of the admins. Usually these machines are run by +volunteers.

-Debian servers are well known servers which serve critical functions -in the Debian project. Every developer should know what these servers -are and what they do. +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. +

+Please do not put any material that doesn't relate to Debian on the Debian +servers, unless you have prior permission. +

+The current list of Debian machines is available at +. That web page contains machine names, +contact information, information about who can log in, SSH keys 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, -please find the contact address for the particular machine at . If you have a non-operating problems -(such as packages to be remove, suggestions for the web site, etc.), +the Debian system administrator team is reachable at +debian-admin@lists.debian.org. +

+If you have a problem with a certain service, not related to the system +administration (such as packages to be removed from the archive, +suggestions for the web site, etc.), generally you'll report a bug against a ``pseudo-package''. See for information on how to submit bugs. - The master server + The bugs server

-master.debian.org is the canonical location for the Bug -Tracking System (BTS). 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 +bugs.debian.org is the canonical location for the Bug Tracking +System (BTS). 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 reduce unnecessary duplication of effort or wasted processing time.

-All Debian developers have accounts on master.debian.org. -Please take care to protect your password to this machine. Try to -avoid login or upload methods which send passwords over the Internet -in the clear. -

-If you find a problem with master.debian.org such as disk -full, suspicious activity, or whatever, send an email to -&email-debian-admin;. +All Debian developers have accounts on bugs.debian.org. The ftp-master server

-The ftp-master server, ftp-master.debian.org (or -auric.debian.org), holds the canonical copy of the Debian +The ftp-master.debian.org server holds the canonical copy of the Debian archive (excluding the non-US packages). Generally, package uploads go to this server; see .

@@ -485,34 +585,59 @@ bugs against the ftp.debian.org pseudo-package or an email to &email-ftpmaster;, but also see the procedures in . - The WWW server + The non-US server

-The main web server, www.debian.org, is also known as -klecker.debian.org. All developers are given accounts on this -machine. +The non-US server, non-us.debian.org, +holds the canonical copy of the non-US part of the Debian archive. +If you need to upload a package into one of the non-US sections, upload it +to this server; see .

-If you have some Debian-specific information which you want to serve -up on the web, you can do this by putting material in the -public_html directory under your home directory. You should -do this on klecker.debian.org. Any material you put in those areas -are accessible via the URL -http://people.debian.org/~user-id/. -You should only use this particular location because it will be backed up, -whereas on other hosts it won't. Please do not put any material on Debian -servers not relating to Debian, unless you have prior permission. -Send mail to &email-debian-devel; if you have any questions. +Problems with the non-US package archive should generally be submitted as +bugs against the nonus.debian.org pseudo-package (notice +the lack of hyphen between "non" and "us" in the pseudo-package name +— that's for backwards compatibility). Remember to check whether or +not someone else has already reported the problem on the +. + + The www-master server +

+The main web server is www-master.debian.org. +It holds the official web pages, the face +of Debian for most newbies.

If you find a problem with the Debian web server, you should generally submit a bug against the pseudo-package, -www.debian.org. First check whether or not someone +www.debian.org. Remember to check whether or not someone else has already reported the problem on the . + The people web server +

+people.debian.org is the server used +for developers' own web pages about anything related to Debian. +

+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/. +

+You should only use this particular location because it will be backed up, +whereas on other hosts it won't. +

+Usually the only reason to use a different host is when you need to publish +materials subject to the U.S. export restrictions, in which case you can use +one of the other servers located outside the United States, such as the +aforementioned non-us.debian.org. +

+Send mail to &email-debian-devel; if you have any questions. The CVS server

-cvs.debian.org is also known as klecker.debian.org, -discussed above. If you need to use a publically accessible CVS +Our CVS server is located on cvs.debian.org. +

+If you need to use a publicly accessible CVS server, for instance, to help coordinate work on a package between many different developers, you can request a CVS area on the server.

@@ -523,10 +648,21 @@ be accessed read-only via the Web at .

To request a CVS area, send a request via email to &email-debian-admin;. Include the name of the requested CVS area, -Debian account should own the CVS root area, and why you need it. +the Debian account that should own the CVS root area, and why you need it. + + + The Developers Database +

+The Developers Database, at , is an LDAP +directory for managing Debian developer attributes. You can use this +resource to search the list of Debian developers. For information on +keeping your entry the developer database up-to-date, see . Part of this information is also available through +the finger service on Debian servers, try +finger yourlogin@debian.org to see what it reports. - Mirrors of Debian servers + Mirrors of Debian servers

The web and FTP servers have several mirrors available. Please do not put heavy load on the canonical FTP or web servers. Ideally, the @@ -548,62 +684,42 @@ interested in helping Debian. As such, developers generally do not have accounts on these machines. - Other Debian Machines -

-There are other Debian machines which may be made available to you. -You can use these for Debian-related purposes as you see fit. Please -be kind to system administrators, and do not use up tons and tons of -disk space, network bandwidth, or CPU without first getting the -approval of the local maintainers. Usually these machines are run by -volunteers. Generally, these machines are for porting activities. -

-Aside from the servers mentioned in , there -is a list of machines available to Debian developers at . - - - - The Debian Archive - - Overview + The Debian archive

-The &debian-formal; distribution consists of a lot of Debian packages -(.deb's, currently around &number-of-pkgs;) and a few -additional files (documentation, installation disk images, etc.). +The &debian-formal; distribution consists of a lot of packages +(.deb's, currently around &number-of-pkgs;) and a few +additional files (such documentation and installation disk images).

Here is an example directory tree of a complete Debian archive:

&sample-dist-dirtree;

As you can see, the top-level directory contains two directories, -dists/ and pool/. The latter is a ``pool'' in which the +dists/ and pool/. The latter is a “pool” in which the packages actually are, and which is handled by the archive maintenance database and the accompanying programs. The former contains the distributions, stable, testing and unstable. -Each of those distribution directories is divided in equivalent -subdirectories purpose of which is equal, so we will only explain how it -looks in stable. The Packages and Sources files in the -distribution subdirectories can reference files in the pool/ -directory. +The Packages and Sources files in the +distribution subdirectories can reference files in the pool/ +directory. The directory tree below each of the distributions is arranged +in an identical manner. What we describe below for stable is +equally applicable to the unstable and testing +distributions.

-dists/stable contains three directories, namely main, -contrib, and non-free. +dists/stable contains three directories, namely main, +contrib, and non-free.

-In each of the areas, there is a directory with the source packages -(source), a directory for each supported architecture -(binary-i386, binary-m68k, etc.), and a directory -for architecture independent packages (binary-all). +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.).

-The main area contains additional directories which holds +The main area contains additional directories which holds the disk images and some essential pieces of documentation required for installing the Debian distribution on a specific architecture -(disks-i386, disks-m68k, etc.). -

-The binary-* and source directories are divided -further into subsections. +(disks-i386, disks-m68k, etc.). - Sections + Sections

The main section of the Debian archive is what makes up the official &debian-formal; distribution. The @@ -616,14 +732,14 @@ Every package in the main section must fully comply with the (DFSG) and with all other policy requirements as described in the . The DFSG is -our definition of ``free software.'' Check out the Debian Policy +our definition of “free software.” Check out the Debian Policy Manual for details.

Packages in the contrib section have to comply with the DFSG, but may fail other requirements. For instance, they may depend on non-free packages.

-Packages which do not apply to the DFSG are placed in the +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 infrastructure (such as our bug-tracking system and mailing @@ -646,7 +762,7 @@ many on the CD-ROMs as he's allowed to. (Since this varies greatly from vendor to vendor, this job can't be done by the Debian developers.) - Architectures + Architectures

In the first days, the Linux kernel was only available for the Intel i386 (or greater) platforms, and so was Debian. But when Linux became @@ -661,102 +777,101 @@ it should, too. Therefore, Debian has ports underway; in fact, we also have ports underway to non-Linux kernel. Aside from i386 (our name for Intel x86), there is m68k, alpha, powerpc, sparc, hurd-i386, -and arm, as of this writing. +arm, ia64, hppa, s390, mips, +mipsel and sh as of this writing.

&debian-formal; 1.3 is only available as i386. Debian 2.0 shipped for i386 and m68k architectures. Debian 2.1 ships for the i386, m68k, alpha, and -sparc architectures. Debian 2.2 adds support for the -powerpc and arm architectures. +sparc architectures. Debian 2.2 added support for the +powerpc and arm architectures. Debian 3.0 adds +support of five new architectures: ia64, hppa, +s390, mips and mipsel.

Information for developers or uses about the specific ports are available at the . - Subsections + - Packages + Packages

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. +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.

If a package is developed specially for Debian and is not distributed -outside of Debian, there is just one .tar.gz file which +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 +elsewhere too, the .orig.tar.gz file stores the so-called upstream source code, that is the source code that's distributed from the upstream maintainer (often the author of -the software). In this case, the .diff.gz contains the +the software). In this case, the .diff.gz contains the changes made by the Debian maintainer.

-The .dsc lists all the files in the source package together +The .dsc file lists all the files in the source package together with checksums (md5sums) and some additional info about the package (maintainer, version, etc.). - Distribution directories + Distribution directories

The directory system described in the previous chapter is itself contained within distribution directories. Each -distribution is actually contained in the pool directory in the +distribution is actually contained in the pool directory in the top-level of the Debian archive itself.

To summarize, the Debian archive has a root directory within an FTP server. For instance, at the mirror site, ftp.us.debian.org, the Debian archive itself is contained in /debian, which is a common location -(another is /pub/debian). +(another is /pub/debian).

A distribution is comprised of Debian source and binary packages, and the -respective Sources and Packages index files, containing +respective Sources and Packages index files, containing the header information from all those packages. The former are kept in the -pool/ directory, while the latter are kept in the dists/ -directory of the archive (because of backwards compatibility). +pool/ directory, while the latter are kept in the dists/ +directory of the archive (for backwards compatibility). - Stable, testing, and unstable + Stable, testing, and unstable

There are always distributions called stable (residing in -dists/stable), one called testing (residing in -dists/testing), and one called unstable (residing in -dists/unstable). This reflects the development process of the +dists/stable), one called testing (residing in +dists/testing), and one called unstable (residing in +dists/unstable). This reflects the 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 packages in this distribution at any time. Thus, the contents of this -distribution change from day-to-day. Since no special effort is done +distribution changes from day-to-day. Since no special effort is done to make sure everything in this distribution is working properly, it is -sometimes ``unstable.'' -

-Packages get copied from unstable to testing if they -satisfy certain criteria. To get into testing distribution, a -package needs to be in the archive for two weeks and not have any -release critical bugs. After that period, it will propagate into -testing as soon as anything it depends on is also added. This -process is automatic. You can see some notes on this system as well -as update_excuses (describing which packages are valid -candidates, which are not, and why not) at . +sometimes 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. + are launched each day after the +new packages have been installed.

After a period of development, once the release manager deems fit, the testing distribution is frozen, meaning that the policies @@ -765,7 +880,7 @@ tightened. Packages which are too buggy are removed. No changes are allowed into testing except for bug fixes. After some time has elapsed, depending on progress, the testing distribution goes into a `deep freeze', when no changes are made to it except those -needed for the installation system. This is called a ``test cycle'', +needed for the installation system. This is called a “test cycle”, and it can last up to two weeks. There can be several test cycles, until the distribution is prepared for release, as decided by the release manager. At the end of the last test cycle, the @@ -776,24 +891,25 @@ that time (although it can be found at &archive-host;). This development cycle is based on the assumption that the unstable distribution becomes stable after passing a period of being in testing. Even once a distribution is -considered stable, a few bugs inevitably remain &mdash that's why the +considered stable, a few bugs inevitably remain — that's why the stable distribution is updated every now and then. However, these updates are tested very carefully and have to be introduced into the archive individually to reduce the risk of introducing new bugs. You can find proposed additions to stable in the -proposed-updates directory. Those packages in -proposed-updates that pass muster are periodically moved as a +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., `1.3' becomes `1.3r1', -`2.0r2' becomes `2.0r3', and so forth). +stable distribution is incremented (e.g., ‘3.0’ becomes +‘3.0r1’, ‘2.2r4’ becomes ‘2.2r5’, and +so forth).

Note that development under unstable continues during the -``freeze'' period, since the unstable distribution remains in +freeze period, since the unstable distribution remains in place in parallel with testing. - Experimental + Experimental

-The experimental distribution is a specialty distribution. +The experimental distribution is a special distribution. It is not a full distribution in the same sense as `stable' 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 @@ -821,16 +937,19 @@ access. Some experimental software can still go into unstable, 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. +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 removed once you upload +the package in unstable with a higher version number.

New software which isn't likely to damage your system can go directly into unstable.

An alternative to experimental is to use your personal web space -on people.debian.org (klecker.debian.org). +on people.debian.org. - Release code names + 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, @@ -867,10 +986,331 @@ real distribution directories use the code names, while symbolic links for stable, testing, and unstable point to the appropriate release directories. + + The Incoming system +

+The Incoming system is responsible of collecting updated packages and +installing them in the Debian archive. It consists of a set of +directories and scripts that are installed both on &ftp-master-host; +and &non-us-host;. +

+Packages are uploaded by all the maintainers into a directory called +unchecked. This directory is scanned every 15 minutes by the katie script +that verifies the integrity of the uploaded packages and the cryptographic +signatures. If the package is considered ready to be installed, it +is moved into the accepted directory. If this is the first upload of +the package, it is moved in the new directory, where it waits +for an approval of the ftpmasters. If the package contains files to be installed +"by-hand" is is moved in the byhand directory, where it waits +for a manual installation by the ftpmasters. Otherwise, if any error has been detected, +the package is refused and is moved in the reject directory. +

+Once the package is accepted the system sends a confirmation +mail to the maintainer, 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 (there is no +such URL for packages in the non-US archive) until it is really installed +in the Debian archive. This happens only once a day, 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 Sources index files for example) have been +made, a special script is called to ask all the primary mirrors to update +themselves. +

+All debian developers have write access to the unchecked +directory in order to upload their packages, they also have that access +to the reject directory in order to remove their bad uploads +or to move some files back in the unchecked directory. But +all the other directories are only writable by the ftpmasters, that is +why you can not remove an upload once it has been accepted. + + Delayed incoming +

+The unchecked directory has a special DELAYED +subdirectory. It is itself subdivided in nine directories +called 1-day to 9-day. Packages which are uploaded in +one of those directories will be moved in the real unchecked +directory after the corresponding number of days. +This is done by a script that 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 in the +adjacent directory (for example, a package in 5-day will +be moved in 4-day). This feature is particularly useful +for people who are doing non-maintainer uploads. Instead of +waiting before uploading a NMU, it is uploaded as soon as it is +ready but in one of those DELAYED/x-day directories. +That leaves the corresponding number of days for the maintainer +to react and upload another fix themselves if they are not +completely satisfied with the NMU. Alternatively they can remove +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 +dupload (see ), you can add this +snippet to your configuration file: + +$delay = ($ENV{DELAY} || 7); +$cfg{'delayed'} = { + fqdn => "&ftp-master-host;", + login => "yourdebianlogin", + incoming => "/org/ftp.debian.org/incoming/DELAYED/$delay-day/", + dinstall_runs => 1, + method => "scpb" +}; + +Once you've made that change, dupload can be used to +easily upload a package in one of the delayed directories: +DELAY=5 dupload --to delayed <changes-file> + + + The testing scripts +

+The testing scripts are run each day after the installation of the +updated packages. They generate the Packages files for +the testing distribution, but they do so in an intelligent manner +trying to avoid any inconsistency and trying to use only +non-buggy packages. +

The inclusion of a package from unstable is conditional on the following: + + +The package must have been available in unstable for several days; +the precise number depends on the upload's urgency field. It +is 10 days for low urgency, 5 days for medium urgency and 2 days for high +urgency. Those delays may be doubled during a freeze; + +It must have less release-critical bugs than the version available +in testing; + +It must be available on all architectures on which it has been +previously built. may be of interest to +check that information; + +It must not break any dependency of a package that is already available +in testing; + +The packages on which it depends must either be available in testing +or they must be accepted into testing at the same time (and they will +if they respect themselves all the criteria); + +

+The scripts are generating some output files to explain why some packages +are kept out of testing. They are available at . Alternatively, it is possible to use +the grep-excuses program part of the +devscripts package. It can be easily put in a crontab +to keep someone informed of the progression of his packages in testing. +

+The update_excuses file does not always give the precise reason +why the package is refused, one may have to find it on their own by looking +what would break with the inclusion of the package. The gives some more information +about the usual problems which may be causing such troubles. +

+Sometimes, some packages never enter testing because the set of +inter-relationship is too complicated and can not be sorted out +by the scripts. In that case, the release manager must be +contacted, and he will force the inclusion of the packages. - Package uploads + Package's information +

+ + On the web +

+Each package has several dedicated web pages that contain a lot of +information. http://&packages-host;/package-name +will display each version of the package +available in the various distributions. The per-version detailed +information includes the package description, +the dependencies and links to download the package. +

+The bug tracking system sorts the bugs by package, you can +watch the bugs of each package at +http://&bugs-host;/package-name. - New packages + The madison utility +

+madison is a command-line utility that is available +on both &ftp-master-host; and &non-us-host;. 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. +

+ +$ 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 + +

+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 time the package has been +recompiled on most of the architectures. + + The Package Tracking System +

+The Package Tracking System (PTS) is basically a tool to track by mail +the activity of a source package. You just have to subscribe +to a source package to start getting the mails related to it. +You get the same mails than the maintainer. Each mail +sent through the PTS is classified and associated to one of +the keyword listed below. This will let you select the mails that +you want to receive. +

+By default you will get: + + bts + +All the bug reports and following discussions. + + bts-control + +The control mails notifying a status change in one of the bugs. + + upload-source + +The confirmation mail from katie when an uploaded source +package is accepted. + + katie-other + +Other warning and error mails from katie (like the +override disparity for the section or priority field). + + default + +Any non-automatic mail sent to the PTS by people who wanted to +contact the subscribers of the package. + + summary + +In the future, you may receive regular summary mails to keep you +informed of the package's status (bug statistics, porting overview, +progression in testing, ...). + +

+You can also decide to receive some more information: + + upload-binary + +The confirmation mail from katie when an uploaded binary +package is accepted (to check that your package is recompiled for all +architectures). + + cvs + +CVS commits if the maintainer has setup a system to forward commit +notification to the PTS. + + + The PTS email interface +

+You can control your subscription(s) to the PTS by sending +various commands to pts@qa.debian.org. + + + +subscribe <srcpackage> [<email>] + + Subscribes email to communications related to the source package + srcpackage. Sender address is used if the second argument is + not present. If srcpackage is not a valid source package, + you'll get a warning. However if it's a valid binary package, the PTS + will subscribe you to the corresponding source package. + +unsubscribe <srcpackage> [<email>] + + Removes a previous subscription to the source package srcpackage + using the specified email address or the sender address if the second + argument is left out. + +which [<email>] + + Lists all subscriptions for the sender or the email address optionally + specified. + +keyword [<email>] + + Tells you the keywords that you are accepting. Each mail sent through + the Package Tracking System is associated to a keyword and you receive + only the mails associated to keywords that you are accepting. Here is + the list of available keywords: + + bts: mails coming from the Debian Bug Tracking System + bts-control: reply to mails sent to + control@bugs.debian.org + summary: automatic summary mails about the state of a package + cvs: notification of CVS commits + upload-source: announce of a new source upload that + has been accepted + upload-binary: announce of a new binary-only upload (porting) + katie-other: other mails from ftpmasters + (override disparity, etc.) + default: all the other mails (those which aren't "automatic") + + +keyword <srcpackage> [<email>] + + Same as previous item but for the given source package since + you may select a different set of keywords for each source package. + +keyword [<email>] {+|-|=} <list of keywords> + + Accept (+) or refuse (-) mails associated to the given keyword(s). + Define the list (=) of accepted keywords. + +keyword <srcpackage> [<email>] {+|-|=} <list of keywords> + + Same as previous item but overrides the keywords list for the + indicated source package. + +quit | thanks | -- + + Stops processing commands. All following lines are ignored by + the bot. + + + Filtering PTS mails +

+Once you are subscribed to a package, you will get the mails sent to +srcpackage@packages.qa.debian.org. Those mails +have special headers appended to let you filter them in a special +mailbox with procmail. The added headers are +X-Loop, X-PTS-Package, X-PTS-Keyword and +X-Unsubscribe. +

+Here is an example of added headers for a source upload notification +on the dpkg package: + +X-Loop: dpkg@&pts-host; +X-PTS-Package: dpkg +X-PTS-Keyword: upload-source +X-Unsubscribe: echo 'unsubscribe dpkg' | mail pts@qa.debian.org + + + Forwarding CVS commits in the PTS +

+If you use a publicly accessible CVS repository for maintaining +your Debian package you may want to forward the commit notification +to the PTS so that the subscribers (possible co-maintainers) can +closely follow the package's evolution. +

+It's very easy to setup. Once your CVS repository generates commit +notifications, you just have to make sure it sends a copy of those mails +to srcpackage_cvs@&pts-host;. Only people who +accepts the cvs keyword will receive the notifications. + + + Managing Packages +

+This chapter contains information related to creating, uploading, +maintaining, and porting packages. + + Package uploads + + New packages

If you want to create a new package for the Debian distribution, you should first check the ) against the -pseudo package wnpp +pseudo-package wnpp describing your plan to create a new package, including, but not limiting yourself to, a description of the package, the license of the prospective package and the current URL where it can be downloaded @@ -922,29 +1362,29 @@ The announcements give maintainers and other interested parties a better feel of what is going on, and what is new, in the project. - + Adding an entry to debian/changelog

Changes that you make to the package need to be recorded in the debian/changelog. These changes should provide a concise description of what was changed, why (if it's in doubt), and note if -any bugs were closed. They also record when the packages was +any bugs were closed. They also record when the package was completed. This file will be installed in /usr/share/doc/package/changelog.Debian.gz, or /usr/share/doc/package/changelog.gz for native packages.

-The debian/changelog file conform to a certain structure, +The debian/changelog file conforms to a certain structure, with a number of different fields. One field of note, the distribution, is described in . More -information about the structure structure of this file can be found in +information about the structure of this file can be found in the Debian Policy section titled "debian/changelog".

Changelog entries can be used to automatically close Debian bugs when the package is installed into the archive. See .

-It is conventional that the changelog entry notating that the package +It is conventional that the changelog entry notating of a package that contains a new upstream version of the software looks like this: * new upstream version @@ -956,7 +1396,7 @@ and . - Checking the package prior to upload + Checking the package prior to upload

Before you upload your package, you should do basic testing on it. At a minimum, you should try the following activities (you'll need to @@ -981,16 +1421,16 @@ to emit errors (they will start with E). For more information on lintian, see . Downgrade the package to the previous version (if one exists) — this -tests the postrm and prerm scripts. +tests the postrm and prerm scripts. Remove the package, then reinstall it. - Generating the changes file + Generating the changes file

When a package is uploaded to the Debian FTP archive, it must be -accompanied by a .changes file, which gives directions to the +accompanied by a .changes file, which gives directions to the archive maintainers for its handling. This is usually generated by dpkg-genchanges during the normal package build process.

@@ -1005,31 +1445,28 @@ automatically using the Description field, see . - The original source tarball + The original source tarball

The first time a version is uploaded which corresponds to a particular upstream version, the original source tar file should be uploaded and -included in the .changes file. Subsequently, this very same -tar file should be used to build the new diffs and .dsc +included in the .changes file. Subsequently, this very same +tar file should be used to build the new diffs and .dsc files, and will not need to be re-uploaded.

By default, dpkg-genchanges and dpkg-buildpackage will include the original source tar file if and only if the Debian revision part of the source version -number is 0 or 1, indicating a new upstream version. This behaviour +number is 0 or 1, indicating a new upstream version. This behavior may be modified by using -sa to always include it or -sd to always leave it out.

If no original source is included in the upload, the original source tar-file used by dpkg-source when constructing the -.dsc file and diff to be uploaded must be -byte-for-byte identical with the one already in the archive. If there -is some reason why this is not the case, the new version of the -original source should be uploaded, possibly by using the -sa -flag. +.dsc file and diff to be uploaded must be +byte-for-byte identical with the one already in the archive. - Picking a distribution + Picking a distribution

The Distribution field, which originates from the first line of the debian/changelog file, indicates which distribution the @@ -1092,17 +1529,17 @@ fix. --> - Uploading to stable + Uploading to stable

Uploading to stable means that the package will be placed into the -proposed-updates directory of the Debian archive for further +proposed-updates directory of the Debian archive for further testing before it is actually included in stable.

Extra care should be taken when uploading to stable. Basically, a package should only be uploaded to stable if one of the following happens: a security problem (e.g. a Debian security advisory) - a truely critical functionality problem + a truly critical functionality problem the package becomes uninstallable a released architecture lacks the package @@ -1110,7 +1547,7 @@ package should only be uploaded to stable if one of the following happens: It is discouraged to change anything else in the package that isn't important, because even trivial fixes can cause bugs later on. Uploading new upstream versions to fix security problems is deprecated; applying the -specific patch from the new upstream version to the old one ("backporting" +specific patch from the new upstream version to the old one ("back-porting" the patch) is the right thing to do in most cases.

Packages uploaded to stable need to be compiled on systems running @@ -1130,57 +1567,56 @@ inclusion. - Uploading a package + Uploading a package - Uploading to ftp-master + Uploading to ftp-master

To upload a package, you need a personal account on -ftp-master.debian.org, which you should have as an +&ftp-master-host;, which you should have as an official maintainer. If you use scp or rsync -to transfer the files, place them into &us-upload-dir;; +to transfer the files, place them into &us-upload-dir;; if you use anonymous FTP to upload, place them into -/pub/UploadQueue/. Please note that you should transfer +&upload-queue;. Please note that you should transfer the changes file last. Otherwise, your upload may be rejected because the archive maintenance software will parse the changes file and see that not -all files have been uploaded. If you don't want to bother with transfering +all files have been uploaded. If you don't want to bother with transferring the changes file last, you can simply copy your files to a temporary directory on ftp-master and then move them to -&us-upload-dir;. +&us-upload-dir;.

-Note: Do not upload to ftp-master packages -containing software that is patent-restricted by the United States -government, any cryptographic packages which belong in -contrib or non-free. If you can't upload it to -ftp-master, then neither can you upload it to the overseas -upload queues on chiark or erlangen. Uploads of +Note: Do not upload to ftp-master cryptographic +packages which belong to contrib or non-free. Uploads of such software should go to non-us (see ). If you are not sure whether U.S. patent -controls or cryptographic controls apply to your package, post a -message to &email-debian-devel; and ask. -

-You may also find the Debian packages dupload or -dput useful -when uploading packages. These handy program are distributed with -defaults for uploading via ftp to ftp-master, -chiark, and erlangen. It can also be configured to -use ssh or rsync. See , and for more information. -

-After uploading your package, you can check how the archive maintenance -software will process it by running dinstall on your changes -file: dinstall -n foo.changes - - Uploading to non-US (pandora) +id="upload-non-us">). Furthermore packages containing code that is +patent-restricted by the United States government can not be uploaded to +ftp-master; depending on the case they may still be uploaded to +non-US/non-free (it's in non-free because of distribution issues +and not because of the license of the software). If you can't upload it to +ftp-master, then neither can you upload it to the overseas upload +queues on chiark or erlangen. If you are not sure +whether U.S. patent controls or cryptographic controls apply to your +package, post a message to &email-debian-devel; and ask. +

+You may also find the Debian packages or + useful +when uploading packages. These handy programs help automate the +process of uploading packages into Debian. +

+After uploading your package, you can check how the archive +maintenance software will process it by running dinstall +on your changes file: dinstall -n foo.changes. +Note that dput can do this for you automatically. + + Uploading to non-US

As discussed above, export controlled software should not be uploaded to ftp-master. Instead, upload the package to non-us.debian.org, placing the files in -&non-us-upload-dir; (both and can be used also, with the right invokation). By default, +&non-us-upload-dir; (again, both and can do this for you if invoked properly). By default, you can use the same account/password that works on ftp-master. If you use anonymous FTP to upload, place the -files into /pub/UploadQueue/. +files into &upload-queue;.

You can check your upload the same way it's done on ftp-master, with: @@ -1194,8 +1630,8 @@ restriction has been waived for software which is already available outside the U.S. Therefore, any cryptographic software which belongs in the main section of the Debian archive and does not depend on any package outside of main (e.g., does not depend on -anything in non-US/main) can be uploaded to ftp-master or its -queues, described above. +anything in non-US/main) can be uploaded to ftp-master +or its queues, described above.

Debian policy does not prevent upload to non-US by U.S. residents or citizens, but care should be taken in doing so. It is recommended that @@ -1215,10 +1651,10 @@ advice. Again, it is strongly recommended that U.S. citizens and residents consult a lawyer before doing uploads to non-US. - Uploads via chiark + Uploads via chiark

If you have a slow network connection to ftp-master, there are -alternatives. One is to upload files to Incoming via a +alternatives. One is to upload files to Incoming via a upload queue in Europe on chiark. For details connect to .

@@ -1232,18 +1668,18 @@ The program dupload comes with support for uploading to program for details. - Uploads via erlangen + Uploads via erlangen

Another upload queue is available in Germany: just upload the files via anonymous FTP to .

The upload must be a complete Debian upload, as you would put it into -ftp-master's Incoming, i.e., a .changes files -along with the other files mentioned in the .changes. The -queue daemon also checks that the .changes is correctly -PGP-signed by a Debian developer, so that no bogus files can find +ftp-master's Incoming, i.e., a .changes files +along with the other files mentioned in the .changes. The +queue daemon also checks that the .changes is correctly +signed with GnuPG or OpenPGP by a Debian developer, so that no bogus files can find their way to ftp-master via this queue. Please also make sure that -the Maintainer field in the .changes contains +the Maintainer field in the .changes contains your e-mail address. The address found there is used for all replies, just as on ftp-master.

@@ -1263,7 +1699,7 @@ The program dupload comes with support for uploading to the program for details. - Other Upload Queues + Other upload queues

Another upload queue is available which is based in the US, and is a good backup when there are problems reaching ftp-master. You can @@ -1275,14 +1711,14 @@ anonymous FTP to . - Announcing package uploads + Announcing package uploads

When a package is uploaded, an announcement should be posted to one of the ``debian-changes'' lists. This is now done automatically by the archive maintenance software when it runs (usually once a day). You just need to use a recent dpkg-dev (>= 1.4.1.2). The mail generated by -the archive maintenance software will contain the PGP/GPG signed -.changes files that you uploaded with your package. +the archive maintenance software will contain the OpenPGP/GnuPG signed +.changes files that you uploaded with your package. Previously, dupload used to send those announcements, so please make sure that you configured your dupload not to send those announcements (check its documentation and look for @@ -1293,12 +1729,8 @@ If a package is released with the Distribution: set to package is released with Distribution: set to `unstable', or `experimental', the announcement will be posted to &email-debian-devel-changes; instead. -

-The dupload program is clever enough to determine -where the announcement should go, and will automatically mail the -announcement to the right list. See . - + Notification that a new package has been installed

The Debian archive maintainers are responsible for handling package @@ -1311,8 +1743,8 @@ distribution is handled manually. When uploads are handled manually, the change to the archive may take up to a month to occur. Please be patient.

-In any case, you will receive email notification indicating that the -package has added to the archive, which also indicates which bugs will +In any case, you will receive an email notification indicating that the +package has been added to the archive, which also indicates which bugs will be closed by the upload. Please examine this notification carefully, checking if any bugs you meant to close didn't get triggered.

@@ -1320,7 +1752,7 @@ The installation notification also includes information on what section the package was inserted into. If there is a disparity, you will receive a separate email notifying you of that. Read on below. - The override file + The override file

The debian/control file's Section and Priority fields do not actually specify where the file will @@ -1351,16 +1783,16 @@ name="dpkg-scanpackages" section="8">, &file-bts-mailing;, and - Non-Maintainer Uploads (NMUs) + Non-Maintainer Uploads (NMUs)

Under certain circumstances it is necessary for someone other than the official package maintainer to make a release of a package. This is called a non-maintainer upload, or NMU.

-Debian porters, who compile packages for different architectures, do -NMUs as part of their normal porting activity (see ). Another reason why NMUs are done is when a Debian -developers needs to fix another developers' packages in order to +Debian porters, who compile packages for different architectures, +occasionally do binary-only NMUs as part of their porting activity +(see ). Another reason why NMUs are done is when a +Debian developers needs to fix another developers' packages in order to address serious security problems or crippling bugs, especially during the freeze, or when the package maintainer is unable to release a fix in a timely fashion. @@ -1369,7 +1801,7 @@ This chapter contains information providing guidelines for when and how NMUs should be done. A fundamental distinction is made between source and binary-only NMUs, which is explained in the next section. - Terminology + Terminology

There are two new terms used throughout this section: ``binary-only NMU'' and ``source NMU''. These terms are used with specific technical @@ -1384,8 +1816,7 @@ Source NMUs always involves changes to the source (even if it is just a change to debian/changelog). This can be either a change to the upstream source, or a change to the Debian bits of the source. Note, however, that source NMUs may also include -architecture-dependent packages, as well as an updated Debian diff -(or, more rarely, new upstream source as well). +architecture-dependent packages, as well as an updated Debian diff.

A binary-only NMU is a recompilation and upload of a binary package for a given architecture. As such, it is usually part of a porting @@ -1404,7 +1835,7 @@ we refer to any type of non-maintainer upload NMUs, whether source and binary, or binary-only. - Who can do an NMU + Who can do an NMU

Only official, registered Debian maintainers can do binary or source NMUs. An official maintainer is someone who has their key in the @@ -1415,7 +1846,7 @@ to the Bug Tracking System. Maintainers almost always appreciate quality patches and bug reports. - When to do a source NMU + When to do a source NMU

Guidelines for when to do a source NMU depend on the target distribution, i.e., stable, unstable, or experimental. Porters have @@ -1438,37 +1869,36 @@ for the problem. As with any source NMU, the guidelines found in need to be followed.

Bug fixes to unstable by non-maintainers are also acceptable, but only -as a last resort or with permission. Try the following steps first, -and if they don't work, it is probably OK to do an NMU: +as a last resort or with permission. The following protocol should +be respected to do an NMU:

-Make sure that the package bug is in the Debian Bug Tracking System -(BTS). If not, submit a bug. - -Email the maintainer, and offer to help fix the package bug. Give it a -few days. +Make sure that the package's bug is in the Debian Bug Tracking System +(BTS). If not, submit a bug. -Go ahead and fix the bug, submitting a patch to the right bug in the -BTS. Build the package and test it as discussed in . Use it locally. - -Wait a couple of weeks for a response. - -Email the maintainer, asking if it is OK to do an NMU. +Wait a few days the response from the maintainer. If you don't get +any response, you may want to help him by sending the patch that fixes +the bug. Don't forget to tag the bug with the "patch" keyword. +Wait a few more days. If you still haven't got an answer from the +maintainer, send him a mail announcing your intent to NMU the package. +Prepare an NMU as described in , test it +carefully on your machine (cf. ). Double check that your patch doesn't have any unexpected side effects. -Make sure your patch is as small and as non-disruptive as it can be. +Make sure your patch is as small and as non-disruptive as it can be. -Wait another week for a response. +Upload your package to incoming in DELAYED/7-day (cf. +), send the final patch to the maintainer via +the BTS, and explain to them that they have 7 days to react if they want +to cancel the NMU. -Go ahead and do the source NMU, as described in . +Follow what happens, you're responsible for any bug that you introduced +with your NMU. You should probably use (PTS) +to stay informed of the state of the package after your NMU. - - - How to do a source NMU + How to do a source NMU

The following applies to porters insofar as they are playing the dual role of being both package bug-fixers and package porters. If a @@ -1487,7 +1917,7 @@ However, aesthetic changes must not be made in a non-maintainer upload. - Source NMU version numbering + Source NMU version numbering

Whenever you have made a change to a package, no matter how trivial, the version number needs to change. This enables our packing system @@ -1514,51 +1944,37 @@ absolutely necessary for someone other than the usual maintainer to make a release based on a new upstream version then the person making the release should start with the debian-revision value `0.1'. The usual maintainer of a package should start their -debian-revision numbering at `1'. Note that if you do -this, you'll have to invoke dpkg-buildpackage with the --sa switch to force the build system to pick up the new -source package (normally it only looks for Debian revisions of '0' or -'1' — it's not yet clever enough to know about `0.1'). -

-Remember, porters who are simply recompiling a package for a different -architecture do not need to renumber. Porters should use new version -numbers if and only if they actually have to modify the source package -in some way, i.e., if they are doing a source NMU and not a binary -NMU. +debian-revision numbering at `1'. - + Source NMUs must have a new changelog entry

A non-maintainer doing a source NMU must create a changelog entry, describing which bugs are fixed by the NMU, and generally why the NMU was required and what it fixed. The changelog entry will have the non-maintainer's email address in the log entry and the NMU version -number in it.

+number in it.

By convention, source NMU changelog entries start with the line * Non-maintainer upload -

+ - Source NMUs and the Bug Tracking System + Source NMUs and the Bug Tracking System

Maintainers other than the official package maintainer should make as few changes to the package as possible, and they should always send a patch as a unified context diff (diff -u) detailing their changes to the Bug Tracking System.

-What if you are simply recompiling the package? In this case, the -process is different for porters than it is for non-porters, as -mentioned above. If you are not a porter and are doing an NMU that -simply requires a recompile (i.e., a new shared library is available -to be linked against, a bug was fixed in -debhelper), there must still be a changelog entry; -therefore, there will be a patch. If you are a porter, you are -probably just doing a binary-only NMU. (Note: this leaves out in the cold -porters who have to do recompiles — chalk it up as a weakness in how -we maintain our archive.) +What if you are simply recompiling the package? If you just need to +recompile it for a single architecture, then you may do a binary-only +NMU as described in which doesn't require any +patch to be sent. If you want the package to be recompiled for all +architectures, then you do a source NMU as usual and you will have to +send a patch.

If the source NMU (non-maintainer upload) fixes some existing bugs, these bugs should be tagged fixed in the Bug Tracking @@ -1575,35 +1991,51 @@ changes in the NMU are incorporated officially into the package by the official package maintainer.

Also, after doing an NMU, you have to open a new bug and include a -patch showing all the changes you have made. The normal maintainer -will either apply the patch or employ an alternate method of fixing -the problem. Sometimes bugs are fixed independently upstream, which -is another good reason to back out an NMU's patch. If the maintainer -decides not to apply the NMU's patch but to release a new version, -the maintainer needs to ensure that the new upstream version really -fixes each problem that was fixed in the non-maintainer release. +patch showing all the changes you have made. Alternatively you can send +that information to the existing bugs that are fixed by your NMU. +The normal maintainer will either apply the patch or employ an alternate +method of fixing the problem. Sometimes bugs are fixed independently +upstream, which is another good reason to back out an NMU's patch. +If the maintainer decides not to apply the NMU's patch but to release a +new version, the maintainer needs to ensure that the new upstream version +really fixes each problem that was fixed in the non-maintainer release.

In addition, the normal maintainer should always retain the entry in the changelog file documenting the non-maintainer upload. - Building source NMUs + Building source NMUs

Source NMU packages are built normally. Pick a distribution using the same rules as found in . Just as described in , a normal changes file, etc., will be built. In -fact, all the prescriptions from apply, including -the need to announce the NMU to the proper lists. +fact, all the prescriptions from apply.

Make sure you do not change the value of the maintainer in the debian/control file. Your name as given in the NMU entry of the debian/changelog file will be used for signing the changes file. + Acknowledging an NMU +

+If one of your packages has been NMUed, you have to incorporate the +changes in your copy of the sources. This is easy, you just have +to apply the patch that has been sent to you. Once this is done, you +have to close the bugs that have been tagged fixed by the NMU. You +can either close them manually by sending the required mails to the +BTS or by adding the required closes: #nnnn in the changelog +entry of your next upload. +

+In any case, you should not be upset by the NMU. An NMU is not a +personal attack against the maintainer. It is a proof that +someone cares enough about the package and that they were willing to help +you in your work, so you should be thankful. You may also want to +ask them if they would be interested to help you on a more frequent +basis as co-maintainer or backup maintainer +(see ). - - Porting and Being Ported + Porting and Being Ported

Debian supports an ever-increasing number of architectures. Even if you are not a porter, and you don't use any architecture but one, it @@ -1616,11 +2048,11 @@ is different from the original architecture of the package maintainer's binary package. It is a unique and essential activity. In fact, porters do most of the actual compiling of Debian packages. For instance, for a single i386 binary package, there must be -a recompile for each architecture, which is amounts to +a recompile for each architecture, which amounts to &number-of-arches; more builds. - Being Kind to Porters + Being kind to porters

Porters have a difficult and unique task, since they are required to deal with a large volume of packages. Ideally, every source package @@ -1647,9 +2079,11 @@ are set properly. The best way to validate this is to use the debootstrap package to create an unstable chroot environment. Within that chrooted environment, install the build-essential package and any package -dependancies mention in Build-Depends and/or +dependencies mentioned in Build-Depends and/or Build-Depends-Indep. Finally, try building your package -within that chrooted environment. +within that chrooted environment. These steps can be automated +by the use of the pbuilder program which is provided by +the package of the same name.

See the for instructions on setting build dependencies. @@ -1662,7 +2096,7 @@ Manual">. Setting your architecture to ``i386'' is usually incorrect. Make sure your source package is correct. Do dpkg-source -x package.dsc to make sure your source package unpacks properly. Then, in there, try building your package from scratch with -dpkg-buildpackage. +dpkg-buildpackage. Make sure you don't ship your source package with the debian/files or debian/substvars files. @@ -1684,43 +2118,46 @@ although you are probably asking for trouble, since different architectures sometimes standardize on different compilers. Make sure your debian/rules contains separate ``binary-arch'' and -``binary-indep'' targets, as the Debian Packaging Manual requires. +``binary-indep'' targets, as the Debian Policy Manual requires. Make sure that both targets work independently, that is, that you can call the target without having called the other before. To test this, try to run dpkg-buildpackage -b. - Guidelines for Porter Uploads + Guidelines for porter uploads

If the package builds out of the box for the architecture to be ported to, you are in luck and your job is easy. This section applies to -that case; it describes how to build and upload your binary-only NMU so +that case; it describes how to build and upload your binary package so that it is properly installed into the archive. If you do have to patch the package in order to get it to compile for the other architecture, you are actually doing a source NMU, so consult instead.

-In a binary-only NMU, no real changes are being made to the source. You do +For a porter upload, no changes are being made to the source. You do not need to touch any of the files in the source package. This includes debian/changelog.

The way to invoke dpkg-buildpackage is as -dpkg-buildpackage -B -eporter-email. Of course, +dpkg-buildpackage -B -mporter-email. Of course, set porter-email to your email address. This will do a -binary-only build of only the architecture-dependant portions of the +binary-only build of only the architecture-dependent portions of the package, using the `binary-arch' target in debian/rules. - - Recompilation Binary-Only NMU Versioning + + Recompilation or binary-only NMU

-Sometimes you need to recompile a package against other packages which -have been updated, such as libraries. You do have to bump the version -number in this case, so that the version comparison system can -function properly. Even so, these are considered binary-only NMUs -— there is no need in this case to trigger all other -architectures to consider themselves out of date or requiring -recompilation. +Sometimes the initial porter upload is problematic because the environment +in which the package was built was not good enough (outdated or obsolete +library, bad compiler, ...). Then you may just need to recompile it in +an updated environment. However, you have to bump the version number in +this case, so that the old bad package can be replaced in the Debian archive +(katie refuses to install new packages if they don't have a +version number greater than the currently available one). Despite the +required modification of the changelog, these are called binary-only NMUs +— there is no need in this case to trigger all other architectures +to consider themselves out of date or requiring recompilation.

Such recompilations require special ``magic'' version numbering, so that the archive maintenance tools recognize that, even though there is a @@ -1736,7 +2173,7 @@ latest version was ``3.4-2.1'', your NMU should have a version number of ``3.4-2.1.1''. - + When to do a source NMU if you are a porter

Porters doing a source NMU generally follow the guidelines found in @@ -1757,7 +2194,7 @@ uploaded with no waiting period for the `frozen' distribution.

However, if you are a porter doing an NMU for `unstable', the above guidelines for porting should be followed, with two variations. -Firstly, the acceptable waiting period &mdash the time between when the +Firstly, the acceptable waiting period — the time between when the bug is submitted to the BTS and when it is OK to do an NMU — is seven days for porters working on the unstable distribution. This period can be shortened if the problem is critical and imposes hardship on @@ -1785,14 +2222,14 @@ the waiting period. Of course, such locations have no official blessing or status, so buyer, beware. - Tools for Porters + Tools for porters

There are several tools available for the porting effort. This section contains a brief introduction to these tools; see the package documentation or references for full information. - + quinn-diff

quinn-diff is used to locate the differences from @@ -1801,7 +2238,7 @@ packages need to be ported for architecture Y, based on architecture X. - + buildd

The buildd system is used as a distributed, @@ -1810,7 +2247,7 @@ conjunction with auto-builders, which are ``slave'' hosts which simply check out and attempt to auto-build packages which need to be ported. There is also an email interface to the system, which allows porters to ``check out'' a source package (usually one which -cannot yet be autobuilt) and work on it. +cannot yet be auto-built) and work on it.

buildd is not yet available as a package; however, most porting efforts are either using it currently or planning to use @@ -1833,7 +2270,7 @@ bounds checking). It will also enable Debian to recompile entire distributions quickly. - + dpkg-cross

dpkg-cross is a tool for installing libraries and @@ -1843,18 +2280,54 @@ headers for cross-compiling in a way similar to enhanced to support cross-compiling. - - - + + Collaborative maintenance +

+"Collaborative maintenance" is a term describing the sharing of Debian +package maintenance duties by several people. This collaboration is +almost a good idea, since it generally results in higher quality and +faster bug fix turnaround time. It is strongly recommended that +packages in which a priority of Standard or which are part of +the base set have co-maintainers.

+

+Generally there is a primary maintainer and one or more +co-maintainers. The primary maintainer is the whose name is listed in +the Maintainer field of the debian/control file. +Co-maintainers are all the other maintainers.

+

+In its most basic form, the process of adding a new co-maintainer is +quite easy: + +

+Setup the co-maintainer with access to the sources you build the +package from. Generally this implies you are using a network-capable +version control system, such as CVS or +Subversion.

+ + +

+Add the co-maintainer's correct maintainer name and address to the +Uploaders field in the global part of the +debian/control file.

+ + +

+Using the PTS (), the co-maintainers +should subscribe themselves to the appropriate source package.

+ +

+ + + Moving, Removing, Renaming, Adopting, and Orphaning Packages

-Some archive manipulation operation are not automated in the Debian +Some archive manipulation operations are not automated in the Debian upload process. These procedures should be manually followed by maintainers. This chapter gives guidelines in what to do in these cases. - Moving packages + Moving packages

Sometimes a package will change its section. For instance, a package from the `non-free' section might be GPL'd in a later version, @@ -1867,27 +2340,37 @@ belongs in. If you need to change the section for one of your packages, change the package control information to place the package in the desired section, and re-upload the package (see the for details). Carefully examine the -installation log sent to you when the package is installed into the -archive. If for some reason the old location of the package remains, -file a bug against ftp.debian.org asking that the old -location be removed. Give details on what you did, since it might be -a bug in the archive maintenance software. +name="Debian Policy Manual"> for details). If your new section is +valid, it will be moved automatically. If it does not, then contact +the ftpmasters in order to understand what happened.

If, on the other hand, you need to change the subsection of one of your packages (e.g., ``devel'', ``admin''), the procedure is slightly different. Correct the subsection as found in the control -file of the package, and reupload that. Also, you'll need to get the +file of the package, and re-upload that. Also, you'll need to get the override file updated, as described in . - Removing packages + Removing packages

If for some reason you want to completely remove a package (say, if it -is an old compatibility library which is not longer required), you +is an old compatibility library which is no longer required), you need to file a bug against ftp.debian.org asking that the package be removed. Make sure you indicate which distribution the -package should be removed from. +package should be removed from. Normally, you can only have packages +removed from unstable and experimental. Packages +are not removed from testing directly. Rather, they will be +removed automatically after the package has been removed from +unstable and no package in testing depends on it. +

+You also have to detail the reasons justifying that request. This is to +avoid unwanted removals and to keep a trace of why a package has been +removed. For example, you can provide the name of the package that +supersedes the one to be removed. +

+Usually you only ask the removal of a package maintained by yourself. +If you want to remove another package, you have to get the approval +of its last maintainer.

If in doubt concerning whether a package is disposable, email &email-debian-devel; asking for opinions. Also of interest is the @@ -1895,11 +2378,17 @@ If in doubt concerning whether a package is disposable, email package. When invoked as apt-cache showpkg package, the program will show details for package, including reverse depends. +

+Once the package has been removed, the package's bugs should be handled. +They should either be reassigned to another package in the case where +the actual code has evolved into another package (e.g. libfoo12 +was removed because libfoo13 supersedes it) or closed if the +software is simply no more part of Debian. - Removing packages from Incoming + Removing packages from Incoming

-In the past, it was possible to remove packages from incoming. -With the introduction of the New Incoming system this is no longer +In the past, it was possible to remove packages from incoming. +However, with the introduction of the new incoming system, this is no longer possible. Instead, you have to upload a new revision of your package with a higher version as the package you want to replace. Both versions will be installed in the archive but only the higher version will actually be @@ -1907,7 +2396,7 @@ available in unstable since the previous version will immediately be replaced by the higher. However, if you do proper testing of your packages, the need to replace a package should not occur too often anyway. - Replacing or renaming packages + Replacing or renaming packages

Sometimes you made a mistake naming the package and you need to rename it. In this case, you need to follow a two-step process. First, set @@ -1916,13 +2405,14 @@ obsolete name of the package (see the for details). Once you've uploaded that package, and the package has moved into the archive, file a bug against ftp.debian.org asking to remove the package with the -obsolete name. +obsolete name. Do not forget to properly reassign the package's bugs +at the same time. - Orphaning a package + Orphaning a package

If you can no longer maintain a package, you need to inform the others about that, and see that the package is marked as orphaned. -you should set the package maintainer to Debian QA Group +You should set the package maintainer to Debian QA Group &orphan-address; and submit a bug report against the pseudo package wnpp. The bug report should be titled O: package -- short description @@ -1933,15 +2423,16 @@ of the message (no, don't use CC:, because that way the message's subject won't indicate the bug number).

If the package is especially crucial to Debian, you should instead submit -a bug against wnpp and title it RFA: package -- +a bug against wnpp and title it RFA: package -- short description and set its severity to -important. Definitely copy the message to debian-devel in this -case, as described above. +important. RFA stands for Request For Adoption. +Definitely copy the message to debian-devel in this case, as described +above.

Read instructions on the for more information. - Adopting a package + Adopting a package

A list of packages in need of a new maintainer is available at in the ).

If you take over an old package, you probably want to be listed as the package's official maintainer in the bug system. This will happen automatically once you upload a new version with an updated Maintainer: field, although it can take a few hours after the upload is done. If you do not expect to upload a new version for a while, -send an email to &email-override; so that bug reports will go to you -right away. +you can use to get the bug reports. However, +make sure that the old maintainer has no problem with the fact that +they will continue to receive the bugs during that time. + Handling package bugs +

+Often as a package maintainer, you find bugs in other packages or else +have bugs reported to your packages which need to be reassigned. The + can tell you how +to do this. Some information on filing bugs can be found in . - Handling Bugs - - Monitoring bugs + Monitoring bugs

If you want to be a good maintainer, you should periodically check the for your packages. The BTS contains all the open bugs against your packages. +You can check them by browsing this page: +http://&bugs-host;/yourlogin@debian.org.

Maintainers interact with the BTS via email addresses at -bugs.debian.org. Documentation on available commands can be +&bugs-host;. Documentation on available commands can be found at , or, if you have installed the doc-debian package, you can look at the local files &file-bts-docs;. @@ -1988,40 +2488,109 @@ outlining all the open bugs against your packages: # ask for weekly reports of bugs in my packages &cron-bug-report; -Replace address with you official Debian +Replace address with your official Debian maintainer address. - Submitting Bugs -

-Often as a package maintainer, you find bugs in other packages or else -have bugs reported to your packages which need to be reassigned. The - can tell you how -to do this. -

-We encourage you to file bugs when there are problems. Try to submit -the bug from a normal user account at which you are likely to receive -mail. Do not submit bugs as root. -

-Make sure the bug is not already filed against a package. Try to do a -good job reporting a bug and redirecting it to the proper location. -For extra credit, you can go through other packages, merging bugs -which are reported more than once, or setting bug severities to -`fixed' when they have already been fixed. Note that when you are -neither the bug submitter nor the package maintainer, you should -not actually close the bug (unless you secure permission from the -maintainer). - - Responding to Bugs + Responding to bugs

-Make sure that any discussions you have about bugs are sent both to +Make sure that any discussion you have about bugs are sent both to the original submitter of the bug, and the bug itself (e.g., +123@bugs.debian.org). If you're writing a new +mail and you don't remember the submitter email address, you can +use the 123-submitter@bugs.debian.org email to +contact the submitter and to record your mail within the +bug log (that means you don't need to send a copy of the mail to 123@bugs.debian.org).

-You should never close bugs via the bug server `close' +You should never close bugs via the bug server close command sent to &email-bts-control;. If you do so, the original -submitter will not receive any feedback on why the bug was closed. - - When bugs are closed by new uploads +submitter will not receive any information about why the bug was +closed. + + Bug housekeeping +

+As a package maintainer, you will often find bugs in other packages or +have bugs reported against your packages which are actually bugs in +other packages. The document the technical operations of the BTS, such as +how to file, reassign, merge, and tag bugs. This section contains +some guidelines for managing your own bugs, based on the collective +Debian developer experience. +

+Filing bugs for problems that you find in other packages is one of +the "civic obligations" of maintainership, see +for details. However handling the bugs on your own packages is +even more important. +

+Here's a list of steps that you may follow to handle a bug report: + + +Decide whether the report corresponds to a real bug or not. Sometimes +users are just calling a program in the wrong way because they haven't +read the documentation. If you diagnose this, just close the bug with +enough information to let the user correct his problem (give pointers +to the good documentation and so on). If the same report comes up +again and again you may ask yourself if the documentation is good +enough or if the program shouldn't detect its misuse in order to +give an informative error message. This is an issue that may need +to be brought to the upstream author. +

+If the bug submitter disagree with your decision to close the bug, +they may reopen it until you find an agreement on how to handle it. +If you don't find any, you may want to tag the bug wontfix +to let people know that the bug exists but that it won't be corrected. +If this situation is unacceptable, you (or the submitter) may want to +require a decision of the technical committee by reassigning the bug +to tech-ctte (you may use the clone command of +the BTS if you wish to keep it reported against your package). + + +If the bug is real but it's caused by another package, just reassign +the bug the right package. If you don't know which package it should +be reassigned to, you may either ask for help on &email-debian-devel; or +reassign it to debian-policy to let them decide which +package is in fault. +

+Sometimes you also have to adjust the severity of the bug so that it +matches our definition of the severity. That's because people tend to +inflate the severity of bugs to make sure their bugs are fixed quickly. +Some bugs may even be dropped to wishlist severity when the requested +change is just cosmetic. + +The bug submitter may have forgotten to provide some information, in that +case you have to ask him the information required. You may use the +moreinfo tag to mark the bug as such. Moreover if you can't +reproduce the bug, you tag it unreproducible. Anyone who +can reproduce the bug is then invited to provide more information +on how to reproduce it. After a few months, if this information has not +been sent by someone, the bug may be closed. + +If the bug is related to the packaging, you just fix it. If you are not +able to fix it yourself, then tag the bug as help. You can +also ask for help on &email-debian-devel; or &email-debian-qa;. If it's an +upstream problem, you have to forward it to the upstream author. +Forwarding a bug is not enough, you have to check at each release if +the bug has been fixed or not. If it has, you just close it, otherwise +you have to remind the author about it. If you have the required skills +you can prepare a patch that fixes the bug and that you send at the +same time to the author. Make sure to send the patch in the BTS and to +tag the bug as patch. + +If you have fixed a bug in your local copy, or if a fix has been +committed to the CVS repository, you may tag the bug as +pending to let people know that the bug is corrected and that +it will be closed with the next upload (add the closes: in +the changelog). This is particularly useful if you +are several developers working on the same package. + +Once a corrected package is available in the unstable +distribution, you can close the bug. This can be done automatically, +read . + + + + When bugs are closed by new uploads

If you fix a bug in your packages, it is your responsibility as the package maintainer to close the bug when it has been fixed. However, @@ -2040,7 +2609,7 @@ acme-cannon (3.1415) unstable; urgency=low * Frobbed with options (closes: Bug#98339) * Added safety to prevent operator dismemberment, closes: bug#98765, bug#98713, #98714. - * Added manpage. Closes: #98725. + * Added man page. Closes: #98725. Technically speaking, the following Perl regular expression is what is @@ -2049,16 +2618,17 @@ used: /closes:\s*(?:bug)?\#\s*\d+(?:,\s*(?:bug)?\#\s*\d+)*/ig -The author prefers the (closes: Bug#XXX) syntax, -since it stands out from the rest of the changelog entries. +The author prefers the closes: #XXX syntax, as +one of the most concise and easiest to integrate with the text of the +changelog.

If you want to close bugs the old fashioned, manual way, it is usually -sufficient to mail the .changes file to +sufficient to mail the .changes file to XXX-done@bugs.debian.org, where XXX is your bug number. - Lintian reports + Lintian reports

You should periodically get the new lintian from `unstable' and check over all your packages. Alternatively you can @@ -2069,10 +2639,272 @@ latest version of the distribution (usually from 'unstable') using the latest lintian. - Reporting lots of bugs at once + + Best Packaging Practices +

+Debian's quality is largely due to its Policy that all packages +follow. But it's also because we accumulated years of experience +in packaging; very talented people created great tools to make +good packages without much troubles. +

+This chapter provides the best known solutions to common problems +faced during packaging. It also lists various advice collected on +several mailing lists. By following them, you will make Debian's quality +even better. + + + Packaging tools and common cases + + Helper scripts +

+To help you in your packaging effort, you can use helper scripts. +The best scripts available are provided by debhelper. +With dh_make (package dh-make), you can +generate in a few seconds a package that is mostly ready. However that +apparent simplicity is hiding many things done by the helper scripts. +You have to know what is done by them, that's why you are strongly +encouraged to read the corresponding manual pages, starting with +debhelper(1). That's required because you'll have to +understand what is going on to be able to use them wisely and to +fix bugs in a pretty way. +

+debhelper is very useful because it lets you follow the latest Debian policy +without doing many modifications since the changes that can be automated are +almost always automatically done by a debhelper script. Furthermore it +offers enough flexibility to be able to use it in conjunction with +some hand crafted shell invocations within the rules file. +

+You can however decide to not use any helper script, and still write +some very good rules file. Many examples are available +at . + + + + Package with multiple patches +

+Big packages tend to have many upstream bugs that you want to fix within +the Debian package. If you just correct the bug in the source, all the +fixes are directly integrated in the .diff.gz file and you +can't easily differentiate the various patches that you applied. It gets +very messy when you have to update the package to a new upstream version +which integrates some of the fixes (but not all). +

+The good solution is to keep separate patches within the +debian/patches directory and to apply them on the fly at +build time. The package dbs provides an +implementation of such a system, you just have to build-depend on dbs to +be able to use its functionalities. The package +hello-dbs is a simple example that demonstrates how to +use dbs. +

+Additionally, dbs provides facilities to create the patches and to keep +track of what they are for. + + Multiple binary packages +

+A single source package will often build several binary packages, either +to provide several flavors of the same software (examples are the +vim-* packages) or to make several small packages instead of a big one +(it's interesting if the user doesn't need all the packages and can thus +save some disk space). +

+The second case can be easily managed by dh_install (from +debhelper) to move files from the build directory to +the package's temporary trees. +

+The first case is a bit more difficult since it involves multiple recompiles +of the same software but with different configure options. The +vim is an example of how to manage this with an +hand crafted rules file. + + + Handling debconf translations +

+Like porters, translators have a difficult task. Since they work on many +packages, they cannot keep track of every change in packages in order to +be informed when a translated string is outdated. Fortunately +debconf can automatically report outdated translations, +if package maintainers follow some basic guidelines described below. +

+Translators can use debconf-getlang (package +debconf-utils) to write a templates.xx +file containing both English and localized fields (where xx is +the language code, may be followed by a country code). This file can be +put into the debian subdirectory without any change. +

+When building a binary package, debian/templates.xx files are +merged along with debian/templates to generate the +templates file contained in the binary package. This is +automatically done by dh_installdebconf (package +debhelper). If you do not use debhelper, you can +do the same with debconf-mergetemplate +(package debconf-utils). +

+When the package maintainer needs to update the templates file, they only +change debian/templates. When English strings in this file +and in debian/templates.xx differ, translators do know that +their translation is outdated. +

+Please see the page about + +at the Debian web site, it contains more detailed instructions, including a +full example. + + + + Specific packaging practices + + + + Libraries +

+Libraries are always difficult to package for various reasons. The policy +imposes many constraints to ease their maintenance and to make sure +upgrades are as simple as possible when a new upstream version comes out. +A breakage in a library can result in dozens of dependent packages to +break... +

+Good practices for library packaging have been grouped in +. + + Other specific packages +

+Several subsets of packages have special sub-policies and corresponding +packaging rules and practices: + + +Perl related packages have a , +some examples of packages following that policy are +libdbd-pg-perl (binary perl module) or +libmldbm-perl (arch independent perl module). + +Python related packages have their python policy: +&file-python-policy; (in the python package). + +Emacs related packages have the . + +Java related packages have their . + +Ocaml related packages have their ocaml policy: &file-ocaml-policy; (in +the ocaml package). A good example is the camlzip +source package. + + + + Configuration management + + The wise use of debconf +

+Debconf is a configuration management system, it is used by all the +various packaging scripts (postinst mainly) to request feedback from the +user concerning how to configure the package. Direct user interactions +must now be avoided in favor of debconf interaction. This will enable +non-interactive installations in the future. +

+Debconf is a great tool but it is often badly used ... many common mistakes +are listed in the man page. +It is something that you must read if you decide to use debconf. + + + + + Miscellaneous advice + + + Writing useful descriptions +

+The description of the package (as defined by the corresponding field +in the control file) is usually the first information +available to the user before they install it. As such, it should +provide all the required information to let him decide whether +to install the package. +

+For example, apart from the usual description that you adapt from the +upstream README, you should include the URL of the +web site if there's any. If the package is not yet considered stable +by the author, you may also want to warn the user that the +package is not ready for production use. +

+For consistency and for an aesthetic concern, you should capitalize the +first letter of the description. +

+Last but not least, since the first user impression is based on +that description, you should be careful to avoid English +mistakes. Ensure that you spell check it. +ispell has a special option (-g) for that: +ispell -d american -g debian/control. + + + + + + Beyond Packaging +

+Debian is about a lot more than just packaging software and +maintaining those packages. This chapter contains information about +ways, often really critical ways, to contribute to Debian beyond +simply creating and maintaining packages. +

+As a volunteer organization, Debian relies on the discretion of its +members in choosing what they want to work on, and choosing what is +the most critical thing to spend their time on. + + + Bug Reporting +

+We encourage you to file bugs as you find them in Debian packages. In +fact, Debian developers are often the first line testers. Finding and +reporting bugs in other developer's packages improves the quality of +Debian. +

+Try to submit the bug from a normal user account at which you are +likely to receive mail. Do not submit bugs as root. +

+Make sure the bug is not already filed against a package. Try to do a +good job reporting a bug and redirecting it to the proper location. +For extra credit, you can go through other packages, merging bugs +which are reported more than once, or setting bug severities to +`fixed' when they have already been fixed. Note that when you are +neither the bug submitter nor the package maintainer, you should +not actually close the bug (unless you secure permission from the +maintainer). +

+From time to time you may want to check what has been going on +with the bug reports that you submitted. Take this opportunity to +close those that you can't reproduce anymore. To find +out all the bugs you submitted, you just have to visit +http://&bugs-host;/from:<your-email-addr>. + + Reporting lots of bugs at once

Reporting a great number of bugs for the same problem on a great -number of different packages &mdash i.e., more than 10 &mdash is a deprecated +number of different packages — i.e., more than 10 — is a deprecated practice. Take all possible steps to avoid submitting bulk bugs at all. For instance, if checking for the problem can be automated, add a new check to lintian so that an error or warning @@ -2091,23 +2923,78 @@ that the bug report is not forwarded to the bug distribution mailing list. - - Interaction with Prospective Developers + Quality Assurance effort +

+Even though there is a dedicated group of people for Quality +Assurance, QA duties are not reserved solely for them. You can +participate in this effort by keeping your packages as bug-free as +possible, and as lintian-clean (see ) as +possible. If you do not find that possible, then you should consider +orphaning some of your packages (see ). Alternatively, you may ask the help of other people +in order to catch up the backlog of bugs that you have (you can ask +for help on &email-debian-qa; or &email-debian-devel;). + + Dealing with unreachable maintainers +

+If you notice that a package is lacking maintenance, you should +make sure the maintainer is active and will continue to work on +his packages. Try contacting him yourself. +

+If you do not get a reply after a few weeks you should collect all +useful information about this maintainer. Start by logging into +the +and doing a full search to check whether the maintainer is on vacation +and when they were last seen. Collect any important package names +they maintain and any Release Critical bugs filed against them. +

+Send all this information to &email-debian-qa;, in order to let the +QA people do whatever is needed. + Contacting other maintainers

-This chapter describes procedures that existing Debian developers should -follow when it comes to dealing with wannabe developers. +During your lifetime within Debian, you will have to contact other +maintainers for various reasons. You may want to discuss a new +way of cooperating between a set of related packages, or you may +simply remind someone that a new upstream version is available +and that you need it. +

+Looking up the email address of the maintainer for the package can be +distracting. Fortunately, there is a simple email alias, +<package>@&packages-host;, which provides a way to +email the maintainer, whatever their individual email address (or +addresses) may be. Replace <package> with the name of +a source or a binary package. +

+You may also be interested in contacting the persons who are +subscribed to a given source package via . +You can do so by using the <package-name>@&pts-host; +email address. + + + + Interacting with prospective Debian developers +

+Debian's success depends on its ability to attract and retain new and +talented volunteers. If you are an experienced developer, we +recommend that you get involved with the process of bringing in new +developers. This section describes how to help new prospective +developers. - Sponsoring packages + + Sponsoring packages

Sponsoring a package means uploading a package for a maintainer who is not able to do it on their own, a new maintainer applicant. Sponsoring a package also means accepting responsibility for it.

+If you wish to volunteer as a sponsor, you can sign up at . +

New maintainers usually have certain difficulties creating Debian packages — this is quite understandable. That is why the sponsor is there, to check the package and verify that it is good enough for inclusion in Debian. -(Note that if the sponsored package is new, the FTP admins will also have to +(Note that if the sponsored package is new, the ftpmasters will also have to inspect it before letting it in.)

Sponsoring merely by signing the upload or just recompiling is @@ -2117,22 +3004,57 @@ doesn't matter that you left the prospective developer's name both in the changelog and the control file, the upload can still be traced to you.

If you are an application manager for a prospective developer, you can also -be their sponsor. That way you can also verify the how the applicant is -handling the `Tasks and Skills' part of their application. +be their sponsor. That way you can also verify how the applicant is +handling the 'Tasks and Skills' part of their application. - Advocating new developers + Managing sponsored packages +

+By uploading a sponsored package to Debian, you are certifying that +the package meets minimum Debian standards. That implies that you +must build and test the package on your own system before uploading. +

+You can not simply upload a binary .deb from the sponsoree. In +theory, you should only ask only for the diff file, and the location of the +original source tarball, and then you should download the source and apply +the diff yourself. In practice, you may want to use the source package +built by your sponsoree. In that case, you have to check that they haven't +altered the upstream files in the .orig.tar.gz file that +they're providing. +

+Do not be afraid to write the sponsoree back and point out changes +that need to be made. It often takes several rounds of back-and-forth +email before the package is in acceptable shape. Being a sponsor +means being a mentor. +

+Once the package meets Debian standards, build the package with +dpkg-buildpackage -us -uc and sign it +with debsign -m <your-email-addr> <changes-file> +before uploading it to the incoming directory. +

+The Maintainer field of the control file and the +changelog should list the person who did the packaging, i.e. the +sponsoree. The sponsoree will therefore get all the BTS mail about the +package. +

+If you prefer to leave a more evident trace of your sponsorship job, you +can add a line stating it in the most recent changelog entry. +

+You are encouraged to keep tabs on the package you sponsor using +. + + Advocating new developers

See the page about at the Debian web site. - Handling new maintainer applications + Handling new maintainer applications

Please see at the Debian web site. - Overview of Debian Maintainer Tools + Overview of Debian Maintainer Tools

This section contains a rough overview of the tools available to maintainers. The following is by no means complete or definitive, but @@ -2152,7 +3074,7 @@ endorse any particular tool to the exclusion of a competing tool. Most of the descriptions of these packages come from the actual package descriptions themselves. Further information can be found in the package documentation itself. You can also see more info with the -command apt-cache show package_name. +command apt-cache show <package-name>. @@ -2180,7 +3102,7 @@ id="upload-checking"> and .

debconf provides a consistent interface to configuring packages interactively. It is user interface -independant, allowing end-users to configure packages with a +independent, allowing end-users to configure packages with a text-only interface, an HTML interface, or a dialog interface. New interfaces can be added modularly.

@@ -2235,7 +3157,7 @@ favor of debhelper. However, it's not a bug to use

yada is another packaging helper tool. It uses a debian/packages file to auto-generate -debian/rules other necessary files in the +debian/rules and other necessary files in the debian/ subdirectory.

Note that yada is called "essentially unmaintained" @@ -2271,7 +3193,7 @@ a version control system. dupload

-dupload is a package and a script to automagically +dupload is a package and a script to automatically upload Debian packages to the Debian archive, to log the upload, and to send mail about the upload of a package. You can configure it for new upload locations or methods. @@ -2284,7 +3206,7 @@ The dput package and script does much the same thing as dupload, but in a different way. It has some features over dupload, such as the ability to check the GnuPG signature and checksums before uploading, and the -possibility of running dinstall in dry-run mode after the +possibility of running dinstall in dry-run mode after the upload. @@ -2302,26 +3224,39 @@ user: dpkg-buildpackage -rfakeroot. debootstrap

The debootstrap package and script allows you to -"bootstrap" a Debian base system into any part of your filesystem. +"bootstrap" a Debian base system into any part of your file-system. By "base system", we mean the bare minimum of packages required to operate and install the rest of the system.

-Having a system link this can be useful in many ways. For instance, +Having a system like this can be useful in many ways. For instance, you can chroot into it if you want to test your build depends. Or, you can test how your package behaves when installed into a bare base system. + + pbuilder +

+pbuilder constructs a chrooted system, and builds +a package inside the chroot. It is very useful to check that +a package's build-dependencies are correct, and to be sure that +unnecessary and wrong build dependencies will not exist in the +resulting package. + + devscripts

devscripts is a package containing a few wrappers -and tools which you may find helpful for maintaining your Debian +and tools which are very helpful for maintaining your Debian packages. Example scripts include debchange and dch, which manipulate your debian/changelog file from the command-line, and debuild, which is a -wrapper around dpkg-buildpackage. - +wrapper around dpkg-buildpackage. The bts +utility is also very helpful to update the state of bug reports on the +command line, as is uscan to watch for new upstream +versions of your packages. Check the devscripts(1) manual +page for a complete list of available scripts. @@ -2340,7 +3275,7 @@ finalizing a version and listing the package's current bugs. debget is a package containing a convenient script which can be helpful in downloading files from the Debian archive. You can use it to download source packages, for instance (although -apt-get source package does pretty much the same +apt-get source <package-name> does pretty much the same thing). @@ -2349,7 +3284,7 @@ thing). alien dpkg-repack grep-dctrl - pbuilder --> +-->