X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=pkgs.dbk;h=d7273299c1972a79dae2bbf3724bf1022a2ff10d;hp=86d9273e90783fe8d7f407cdbd262d614e105ba6;hb=b5bd78d4bb84a0450d509fc20ec0df7c34fd040b;hpb=fc34d7250f853440f2e1a9e89c5fd34419ee0f40 diff --git a/pkgs.dbk b/pkgs.dbk index 86d9273..d727329 100644 --- a/pkgs.dbk +++ b/pkgs.dbk @@ -55,7 +55,7 @@ the rejection email in case you are already re-uploading. When closing security bugs include CVE numbers as well as the -Closes: #nnnnn +Closes: #nnnnn. This is useful for the security team to track vulnerabilities. If an upload is made to fix the bug before the advisory ID is known, it is encouraged to modify the historical changelog entry with the next upload. Even in this case, please @@ -174,7 +174,7 @@ output a very verbose description of the problem. Normally, a package should not be uploaded if it causes -lintian to emit errors (they will start with E). +lintian to emit errors (they will start with E). For more information on lintian, see Any fixed packages that you have prepared yourself (send only the -.diff.gz and .dsc files and read .diff.gz and .dsc files and read first) @@ -2294,7 +2294,7 @@ In any case, it is a bad idea to automatically put all team members in the a false sense of good maintenance. For the same reason, team members do not need to add themselves to the Uploaders field just because they are uploading the package once, they can do a “Team upload” (see ). Conversely, it it a bad idea to keep a +linkend="nmu-team-upload"/>). Conversely, it is a bad idea to keep a package with only the mailing list address as a Maintainer and no Uploaders.