X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=pkgs.dbk;h=ad290afcabf8050f42590d07c4ed58fd48cfdd05;hb=ab99f3331f87e57627fe7ac5701540aea6b6ffa5;hp=8dd84be2514106eec429357cc2c60bb691974d4e;hpb=f5e816ccb9b3f7134c12b82c3388b586e29c7676;p=developers-reference.git diff --git a/pkgs.dbk b/pkgs.dbk index 8dd84be..ad290af 100644 --- a/pkgs.dbk +++ b/pkgs.dbk @@ -301,7 +301,7 @@ time. Special case: uploads to the <literal>stable</literal> and <literal>oldstable</literal> distributions -Uploading to stable means that the package will transfered +Uploading to stable means that the package will transferred to the proposed-updates-new queue for review by the stable release managers, and if approved will be installed in stable-proposed-updates directory of the Debian archive. @@ -888,7 +888,7 @@ below on how to prepare packages for the Security Team to handle. The Security Tracker The security team maintains a central database, the -Debian Security Tracker. +Debian Security Tracker. This contains all public information that is known about security issues: which packages and versions are affected or fixed, and thus whether stable, testing and/or unstable are vulnerable. Information that is still confidential @@ -1847,8 +1847,7 @@ fail also, and indicate this to a human reader without actually trying. In order to prevent autobuilders from needlessly trying to build your package, it must be included in packages-arch-specific, a list used by the wanna-build script. The current version is available -as ; +as ; please see the top of the file for whom to contact for changes.