Previous: Automated Upload Registration, Up: Automated FTP Uploads
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
.
Upload the triplet via anonymous ftp to ftp-upload.gnu.org
. If
the upload is destined for ftp.gnu.org
, then place the triplet
in the /incoming/ftp directory. If the upload is destined for
alpha.gnu.org
, then place the triplet in the
/incoming/alpha directory.
Uploads are processed every five minutes. Uploads that are in progress when the upload processing script is running are handled properly, so do not worry about the timing of your upload.
The directive file should contain one line, excluding the clearsigned data GPG that inserts, which specifies the final destination directory where items (1) and (2) to be placed.
For example, the foo.tar.gz.directive file might contain the single line:
directory: bar/v1
This directory line indicates that foo.tar.gz and
foo.tar.gz.sig are part of package bar
. If you were to
upload the triplet to /incoming/ftp, and the system can
positively authenticate the signatures, then the files
foo.tar.gz and foo.tar.gz.sig will be placed in the
directory gnu/bar/v1 of the ftp.gnu.org
site.
The directive file can be used to create currently non-existent
directory trees, as long as they are under the package directory for
your package (in the example above, that is bar
).
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.