X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=pkgs.dbk;h=6846e24c98b53a7ac7735643ad26c7396990a519;hb=7b6908b7523a7a9d36ee0ee7eb9e8a2d27b8f83a;hp=38256bfe2cd3b863ca1c524d883ed59d105c846f;hpb=7347b8fe6bde56036f349496304bca972f7035ee;p=developers-reference.git
diff --git a/pkgs.dbk b/pkgs.dbk
index 38256bf..6846e24 100644
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -841,14 +841,22 @@ fixing them themselves, sending security advisories, and maintaining
When you become aware of a security-related bug in a Debian package, whether or
not you are the maintainer, collect pertinent information about the problem,
-and promptly contact the security team at
-&email-security-team; as soon as possible. DO NOT UPLOAD any packages for stable
-without contacting the team. Useful information includes, for example:
+and promptly contact the security team, preferedly by filing a ticket in
+their Request Tracker.
+See .
+Alternatively you may email &email-security-team;.
+DO NOT UPLOAD any packages for
+stable without contacting the team. Useful information
+includes, for example:
+Whether or not the bug is already public.
+
+
+
+
Which versions of the package are known to be affected by the bug. Check each
version that is present in a supported Debian release, as well as
testing and unstable.
@@ -1151,12 +1159,13 @@ uploads.
-Unless the upstream source has been uploaded to security.debian.org
- before (by a previous security update), build the upload with full upstream source (dpkg-buildpackage
--sa). If there has been a previous upload to
-security.debian.org with the same upstream version, you may
-upload without upstream source (dpkg-buildpackage -sd).
+Unless the upstream source has been uploaded to
+security.debian.org before (by a previous security update),
+build the upload with full upstream source
+(dpkg-buildpackage -sa). If there has been a previous
+upload to security.debian.org with the same upstream
+version, you may upload without upstream source (dpkg-buildpackage
+-sd).
@@ -1278,7 +1287,7 @@ short summary of the reason for the removal request.
[architecture list] is optional and only needed
if the removal request only applies to some architectures, not all. Note
that the reportbug will create a title conforming
-to these rules when you use it to report a bug against the
+to these rules when you use it to report a bug against the
ftp.debian.org pseudo-package.
@@ -1862,6 +1871,35 @@ role="package">ftp.debian.org.
+
+Marking non-free packages as auto-buildable
+
+By default packages from non-free are not built by the autobuilder
+network (mostly because the license of the packages could disapprove).
+To enable a package to be build you need to perform the following
+steps:
+
+
+
+
+Check whether it is legally allowed and technically possible
+to auto-build the package ;
+
+
+
+
+Add XS-Autobuild: yes into the header part
+of debian/control ;
+
+
+
+
+Send an email to &email-nonfree-release; and explain why the
+package can legitimately and technically be auto-built.
+
+
+
+
@@ -1946,6 +1984,11 @@ to the maintainer to react (for example, by uploading to the
+Upload fixing only release-critical bugs older than 7 days, with no maintainer activity on the bug for 7 days and no indication that a fix is in progress: 0 days
+
+
+
+
Upload fixing only release-critical bugs older than 7 days: 2 days
@@ -2392,7 +2435,7 @@ 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 cannot be sorted out by the
+set of interrelationship is too complicated and cannot be sorted out by the
scripts. See below for details.