2 This directory is the Debian upload queue of ssh.upload.debian.org. All
3 valid files uploaded here will be transferred to ftp.upload.debian.org.
5 Only known Debian developers can upload here. Uploads have to be signed
6 by PGP keys in the Debian keyring. Files not meeting this criterion or
7 files not mentioned in a .changes file will be removed after some time.
9 The queue daemon will notify you by mail of success or any problems
16 Besides *.changes files, you can also upload *.commands files for the
17 daemon to process. With *.commands files, you can instruct the daemon
18 to remove or rename files in the queue directory that, for example,
19 resulted from failed or interrupted uploads. A *.commands file looks
20 much like a *.changes, but contains only two fields: Uploader: and
21 Commands:. It must be PGP-signed by a known Debian developer, to avoid
22 that E.V.L. Hacker can remove/rename files in the queue. The basename
23 (the part before the .commands extension) doesn't matter, but best
24 make it somehow unique.
26 The Uploader: field should contain the mail address to which the reply
27 should go, just like Maintainer: in a *.changes. Commands: is a
28 multi-line field like e.g. Description:, so each continuation line
29 should start with a space. Each line in Commands: can contain a
30 standard 'rm' command, but no options are allowed. Filenames may not
31 contain slashes (so that they're restricted to the queue
32 directory). 'rm' can process as much arguments as you give it (not only
33 one), and also knows about the shell wildcards *, ?, and [].
35 Example of a *.commands file:
37 -----BEGIN PGP SIGNED MESSAGE-----
40 Uploader: Some One <some@example.com>
42 rm hello_1.0-1_i386.deb
44 -----BEGIN PGP SIGNATURE-----
45 Version: GnuPG v1.4.12 (GNU/Linux)
48 -----END PGP SIGNATURE-----