X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=beyond-pkging.dbk;h=cafbbd39f0a7f9a9318bee4a7dcceab416fe1f82;hp=b43eda4413c1234c6a4c78c1bc8f20ca6ccc7a6d;hb=2a571cfb5cf92b9559db64e422c92535a90fb08a;hpb=1c245b536e741df8beeceb7c109ccf884cd90276 diff --git a/beyond-pkging.dbk b/beyond-pkging.dbk index b43eda4..cafbbd3 100644 --- a/beyond-pkging.dbk +++ b/beyond-pkging.dbk @@ -64,7 +64,7 @@ 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>. +http://&bugs-host;/from:your-email-addr.
Reporting lots of bugs at once (mass bug filing) @@ -85,7 +85,7 @@ several maintainers start filing the same bug report simultaneously. Please use the programs dd-list and if appropriate -whodepends (from the package devscripts) to generate a list +whodepends (from the package devscripts) to generate a list of all affected packages, and include the output in your mail to &email-debian-devel;. @@ -109,24 +109,24 @@ To add usertags when filing bugs, specify the User and To: submit@bugs.debian.org -Subject: <title-of-bug> +Subject: title-of-bug -Package: <pkgname> +Package: pkgname [ ... ] -User: <email-addr> -Usertags: <tag-name> [ <tag-name> ... ] +User: email-addr +Usertags: tag-name [ tag-name ... ] -<description-of-bug ...> +description-of-bug ... Note that tags are seperated by spaces and cannot contain underscores. If you -are filing bugs for for a particular group or team it is recommended that you +are filing bugs for a particular group or team it is recommended that you set the User to an appropriate mailing list after describing your intention there. To view bugs tagged with a specific usertag, visit -http://&bugs-host;/cgi-bin/pkgreport.cgi?users=<email-addr>&tag=<tag-name>. +http://&bugs-host;/cgi-bin/pkgreport.cgi?users=email-addr&tag=tag-name.
@@ -141,13 +141,13 @@ To view bugs tagged with a specific usertag, visit 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 +linkend="lintian"/>) 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 +linkend="orphaning"/>). Alternatively, you may ask the help of other people in order to catch up with the backlog of bugs that you have (you can ask for help on &email-debian-qa; or &email-debian-devel;). At the same time, you can look for -co-maintainers (see ). +co-maintainers (see ). @@ -197,15 +197,15 @@ 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 +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 +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>@&pts-host; email +given source package via . You can do so +by using the package@&pts-host; email address. @@ -225,8 +225,8 @@ There is a simple system (the MIA database) in which information about maintainers who are deemed Missing In Action is recorded. When a member of the QA group contacts an inactive maintainer or finds more information about one, this is recorded in the MIA database. This system is available in -/org/qa.debian.org/mia on the host qa.debian.org -, and can be queried with the mia-query tool. +/org/qa.debian.org/mia on the host qa.debian.org, +and can be queried with the mia-query tool. Use mia-query --help to see how to query the database. If you find that no information has been recorded about an inactive maintainer yet, or that you can add more information, you should generally proceed as follows. @@ -308,8 +308,8 @@ someone with more time. If you are interested in working in the MIA team, please have a look at the -README file in /org/qa.debian.org/mia on -qa.debian.org where the technical details and the MIA procedures are +README file in /org/qa.debian.org/mia on +qa.debian.org where the technical details and the MIA procedures are documented and contact &email-mia;. @@ -369,7 +369,7 @@ In theory, you should only ask 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 +upstream files in the .orig.tar.{gz,bz2,lzma} file that they're providing. @@ -389,7 +389,7 @@ part of your KEY-ID, as long as it's unique in your secret keyring. -The Maintainer field of the control file and the +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. @@ -400,7 +400,7 @@ add a line stating it in the most recent changelog entry. You are encouraged to keep tabs on the package you sponsor using . +linkend="pkg-tracking-system"/>.