2 .TH dgit 1 "" "Debian Project" "dgit"
4 dgit \- git integration with the Debian archive
8 [\fIdgit\-opts\fP] \fBclone\fP [\fIdgit\-opts\fP]
9 \fIpackage\fP [\fIsuite\fP] [\fB./\fP\fIdir|\fB/\fP\fIdir\fR]
12 [\fIdgit\-opts\fP] \fBfetch\fP|\fBpull\fP [\fIdgit\-opts\fP]
16 [\fIdgit\-opts\fP] \fBbuild\fP|\fBsbuild\fP|\fBbuild-source\fP
20 [\fIdgit\-opts\fP] \fBpush\fP [\fIdgit\-opts\fP]
24 [\fIdgit\-opts\fP] \fBrpush\fR \fIbuild-host\fR\fB:\fR\fIbuild-dir\fR
28 [\fIdgit\-opts\fP] \fIaction\fR ...
31 allows you to treat the Debian archive as if it were a git
34 This is the command line reference.
35 Please read the tutorial(s):
38 dgit-user(7) for users: editing, building and sharing packages
39 dgit-nmu-simple(7) for DDs/DMs: doing a straightforward NMU
40 dgit-maint-merge(7) for maintainers: using a merging git workflow
41 dgit-maint-gbp(7) for maintainers: using git-buildpackage
42 dgit-sponsorship(7) for sponsors and sponsored contributors
45 See \fBdgit(7)\fP for detailed information about the data
47 common problems likely to arise with certain kinds of package,
51 \fBdgit clone\fR \fIpackage\fP [\fIsuite\fP] [\fB./\fP\fIdir|\fB/\fP\fIdir\fR]
52 Consults the archive and dgit-repos to construct the git view of
59 in a new directory (named
62 also, downloads any necessary orig tarballs.
64 The suite's git tip is
65 left on the local branch
67 ready for work, and on the corresponding dgit remote tracking branch.
70 remote will be set up to point to the package's dgit-repos tree
71 for the distro to which
75 For your convenience, the
77 remote will be set up from the package's Vcs-Git field, if there is
78 one - but note that in the general case the history found there may be
79 different to or even disjoint from dgit's view.
81 \fBdgit fetch\fR [\fIsuite\fP]
82 Consults the archive and git-repos to update the git view of
83 history for a specific suite (and downloads any necessary orig
84 tarballs), and updates the remote tracking branch
85 .BR remotes/dgit/dgit/ \fIsuite\fR.
86 If the current branch is
88 then dgit fetch defaults to
90 otherwise it parses debian/changelog and uses the suite specified
93 \fBdgit pull\fR [\fIsuite\fP]
94 Does dgit fetch, and then merges the new head of the remote tracking
96 .BI remotes/dgit/dgit/ suite
97 into the current branch.
102 with some suitable options. Options and arguments after build
103 will be passed on to dpkg-buildpackage. It is not necessary to use
104 dgit build when using dgit; it is OK to use any approach which ensures
105 that the generated source package corresponds to the relevant git
108 Tagging, signing and actually uploading should be left to dgit push.
110 \fBdgit build-source\fR ...
111 Builds the source package, and a changes file for a prospective
112 source-only upload, using
114 The output is left in
115 .IR package \fB_\fR version \fB.dsc\fR
117 .IR package \fB_\fR version \fB_source.changes\fR.
119 Tagging, signing and actually uploading should be left to dgit push.
122 Cleans the current working tree (according to the --clean= option in
126 Print a usage summary.
128 \fBdgit sbuild\fR ...
129 Constructs the source package, uses
131 to do a binary build, and uses mergechanges to merge the source and
132 binary changes files. Options and arguments after sbuild will be
134 The output is left in
135 .IR package \fB_\fR version \fB_multi.changes\fR.
137 Tagging, signing and actually uploading should be left to dgit push.
139 \fBdgit gbp-build\fR ...
142 with some suitable options. Options and arguments after gbp-build
143 will be passed on to git-buildpackage.
145 By default this uses \-\-quilt=gbp, so HEAD should be a
146 git-buildpackage style branch, not a patches-applied branch.
148 Tagging, signing and actually uploading should be left to dgit push.
150 \fBdgit push\fR [\fIsuite\fP]
151 Does an `upload', pushing the current HEAD to the archive (as a source
152 package) and to dgit-repos (as git commits). The package must already
153 have been built ready for upload, with the .dsc and .changes
154 left in the parent directory. It is normally best to do the build
155 with dgit too (eg with dgit sbuild): some existing build tools pass
156 unhelpful options to dpkg-source et al by default, which can result in
157 the built source package not being identical to the git tree.
159 In more detail: dgit push checks that the current HEAD corresponds to
160 the .dsc. It then pushes the HEAD to the suite's dgit-repos branch,
161 makes a signed git tag, edits the .dsc to contain the dgit metadata
162 field, runs debsign to sign the upload (.dsc and .changes), pushes the
163 signed tag, and finally uses dput to upload the .changes to the
166 dgit push always uses the package, suite and version specified in the
167 debian/changelog and the .dsc, which must agree. If the command line
168 specifies a suite then that must match too.
170 If dgit push fails while uploading, it is fine to simply retry the
171 dput on the .changes file at your leisure.
173 \fBdgit rpush\fR \fIbuild-host\fR\fB:\fR\fIbuild-dir\fR [\fIpush args...\fR]
174 Pushes the contents of the specified directory on a remote machine.
175 This is like running dgit push on build-host with build-dir as the
176 current directory; however, signing operations are done on the
177 invoking host. This allows you to do a push when the system which has
178 the source code and the build outputs has no access to the key:
180 1. Clone on build host (dgit clone)
182 2. Edit code on build host (edit, git commit)
184 3. Build package on build host (dgit build)
186 4. Test package on build host or elsewhere (dpkg -i, test)
188 5. Upload by invoking dgit rpush on host with your GPG key.
190 However, the build-host must be able to ssh to the dgit repos. If
191 this is not already the case, you must organise it separately, for
192 example by the use of ssh agent forwarding.
194 The remaining arguments are treated just as dgit push would handle
197 build-host and build\-dir can be passed as separate
198 arguments; this is assumed to be the case if the first argument
199 contains no : (except perhaps one in [ ], to support IPv6 address
202 You will need similar enough versions of dgit on the build-host and
203 the invocation host. The build-host needs gnupg installed, with your
204 public key in its keyring (but not your private key, obviously).
206 .B dgit setup-new-tree
207 Configure the current working tree the way that dgit clone would have
208 set it up. Like running
209 .B dgit setup-useremail
211 .B setup-mergechangelogs
212 (but only does each thing if dgit is configured to do it automatically).
213 You can use these in any git repository, not just ones used with
214 the other dgit operations.
216 .B dgit setup-useremail
217 Set the working tree's user.name and user.email from the
218 distro-specific dgit configuration
219 .RB ( dgit-distro. \fIdistro\fR .user-name " and " .user-email ),
220 or DEBFULLNAME or DEBEMAIL.
222 .B dgit setup-mergechangelogs
223 Configures a git merge helper for the file
226 .BR dpkg-mergechangelogs .
229 `3.0 (quilt)' format source packages need changes representing not
230 only in-tree but also as patches in debian/patches. dgit quilt-fixup
231 checks whether this has been done; if not, dgit will make appropriate
232 patches in debian/patches and also commit the resulting changes to
235 This is normally done automatically by dgit build and dgit push.
237 dgit will try to turn each relevant commit in your git history into a
238 new quilt patch. dgit cannot convert nontrivial merges, or certain
239 other kinds of more exotic history. If dgit can't find a suitable
240 linearisation of your history, by default it will fail, but you can
241 ask it to generate a single squashed patch instead.
244 Prints version information and exits.
246 .BI "dgit clone-dgit-repos-server" " destdir"
247 Tries to fetch a copy of the source code for the dgit-repos-server,
248 as actually being used on the dgit git server, as a git tree.
251 .BR --dry-run " | " -n
252 Go through the motions, fetching all information needed, but do not
253 actually update the output(s). For push, dgit does
254 the required checks and leaves the new .dsc in a temporary file,
255 but does not sign, tag, push or upload.
257 .BR --damp-run " | " -L
258 Go through many more of the motions: do everything that doesn't
259 involve either signing things, or making changes on the public
265 for signing the tag and the upload. The default comes from the
268 config setting (see CONFIGURATION, below), or failing that, the
269 uploader trailer line in debian/changelog.
272 does not sign tags or uploads (meaningful only with push).
276 Specifies that we should process source package
278 rather than looking in debian/control or debian/changelog.
279 Valid with dgit fetch and dgit pull, only.
281 .BR --clean=git " | " -wg
284 to clean the working tree,
285 rather than running the package's rules clean target.
287 This will delete all files which are not tracked by git.
288 (Including any files you forgot to git add.)
291 options other than dpkg-source
292 are useful when the package's clean target is troublesome, or
293 to avoid needing the build-dependencies.
295 .BR --clean=git-ff " | " -wgf
297 .BR "git clean -xdff"
298 to clean the working tree.
301 but it also removes any subdirectories containing different git
302 trees (which only unusual packages are likely to create).
304 .BR --clean=check " | " -wc
305 Merely check that the tree is clean (does not contain uncommitted
307 Avoids running rules clean,
308 and can avoid needing the build-dependencies.
310 .BR --clean=none " | " -wn
311 Do not clean the tree, nor check that it is clean.
312 Avoids running rules clean,
313 and can avoid needing the build-dependencies.
315 files which are not in git, or if the build creates such files, a
316 subsequent dgit push will fail.
318 .BR --clean=dpkg-source " | " -wd
319 Use dpkg-buildpackage to do the clean, so that the source package
320 is cleaned by dpkg-source running the package's clean target.
322 Requires the package's build dependencies.
324 .BR --clean=dpkg-source-d " | " -wdd
326 .B dpkg-buildpackage -d
328 so that the source package
329 is cleaned by dpkg-source running the package's clean target.
330 The build-dependencies are not checked (due to
332 which violates policy, but may work in practice.
335 The package is or may be new in this suite. Without this, dgit will
336 refuse to push. It may (for Debian, will) be unable to access the git
337 history for any packages which have been newly pushed and have not yet
341 Do not complain if the working tree does not match your git HEAD.
342 This can be useful with build, if you plan to commit later. (dgit
343 push will still ensure that the .dsc you upload and the git tree
344 you push are identical, so this option won't make broken pushes.)
346 .BR --overwrite =\fIprevious-version\fR
347 Declare that even though your git branch is not a descendant
348 of the version in the archive
349 according to the revision history,
350 it really does contain
351 all the (wanted) changes from that version.
353 This option is useful if you are the maintainer, and you have
354 incorporated NMU changes into your own git workflow in a way that
355 doesn't make your branch a fast forward from the NMU.
358 ought to be the version currently in the archive. If
361 specified, dgit will check that the version in the archive is
362 mentioned in your debian/changelog.
363 (This will avoid losing
364 changes unless someone committed to git a finalised changelog
365 entry, and then made later changes to that version.)
367 dgit push --overwrite
369 pseudo-merge (that is, something that looks like the result
370 of git merge -s ours) to stitch the archive's version into your own
371 git history, so that your push is a fast forward from the archive.
374 .BR gbp ", " dpm " or " unpatched ,
375 implying a split between the dgit view and the
376 maintainer view, the pseudo-merge will appear only in the dgit view.)
378 .BI --deliberately- something
379 Declare that you are deliberately doing
381 This can be used to override safety catches, including safety catches
382 which relate to distro-specific policies.
383 The use of --deliberately is declared and published in the signed tags
384 generated for you by dgit,
385 so that the archive software can give effect to your intent,
387 for the benefit humans looking at the history.
390 understood in the context of Debian are discussed below:
392 .BR --deliberately-not-fast-forward
393 Declare that you are deliberately rewinding history. When pushing to
394 Debian, use this when you are making a renewed upload of an entirely
395 new source package whose previous version was not accepted for release
396 from NEW because of problems with copyright or redistributibility.
398 .BR --deliberately-include-questionable-history
399 Declare that you are deliberately including, in the git history of
400 your current push, history which contains a previously-submitted
401 version of this package which was not approved (or has not yet been
402 approved) by the ftpmasters. When pushing to Debian, only use this
403 option after verifying that: none of the rejected-from-NEW (or
404 never-accepted) versions in the git history of your current push, were
405 rejected by ftpmaster for copyright or redistributability reasons.
407 .BR --deliberately-fresh-repo
408 Declare that you are deliberately rewinding history and want to
409 throw away the existing repo. Not relevant when pushing to Debian,
410 as the Debian server will do this automatically when necessary.
413 When fixing up source format `3.0 (quilt)' metadata, insist on
414 generating a linear patch stack: one new patch for each relevant
416 If such a stack cannot be generated, fail.
417 This is the default for Debian.
419 HEAD should be a series of plain commits
420 (not touching debian/patches/),
422 with as ancestor a patches-applied branch.
425 When fixing up source format `3.0 (quilt)' metadata, prefer to
426 generate a linear patch stack
427 (as with --quilt=auto)
428 but if that doesn't seem possible,
429 try to generate a single squashed patch for all the changes made in git
430 (as with --quilt=smash).
431 This is not a good idea for an NMU in Debian.
434 When fixing up source format `3.0 (quilt)' metadata,
435 generate a single additional patch for all the changes made in git.
436 This is not a good idea for an NMU in Debian.
438 (If HEAD has any in-tree patches already, they must apply cleanly.
439 This will be the case for any trees produced by dgit fetch or clone;
440 if you do not change the upstream version
441 nor make changes in debian/patches,
442 it will remain true.)
445 Check whether source format `3.0 (quilt)' metadata would need fixing
446 up, but, if it does, fail. You must then fix the metadata yourself
447 somehow before pushing. (NB that dpkg-source --commit will not work
448 because the dgit git tree does not have a
452 .BR --quilt=nocheck " | " --no-quilt-fixup
453 Do not check whether up source format `3.0 (quilt)' metadata needs
454 fixing up. If you use this option and the metadata did in fact need
455 fixing up, dgit push will fail.
457 .BR -- [ quilt= ] gbp " | " -- [ quilt= ] dpm " | " --quilt=unapplied
458 Tell dgit that you are using a nearly-dgit-compatible git branch,
460 .BR "maintainer view" ,
462 do not want your branch changed by dgit.
467 is for use with git-buildpackage.
468 Your HEAD is expected to be
469 a patches-unapplied git branch, except that it might contain changes
470 to upstream .gitignore files. This is the default for dgit gbp-build.
475 is for use with git-dpm.
476 Your HEAD is expected to be
477 a patches-applied git branch,
478 except that it might contain changes to upstream .gitignore files.
481 specifies that your HEAD is a patches-unapplied git branch (and
482 that any changes to upstream .gitignore files are represented as
483 patches in debian/patches).
485 With --quilt=gbp|dpm|unapplied,
486 dgit push (or precursors like quilt-fixup and build) will automatically
487 generate a conversion of your git branch into the right form.
488 dgit push will push the
489 dgit-compatible form (the
491 to the dgit git server.
492 The dgit view will be visible to you
493 in the dgit remote tracking branches, but your own branch will
495 dgit push will create a tag
497 for the maintainer view, and the dgit tag
498 .BI archive/debian/ version
500 dgit quilt-fixup will merely do some checks,
501 and cache the maintainer view.
503 .B If you have a branch like this it is essential to specify the appropriate --quilt= option!
504 This is because it is not always possible to tell: a patches-unapplied
505 git branch of a package with one patch, for example, looks very like
506 a patches-applied branch where the user has used git revert to
507 undo the patch, expecting to actually revert it.
508 However, if you fail to specify the right \-\-quilt option,
509 and you aren't too lucky, dgit will notice the problem and stop,
512 .BR -d "\fIdistro\fR | " --distro= \fIdistro\fR
513 Specifies that the suite to be operated on is part of distro
515 This overrides the default value found from the git config option
516 .BR dgit-suite. \fIsuite\fR .distro .
517 The only effect is that other configuration variables (used
518 for accessing the archive and dgit-repos) used are
519 .BR dgit-distro. \fIdistro\fR .* .
521 If your suite is part of a distro that dgit already knows about, you
522 can use this option to make dgit work even if your dgit doesn't know
523 about the suite. For example, specifying
525 will work when the suite is an unknown suite in the Debian archive.
527 To define a new distro it is necessary to define methods and URLs
528 for fetching (and, for dgit push, altering) a variety of information both
529 in the archive and in dgit-repos.
530 How to set this up is not yet documented.
533 Specifies the .changes file which is to be uploaded. By default
534 dgit push looks for single .changes file in the parent directory whose
535 filename suggests it is for the right package and version.
539 pathname contains slashes, the directory part is also used as
541 .BR --build-products-dir ;
542 otherwise, the changes file is expected in that directory (by
547 When doing a build, delete any changes files matching
548 .IB package _ version _*.changes
549 before starting. This ensures that
550 dgit push (and dgit sbuild) will be able to unambigously
551 identify the relevant changes files from the most recent build, even
552 if there have been previous builds with different tools or options.
553 The default is not to remove, but
554 .B \-\-no-rm-old-changes
555 can be used to override a previous \-\-rm-old-changes
556 or the .rm-old-changes configuration setting.
558 .BI --build-products-dir= directory
559 Specifies where to find the built files to be uploaded.
560 By default, dgit looks in the parent directory
564 Do not delete the destination directory if clone fails.
567 Prints debugging information to stderr. Repeating the option produces
568 more output (currently, up to -DDDD is meaningfully different).
571 Specifies a git configuration option, to be used for this run.
572 dgit itself is also controlled by git configuration options.
574 .RI \fB-v\fR version "|\fB_\fR | " \fB--since-version=\fR version |\fB_\fR
577 option to pass to dpkg-genchanges, during builds. Changes (from
578 debian/changelog) since this version will be included in the built
579 changes file, and hence in the upload. If this option is not
580 specified, dgit will query the archive and use the latest version
581 uploaded to the intended suite.
585 inhibits this, so that no -v option will be passed to dpkg-genchanges
586 (and as a result, only the last stanza from debian/changelog will
587 be used for the build and upload).
589 .RI \fB-m\fR maintaineraddress
590 Passed to dpkg-genchanges (eventually).
592 .RI \fB--ch:\fR option
593 Specifies a single additional option to pass, eventually, to
596 Options which are safe to pass include
597 .BR "-si -sa -sd -C" .
599 For other options the caveat below applies.
601 .RI \fB--curl:\fR option " | \fB--dput:\fR" option " |..."
602 Specifies a single additional option to pass to
607 .BR dpkg-buildpackage ,
608 .BR dpkg-genchanges ,
616 Can be repeated as necessary.
618 Use of this ability should not normally be necessary.
619 It is provided for working around bugs,
620 or other unusual situations.
621 If you use these options,
622 you may violate dgit's assumptions
623 about the behaviour of its subprograms
626 For dpkg-buildpackage, dpkg-genchanges, mergechanges and sbuild,
627 the option applies only when the program is invoked directly by dgit.
628 Usually, for passing options to dpkg-genchanges, you should use
629 .BR --ch: \fIoption\fR.
631 Specifying --git is not effective for some lower-level read-only git
632 operations performed by dgit, and also not when git is invoked by
633 another program run by dgit.
635 See notes below regarding ssh and dgit.
637 NB that --gpg:option is not supported (because debsign does not
643 distro config setting.
645 .RI \fB--curl=\fR program " | \fB--dput=\fR" program " |..."
646 Specifies alternative programs to use instead of
651 .BR dpkg-buildpackage ,
652 .BR dpkg-genchanges ,
664 .BR dpkg-buildpackage ,
665 .BR dpkg-genchanges ,
669 this applies only when the program is invoked directly by dgit.
673 specifies the command to run on the remote host when dgit
674 rpush needs to invoke a remote copy of itself. (dgit also reinvokes
675 itself as the EDITOR for dpkg-source --commit; this is done using
676 argv[0], and is not affected by --dgit=).
680 is used instead of gbp build or git-buildpackage. (The default is
681 the latter unless the former exists on PATH.)
684 is used instead of gbp pq.
686 unusually, the specified value is split on whitespace
687 to produce a command and possibly some options and/or arguments.
691 the default value is taken from the
695 environment variables, if set (see below). And, for ssh, when accessing the
696 archive and dgit-repos, this command line setting is overridden by the
698 .BI dgit-distro. distro .ssh
701 (which can in turn be overridden with -c). Also, when dgit is using
702 git to access dgit-repos, only git's idea of what ssh to use (eg,
706 .BI --existing-package= package
707 dgit push needs to canonicalise the suite name. Sometimes, dgit
708 lacks a way to ask the archive to do this without knowing the
709 name of an existing package. Without --new we can just use the
710 package we are trying to push. But with --new that will not work, so
713 or use the value of this option. This option is not needed with the
714 default mechanisms for accessing the archive.
717 Print a usage summary.
719 .BI --initiator-tempdir= directory
720 dgit rpush uses a temporary directory on the invoking (signing) host.
721 This option causes dgit to use
723 instead. Furthermore, the specified directory will be emptied,
724 removed and recreated before dgit starts, rather than removed
725 after dgit finishes. The directory specified must be an absolute
728 .BI --force- something
729 Instructs dgit to try to proceed despite detecting
730 what it thinks is going to be a fatal problem.
731 .B This is probably not going to work.
732 These options are provided as an escape hatch,
733 in case dgit is confused.
734 (They might also be useful for testing error cases.)
736 .B --force-unrepresentable
738 dgit thinks that your git tree contains changes
739 (relative to your .orig tarballs)
740 which dpkg-source is not able to represent.
741 Your build or push will probably fail later.
743 .B --force-unsupported-source-format
744 Carry on despite dgit not understanding your source package format.
745 dgit will probably mishandle it.
747 .B --force-dsc-changes-mismatch
748 Do not check whether .dsc and .changes match.
749 The archive will probably reject your upload.
751 .BR --force-import-gitapply-absurd " | " --force-import-gitapply-no-absurd
752 Force on or off the use of the absurd git-apply emulation
753 when running gbp pq import
754 when importing a package from a .dsc.
755 See Debian bug #841867.
756 .SH WORKFLOW - SIMPLE
757 It is always possible with dgit to clone or fetch a package, make
758 changes in git (using git-commit) on the suite branch
759 .RB ( "git checkout dgit/" \fIsuite\fR)
760 and then dgit push. You can use whatever gitish techniques you like
761 to construct the commits to push;
762 the only requirement is that what you push is a
763 descendant of the state of the archive, as provided by dgit in the
764 remote tracking branch
765 .BR remotes/dgit/dgit/ \fIsuite\fR.
767 If you are using dgit to do an NMU (in Debian),
768 and don't know about the
769 maintainers' preferred packaging workflows, you should make your
770 changes as a linear series of (logicially separated) commits on top of
771 what's already in the archive.
773 If you are lucky the other uploaders have also used dgit and
774 integrated the other relevant git history; if not you can fetch it
775 into your tree and cherry-pick etc. as you wish.
776 .SH WORKFLOW - INTEGRATING BETWEEN DGIT AND OTHER GIT HISTORY
777 If you are the maintainer of a package dealing with uploads made
778 without dgit, you will probably want to merge the synthetic commits
779 (made by dgit to represent the uploads) into your git history.
780 Normally you can just merge the dgit branch into your own master, or
781 indeed if you do your work on the dgit local suite branch
783 you can just use dgit pull.
785 However the first time dgit is used it will generate a new origin
786 commit from the archive which won't be linked into the rest of your
787 git history. You will need to merge this.
789 If last upload was in fact made with git, you should usually proceed
790 as follows: identify the commit which was actually used to build the
791 package. (Hopefully you have a tag for this.) Check out the dgit
793 .RB ( "git checkout dgit/" \fIsuite\fR)
794 and merge that other commit
795 .RB ( "git merge debian/" \fIversion\fR).
796 Hopefully this merge will be trivial because the two trees should
797 be very similar. The resulting branch head can be merged into your
799 .RB ( "git checkout master && git merge dgit/" \fIsuite\fR).
801 If last upload was not made with git, a different approach is required
802 to start using dgit. First, do
804 (or clone) to obtain a git history representation of what's in the
805 archive and record it in the
806 .BI remotes/dgit/dgit/ suite
807 tracking branch. Then somehow, using your other git history
808 plus appropriate diffs and cherry picks from the dgit remote tracking
809 branch, construct a git commit whose tree corresponds to the tree to use for the
812 between what's in the archive and what you intend to upload.
815 to actually upload the result.
817 If the commit-to-be-uploaded is not a descendant of the
818 dgit remote tracking branch, you will need to pass
822 dgit can be configured via the git config system.
823 You may set keys with git-config (either in system-global or per-tree
824 configuration), or provide
826 on the dgit command line.
828 Settings likely to be useful for an end user include:
830 .BR dgit-suite. \fIsuite\fR .distro " \fIdistro\fR"
831 Specifies the distro for a suite. dgit keys off the suite name (which
832 appears in changelogs etc.), and uses that to determine the distro
833 which is involved. The config used is thereafter that for the distro.
835 .BI dgit.default.distro " distro"
836 The default distro for an unknown suite.
840 .BR dgit-distro. \fIdistro\fR . *,
841 the default value used if there is no distro-specific setting.
843 .BR dgit-distro. \fIdistro\fR .clean-mode
844 One of the values for the command line --clean= option; used if
845 --clean is not specified.
847 .BR dgit-distro. \fIdistro\fR .quilt-mode
848 One of the values for the command line --quilt= option; used if
849 --quilt is not specified.
851 .BR dgit-distro. \fIdistro\fR .rm-old-changes
852 Boolean, used if neither \-\-rm-old-changes nor \-\-no-rm-old-changes
853 is specified. The default is not to remove.
855 .BR dgit-distro. \fIdistro\fR .readonly " " auto | a " | " true | t | y | 1 " | " false | f | n | 0
856 Whether you have push access to the distro.
857 For Debian, it is OK to use auto, which uses readonly mode if you are
858 not pushing right now;
859 but, setting this to false will avoid relying on the mirror of the dgit
860 git repository server.
862 .BI dgit-distro. distro .keyid
866 .BI dgit-distro. distro .mirror " url"
868 .BI dgit-distro. distro .username
869 Not relevant for Debian.
871 .BI dgit-distro. distro .upload-host
872 Might be useful if you have an intermediate queue server.
874 .BI dgit-distro. distro .user-name " " dgit-distro. distro .user-email
875 Values to configure for user.name and user.email in new git trees. If
876 not specified, the DEBFULLNAME and DEBEMAIL environment variables are
877 used, respectively. Only used if .setup-usermail is not disabled.
879 .BI dgit-distro. distro .setup-useremail
880 Whether to set user.name and user.email in new git trees.
881 True by default. Ignored for dgit setup-setup-useremail, which does it anyway.
883 .BI dgit-distro. distro .setup-mergechangelogs
884 Whether to setup a merge driver which uses dpkg-mergechangelogs for
885 debian/changelog. True by default. Ignored for dgit
886 setup-mergechangelogs, which does it anyway.
888 .BI dgit-distro. distro .cmd- cmd
889 Program to use instead of
892 .BR -- \fIcmd\fR = "... ."
894 .BI dgit-distro. distro .opts- cmd
895 Extra options to pass to
898 .BR -- \fIcmd\fR : "... ."
899 To pass several options, configure multiple values in git config
900 (with git config --add). The options for
901 .BI dgit.default.opts- cmd
902 .BI dgit-distro. distro /push.opts- cmd
903 and are all used, followed by options from dgit's command line.
904 .SH ACCESS CONFIGURATION
905 There are many other settings which specify how a particular distro's
906 services (archive and git) are provided. These should not normally be
907 adjusted, but are documented for the benefit of distros who wish to
910 .BR dgit-distro. \fIdistro\fR /push. *
911 If set, overrides corresponding non \fB/push\fR config when
916 .BI dgit-distro. distro .git-url
918 .BR dgit-distro. \fIdistro\fR .git-url [ -suffix ]
920 .BI dgit-distro. distro .git-proto
922 .BI dgit-distro. distro .git-path
924 .BR dgit-distro. \fIdistro\fR .git-check " " true | false | url | ssh-cmd
926 .BI dgit-distro. distro .git-check-suffix
928 .BR dgit-distro. \fIdistro\fR .diverts.divert " " new-distro | / \fIdistro-suffix\fR
930 .BI dgit-distro. distro .git-create " " ssh-cmd | true
932 .BR dgit-distro. \fIdistro\fR .archive-query " " ftpmasterapi: " | " madison: "\fIdistro\fR | " dummycat: "\fI/path\fR | " sshpsql: \fIuser\fR @ \fIhost\fR : \fIdbname\fR
934 .BR dgit-distro. \fIdistro\fR .archive-query- ( url | tls-key | curl-ca-args )
936 .BI dgit-distro. distro .madison-distro
938 .BI dgit-distro. distro .archive-query-default-component
940 .BI dgit-distro. distro .dgit-tag-format
942 .BI dgit-distro. distro .ssh
944 .BI dgit-distro. distro .sshpsql-dbname
946 .BR dgit-distro. \fIdistro\fR . ( git | sshpsql ) - ( user | host | user-force )
948 .BI dgit-distro. distro .backports-quirk
949 .SH ENVIRONMENT VARIABLES
951 .BR DGIT_SSH ", " GIT_SSH
952 specify an alternative default program (and perhaps arguments) to use
953 instead of ssh. DGIT_SSH is consulted first and may contain arguments;
954 if it contains any whitespace will be passed to the shell. GIT_SSH
955 specifies just the program; no arguments can be specified, so dgit
956 interprets it the same way as git does.
958 also the --ssh= and --ssh: options.
960 .BR DEBEMAIL ", " DEBFULLNAME
961 Default git user.email and user.name for new trees. See
962 .BR "dgit setup-new-tree" .
964 .BR gpg ", " dpkg- "..., " debsign ", " git ", " curl ", " dput ", " LWP::UserAgent
965 and other subprograms and modules used by dgit are affected by various
966 environment variables. Consult the documentaton for those programs
970 a `dgit rebase-prep' command or some such to turn a
971 fast-forwarding branch containing pseudo-merges
972 back into a rebasing patch stack.
973 It might have to leave a note
974 for a future dgit push.
976 If the dgit push fails halfway through,
977 it is not necessarily restartable and
979 It would be good to check that the proposed signing key is
980 available before starting work.
982 dgit's build functions, and dgit push, may make changes to
983 your current HEAD. Sadly this is necessary for packages in the `3.0
984 (quilt)' source format. This is ultimately due to what I consider
985 design problems in quilt and dpkg-source.
987 --dry-run does not always work properly, as not doing some of the git
988 fetches may result in subsequent actions being different. Doing a
989 non-dry-run dgit fetch first will help.
990 --damp-run is likely to work much better.
998 \fBgit-buildpackage\fP(1),
999 \fBdpkg-buildpackage\fP(1),
1001 https://browse.dgit.debian.org/