X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=developers-reference.sgml;h=646f4f56e5eaf8aaf4bfca8549fc48865ff6865c;hb=373aca6ace7c0f2e56a7ff4017c6a6697812a405;hp=a16315578dc105b9cd3d3bad14584e972940013c;hpb=ce6b59bbab873eb8355e6e14c57aebebba40897c;p=developers-reference.git diff --git a/developers-reference.sgml b/developers-reference.sgml index a163155..646f4f5 100644 --- a/developers-reference.sgml +++ b/developers-reference.sgml @@ -5,7 +5,7 @@ %commondata; - + @@ -76,12 +76,10 @@ 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; -that information is discussed in the . Nor does this reference detail the -standards to which Debian software must comply; that information can -be found in the . +details of the Debian package nor how to generate Debian packages. +Nor does this reference detail the standards to which Debian software +must comply. All of such information can be found in the .

Furthermore, this document is not an expression of formal policy. It contains documentation for the Debian system and @@ -929,9 +927,9 @@ The changes file is a control file with the following fields: &control-file-fields;

All of these fields are mandatory for a Debian upload. See the list -of control fields in the for the contents of these fields. You can close -bugs automatically using the Description field, see for the contents of these fields. You can close bugs +automatically using the Description field, see . Only the Distribution field is discussed in this section, since it relates to the archive maintenance policies. @@ -1087,7 +1085,7 @@ 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) + Uploading to non-US (pandora)

As discussed above, export controlled software should not be uploaded to ftp-master. Instead, use scp or non-anonymous @@ -1102,7 +1100,29 @@ the program for details. You can check your upload the same way it's done on ftp-master, with: dinstall -n foo.changes - +

+Note that U.S. residents or citizens are subject to restrictions on +export of cryptographic software. As of this writing, U.S. citizens are +allowed to export some cryptographic software, subject to notification +rules by the U.S. Department of Commerce. +

+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 +developers take all necessary steps to ensure that they are not +breaking current US law by doing an upload to non-US, including +consulting a lawyer. +

+For packages in non-US main or contrib, developers should at least +follow the . Maintainers of non-US/non-free packages should +further consult these of non-free software. +

+This section is for information only and does not constitute legal +advice. Again, it is strongly recommended that U.S. citizens and +residents consult a lawyer before doing uploads to non-US. + + Uploads via chiark

If you have a slow network connection to ftp-master, there are @@ -1522,7 +1542,7 @@ of things you should check or be aware of. Don't set architecture to a value other than ``all'' or ``any'' unless you really mean it. In too many cases, maintainers don't follow the -instructions in the . Setting your architecture to ``i386'' is usually incorrect. Make sure your source package is correct. Do dpkg-source -x @@ -1711,8 +1731,8 @@ 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 +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 @@ -1753,8 +1773,8 @@ announce list (either &email-debian-changes; or 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 your debian/control file to replace and conflict with the -obsolete name of the package (see the for details). Once you've uploaded +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.