Otherwise, set C<git-check> to a url prefix - ideally, https.
dgit clone will try to fetch
-C<git-check>I<package>C<git-check-suffix>
+C<git-check>B</>I<package>C<git-check-suffix>
and expect to get either some successful fetch (it doesn't matter what)
or a file not found error (http 404 status code).
Other outcomes are fatal errors.
=item B<dgit-distro.>I<distro>B<.archive-query>, B<.archive-query-url>
If you have a smallish distro,
-set this to B<aptget:> (with a colon).
+set C<archive-query> to B<aptget:> (with a colon).
If your distro is large
(eg, if it contains a substantial fraction of Debian)
then this will not be very efficient:
with this setting,
-dgit often needs to downloads and update Sources files.
+dgit often needs to download and update Sources files.
For large distros,
it is better to implement the Debian archive ftpmaster API.
B<suites>,
B<dsc_in_suite/>I<isuite>B</>I<package> and
B<file_in_archive/>I<pat>
+(so you need not implement anything else).
+
+Alternatively,
+if your system supports the rmadison protocol,
+you can set C<archive-query> to B<madison:>[I<madison-distro>].
+dgit will invoke B<rmadison> -uI<madison-distro>.
=item B<dgit-suite.>I<suite>B<.distro> I<distro>
B<cp -a _template.git> I<package>B<.git>.
So you should create B<_template.git> with suitable contents.
+Note that the ssh rune invoked by dgit does not do any locking.
+So if two people dgit push the same package at the same time,
+there will be lossage.
+Either don't do that, or set up B<dgit-repos-server>.
+
=head1 SSH COMMANDS
When a user who can push runs dgit,