Queue.README 3.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697
  1. This directory is the Debian upload queue of ftp.upload.debian.org. All
  2. files uploaded here will be moved into the project incoming dir on
  3. this machine.
  4. Only known Debian developers can upload here. Uploads have to be signed
  5. by PGP keys in the Debian keyring. Files not meeting this criterion or
  6. files not mentioned in a .changes file will be removed after some time.
  7. The queue daemon will notify you by mail of success or any problems
  8. with your upload.
  9. *.commands Files
  10. ----------------
  11. Besides *.changes files, you can also upload *.commands files for the
  12. daemon to process. With *.commands files, you can instruct the daemon
  13. to remove or rename files in the queue directory that, for example,
  14. resulted from failed or interrupted uploads. A *.commands file looks
  15. much like a *.changes, but contains only two fields: Uploader: and
  16. Commands:. It must be PGP-signed by a known Debian developer, to avoid
  17. that E.V.L. Hacker can remove/rename files in the queue. The basename
  18. (the part before the .commands extension) doesn't matter, but best
  19. make it somehow unique.
  20. The Uploader: field should contain the mail address to which the reply
  21. should go, just like Maintainer: in a *.changes. Commands: is a
  22. multi-line field like e.g. Description:, so each continuation line
  23. should start with a space. Each line in Commands: can contain a
  24. standard 'rm' command, but no options are allowed. Except for the
  25. DELAYED queue (see below) filenames may not contain slashes (so that
  26. they're restricted to the queue directory). 'rm' can process as much
  27. arguments as you give it (not only one), and also knows about the shell
  28. wildcards *, ?, and [].
  29. Example of a *.commands file:
  30. -----BEGIN PGP SIGNED MESSAGE-----
  31. Hash: SHA256
  32. Uploader: Some One <some@example.com>
  33. Commands:
  34. rm hello_1.0-1_i386.deb
  35. -----BEGIN PGP SIGNATURE-----
  36. Version: GnuPG v1.4.12 (GNU/Linux)
  37. [...]
  38. -----END PGP SIGNATURE-----
  39. DELAYED Queue
  40. -------------
  41. There is a DELAYED queue available. Packages uploaded into the
  42. X-day (X between 0 and 15) subdirectories of DELAYED/ will be moved into
  43. the DEFERRED queue and won't be placed into the archive before the
  44. waiting time is over.
  45. To avoid confusion, the terms used are:
  46. DELAYED - the public ftp upload directories, reachable via DELAYED/X-day
  47. DEFERRED - this is the place where the uploads are placed by the queue
  48. daemon after processing and where packages wait before they
  49. are moved into the incoming queue.
  50. You can modify the queues (besides uploading packages) with *.commands
  51. files as described above, using the following syntax.
  52. Note that any processing in the DEFERRED queue works on whole uploads
  53. (i.e. a .changes file and all the files that came with it), whereas
  54. operations in the DELAYED queue (and the normal ftp root directory)
  55. work on individual files.
  56. - To move a package from one DEFERRED directory into another, say
  57. from 8-days to 2-days delay:
  58. reschedule foo_1.2-1.1_all.changes 2-day
  59. The move-target has to be without the trailing /.
  60. - To delete an upload (and all associated files) in the DEFERRED queue:
  61. cancel foo_1.2-1.1_all.changes
  62. - To delete a broken upload in the DELAYED queue:
  63. rm DELAYED/X-day/foobar.deb
  64. or
  65. rm --searchdirs foobar.deb
  66. - The old mv command is no longer supported.
  67. Wildcards in .commands files are only valid for the DELAYED queue and
  68. its rm command, the DEFERRED queue commands cancel and reschedule do
  69. not allow them.