Next: , Previous: Automated Upload Registration, Up: Automated FTP Uploads


9.5.2 Automated Upload Procedure

Once you have registered your information as described in the previous section, you will be able to do unattended ftp uploads using the following procedure.

For each upload destined for ftp.gnu.org or alpha.gnu.org, three files (a triplet) need to be uploaded via ftp to the host ftp-upload.gnu.org.

  1. The file to be distributed (for example, foo.tar.gz).
  2. Detached GPG binary signature for (1), made using `gpg -b' (for example, foo.tar.gz.sig).
  3. A clearsigned directive file, made using `gpg --clearsign' (for example, foo.tar.gz.directive.asc).

The names of the files are important. The signature file must have the same name as the file to be distributed, with an additional .sig extension. The directive file must have the same name as the file to be distributed, with an additional .directive.asc extension. If you do not follow this naming convention, the upload will not be processed.

Since v1.1 of the upload script, it is also possible to upload a directive file on its own to perform certain operations on uploaded files. See FTP Upload Directive File - v1.1, for more information.

Upload the file(s) via anonymous ftp to ftp-upload.gnu.org. If the upload is destined for ftp.gnu.org, place the file(s) in the /incoming/ftp directory. If the upload is destined for alpha.gnu.org, place the file(s) in the /incoming/alpha directory.

Uploads are processed every five minutes. Uploads that are in progress while the upload processing script is running are handled properly, so do not worry about the timing of your upload.

Your designated upload email addresses (see Automated Upload Registration) are sent a message if there are any problems processing an upload for your package. You also receive a message when your upload has been successfully processed.

If you have difficulties processing an upload, email ftp-upload@gnu.org.