FAQ 4.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112
  1. 1. Why can't the option -D be used with ftp uploads?
  2. Because the ftp upload method uses anonymous upload queues, which
  3. don't know anything about the user or dinstall. They will just
  4. accept every Debian package and later upload it to the incoming
  5. directory of ftp.upload.debian.org.
  6. 2. Why don't you change the suffix .cf to .conf for consistency purpose?
  7. At the time, where I had to decide on a suffix for the
  8. configuration file, I had the offer to user either "rc", ".cf" or
  9. ".conf". If you look at the dot files in your homedir or the files
  10. in /etc, you'll notice that there's no standard and that every of
  11. these three extension is used. Since I wanted to have a short
  12. suffix, I had to decide between "rc" or ".cf". I decided to use
  13. ".cf" as suffix, because it's an obvious abbreviation for
  14. configuration and also I noticed that postfix uses it as extension.
  15. Since this extension has now been used for quite some time, I'm not
  16. planning to change it. Any change would need a lot of work or
  17. introduce problems for the users.
  18. 3. Why can't dput act like dupload and just use every file in the
  19. directory?
  20. Well, dput was not written as a dupload-in-Python, but as an
  21. alternative tool for uploading Debian packages. dput and dupload
  22. are completely different, especially since dput supports modules.
  23. I only took one or two ideas from dupload, especially the hooks,
  24. but won't implement any further options or features.
  25. 4. Why should I switch to dput since dupload works for me?
  26. Because dput will make you rich and attractive.
  27. Now, seriously, it's a matter of preferences. If you use dupload
  28. and like its behaviour, then continue to use it. But in every
  29. case, I would suggest that you try dput, since it will check the
  30. GnuPG signature and the checksums before uploading and offer to run
  31. dinstall in dry-run mode after the upload. It also offers the usage
  32. of other upload methods via modules.
  33. 5. Where are modules and what are they exactly used for?
  34. dput uses modules for the different upload methods that it offers.
  35. All upload methods are implemented via seperate modules that will
  36. be loaded at runtime. That way we can easily extend the number of
  37. upload methods that dput offers. So if you write or already wrote a
  38. new upload method, then please inform the author of dput, so that
  39. it maybe can be added to dput in the future.
  40. 6. Can I just copy /etc/dput.cf into my homedir as .dput.cf?
  41. No, this shouldn't be done, because .dput.cf is a configuration
  42. file for the user. It should only contain configuration variables
  43. which have a value different from the default and which the user
  44. needs to define. This will reduce the risk of breaking dput, if
  45. either some default value in /etc/dput.cf is changed or a new
  46. configuration variable is added.
  47. 7. How can I set up my own local APT repository and use dput for
  48. installing?
  49. There are many ways to maintain APT repositories. Using Colin
  50. Walters' mini-dinstall-Package is perhaps the easiest way (if you run
  51. sarge or later). If you want to have the repository on a remote
  52. machine, see question 8. For a local repository you might use our
  53. MICRO RECIPE FOR PERSONAL MINI-DINSTALL REPOSITORY
  54. The following dput and mini-dinstall configuration works for the
  55. mainters of dput. For your convenience we have included a "local"
  56. dput target in the stock debian dput.cf which can be used with the
  57. mini-dinstall configuration below.
  58. For simplicity, we do not use the daemon mode of mini-dinstall. As
  59. mini-dinstall has rather flexible configuration options, you might
  60. want to consider reading the documentation yourself, but the file
  61. file below should work out of the box to implement most simple setup.
  62. After copying the configuration file below into your home directory
  63. do mkdir -p public_html/debian ; mini-dinstall --batch
  64. in your home directory to setup your repository.
  65. ~/.mini-dinstall.conf:
  66. # Adapted Colin's mini-dinstall.conf
  67. [DEFAULT]
  68. architectures = all, i386
  69. archivedir = ~/public_html/debian/
  70. use_dnotify = 0
  71. verify_sigs = 0
  72. extra_keyrings = ~/.gnupg/pubring.gpg
  73. mail_on_success = 0
  74. archive_style = flat
  75. poll_time = 10
  76. mail_log_level = NONE
  77. [stable]
  78. [testing]
  79. [unstable]
  80. 8. How do I set up dput to fill my remote APT repository?
  81. Assuming you have remote ssh access, you can use the following
  82. You can use the same mini-dinstall configuration file (and setup
  83. command) as for a local repository on the remote machine.
  84. As ~/.dput.cf you now can use
  85. [myremote]
  86. fqdn = remote.machine.net
  87. login = usernameonremote
  88. method = scp
  89. incoming = ~/public_html/debian/mini-dinstall/incoming
  90. run_dinstall = 0
  91. post_upload_command = ssh usernameonremote@remote.machine.net /usr/bin/mini-dinstall --batch