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-native(7) for maintainers of Debian-native packages
41 dgit-maint-merge(7) for maintainers: using a merging git workflow
42 dgit-maint-gbp(7) for maintainers: using git-buildpackage
43 dgit-sponsorship(7) for sponsors and sponsored contributors
46 See \fBdgit(7)\fP for detailed information about the data
48 common problems likely to arise with certain kinds of package,
52 \fBdgit clone\fR \fIpackage\fP [\fIsuite\fP] [\fB./\fP\fIdir|\fB/\fP\fIdir\fR]
53 Consults the archive and dgit-repos to construct the git view of
60 in a new directory (named
63 also, downloads any necessary orig tarballs.
65 The suite's git tip is
66 left on the local branch
68 ready for work, and on the corresponding dgit remote tracking branch.
71 remote will be set up to point to the package's dgit-repos tree
72 for the distro to which
76 For your convenience, the
78 remote will be set up from the package's Vcs-Git field, if there is
79 one - but note that in the general case the history found there may be
80 different to or even disjoint from dgit's view.
82 \fBdgit fetch\fR [\fIsuite\fP]
83 Consults the archive and git-repos to update the git view of
84 history for a specific suite (and downloads any necessary orig
85 tarballs), and updates the remote tracking branch
86 .BR remotes/dgit/dgit/ \fIsuite\fR.
87 If the current branch is
89 then dgit fetch defaults to
91 otherwise it parses debian/changelog and uses the suite specified
94 \fBdgit pull\fR [\fIsuite\fP]
95 Does dgit fetch, and then merges the new head of the remote tracking
97 .BI remotes/dgit/dgit/ suite
98 into the current branch.
103 with some suitable options. Options and arguments after build
104 will be passed on to dpkg-buildpackage. It is not necessary to use
105 dgit build when using dgit; it is OK to use any approach which ensures
106 that the generated source package corresponds to the relevant git
109 Tagging, signing and actually uploading should be left to dgit push.
111 \fBdgit build-source\fR ...
112 Builds the source package, and a changes file for a prospective
113 source-only upload, using
115 The output is left in
116 .IR package \fB_\fR version \fB.dsc\fR
118 .IR package \fB_\fR version \fB_source.changes\fR.
120 Tagging, signing and actually uploading should be left to dgit push.
123 Cleans the current working tree (according to the --clean= option in
127 Print a usage summary.
129 \fBdgit sbuild\fR ...
130 Constructs the source package, uses
132 to do a binary build, and uses mergechanges to merge the source and
133 binary changes files. Options and arguments after sbuild will be
135 The output is left in
136 .IR package \fB_\fR version \fB_multi.changes\fR.
138 Tagging, signing and actually uploading should be left to dgit push.
140 \fBdgit gbp-build\fR ...
143 with some suitable options. Options and arguments after gbp-build
144 will be passed on to git-buildpackage.
146 By default this uses \-\-quilt=gbp, so HEAD should be a
147 git-buildpackage style branch, not a patches-applied branch.
149 Tagging, signing and actually uploading should be left to dgit push.
151 \fBdgit push\fR [\fIsuite\fP]
152 Does an `upload', pushing the current HEAD to the archive (as a source
153 package) and to dgit-repos (as git commits). The package must already
154 have been built ready for upload, with the .dsc and .changes
155 left in the parent directory. It is normally best to do the build
156 with dgit too (eg with dgit sbuild): some existing build tools pass
157 unhelpful options to dpkg-source et al by default, which can result in
158 the built source package not being identical to the git tree.
160 In more detail: dgit push checks that the current HEAD corresponds to
161 the .dsc. It then pushes the HEAD to the suite's dgit-repos branch,
162 makes a signed git tag, edits the .dsc to contain the dgit metadata
163 field, runs debsign to sign the upload (.dsc and .changes), pushes the
164 signed tag, and finally uses dput to upload the .changes to the
167 dgit push always uses the package, suite and version specified in the
168 debian/changelog and the .dsc, which must agree. If the command line
169 specifies a suite then that must match too.
171 If dgit push fails while uploading, it is fine to simply retry the
172 dput on the .changes file at your leisure.
174 \fBdgit rpush\fR \fIbuild-host\fR\fB:\fR\fIbuild-dir\fR [\fIpush args...\fR]
175 Pushes the contents of the specified directory on a remote machine.
176 This is like running dgit push on build-host with build-dir as the
177 current directory; however, signing operations are done on the
178 invoking host. This allows you to do a push when the system which has
179 the source code and the build outputs has no access to the key:
181 1. Clone on build host (dgit clone)
183 2. Edit code on build host (edit, git commit)
185 3. Build package on build host (dgit build)
187 4. Test package on build host or elsewhere (dpkg -i, test)
189 5. Upload by invoking dgit rpush on host with your GPG key.
191 However, the build-host must be able to ssh to the dgit repos. If
192 this is not already the case, you must organise it separately, for
193 example by the use of ssh agent forwarding.
195 The remaining arguments are treated just as dgit push would handle
198 build-host and build\-dir can be passed as separate
199 arguments; this is assumed to be the case if the first argument
200 contains no : (except perhaps one in [ ], to support IPv6 address
203 You will need similar enough versions of dgit on the build-host and
204 the invocation host. The build-host needs gnupg installed, with your
205 public key in its keyring (but not your private key, obviously).
207 .B dgit setup-new-tree
208 Configure the current working tree the way that dgit clone would have
209 set it up. Like running
210 .B dgit setup-useremail
212 .B setup-mergechangelogs
213 (but only does each thing if dgit is configured to do it automatically).
214 You can use these in any git repository, not just ones used with
215 the other dgit operations.
217 .B dgit setup-useremail
218 Set the working tree's user.name and user.email from the
219 distro-specific dgit configuration
220 .RB ( dgit-distro. \fIdistro\fR .user-name " and " .user-email ),
221 or DEBFULLNAME or DEBEMAIL.
223 .B dgit setup-mergechangelogs
224 Configures a git merge helper for the file
227 .BR dpkg-mergechangelogs .
230 `3.0 (quilt)' format source packages need changes representing not
231 only in-tree but also as patches in debian/patches. dgit quilt-fixup
232 checks whether this has been done; if not, dgit will make appropriate
233 patches in debian/patches and also commit the resulting changes to
236 This is normally done automatically by dgit build and dgit push.
238 dgit will try to turn each relevant commit in your git history into a
239 new quilt patch. dgit cannot convert nontrivial merges, or certain
240 other kinds of more exotic history. If dgit can't find a suitable
241 linearisation of your history, by default it will fail, but you can
242 ask it to generate a single squashed patch instead.
245 Prints version information and exits.
247 .BI "dgit clone-dgit-repos-server" " destdir"
248 Tries to fetch a copy of the source code for the dgit-repos-server,
249 as actually being used on the dgit git server, as a git tree.
252 .BR --dry-run " | " -n
253 Go through the motions, fetching all information needed, but do not
254 actually update the output(s). For push, dgit does
255 the required checks and leaves the new .dsc in a temporary file,
256 but does not sign, tag, push or upload.
258 .BR --damp-run " | " -L
259 Go through many more of the motions: do everything that doesn't
260 involve either signing things, or making changes on the public
266 for signing the tag and the upload. The default comes from the
269 config setting (see CONFIGURATION, below), or failing that, the
270 uploader trailer line in debian/changelog.
273 does not sign tags or uploads (meaningful only with push).
277 Specifies that we should process source package
279 rather than looking in debian/control or debian/changelog.
280 Valid with dgit fetch and dgit pull, only.
282 .BR --clean=git " | " -wg
285 to clean the working tree,
286 rather than running the package's rules clean target.
288 This will delete all files which are not tracked by git.
289 (Including any files you forgot to git add.)
292 options other than dpkg-source
293 are useful when the package's clean target is troublesome, or
294 to avoid needing the build-dependencies.
296 .BR --clean=git-ff " | " -wgf
298 .BR "git clean -xdff"
299 to clean the working tree.
302 but it also removes any subdirectories containing different git
303 trees (which only unusual packages are likely to create).
305 .BR --clean=check " | " -wc
306 Merely check that the tree is clean (does not contain uncommitted
308 Avoids running rules clean,
309 and can avoid needing the build-dependencies.
311 .BR --clean=none " | " -wn
312 Do not clean the tree, nor check that it is clean.
313 Avoids running rules clean,
314 and can avoid needing the build-dependencies.
316 files which are not in git, or if the build creates such files, a
317 subsequent dgit push will fail.
319 .BR --clean=dpkg-source " | " -wd
320 Use dpkg-buildpackage to do the clean, so that the source package
321 is cleaned by dpkg-source running the package's clean target.
323 Requires the package's build dependencies.
325 .BR --clean=dpkg-source-d " | " -wdd
327 .B dpkg-buildpackage -d
329 so that the source package
330 is cleaned by dpkg-source running the package's clean target.
331 The build-dependencies are not checked (due to
333 which violates policy, but may work in practice.
336 The package is or may be new in this suite. Without this, dgit will
337 refuse to push. It may (for Debian, will) be unable to access the git
338 history for any packages which have been newly pushed and have not yet
342 Do not complain if the working tree does not match your git HEAD.
343 This can be useful with build, if you plan to commit later. (dgit
344 push will still ensure that the .dsc you upload and the git tree
345 you push are identical, so this option won't make broken pushes.)
347 .BR --overwrite =\fIprevious-version\fR
348 Declare that even though your git branch is not a descendant
349 of the version in the archive
350 according to the revision history,
351 it really does contain
352 all the (wanted) changes from that version.
354 This option is useful if you are the maintainer, and you have
355 incorporated NMU changes into your own git workflow in a way that
356 doesn't make your branch a fast forward from the NMU.
359 ought to be the version currently in the archive. If
362 specified, dgit will check that the version in the archive is
363 mentioned in your debian/changelog.
364 (This will avoid losing
365 changes unless someone committed to git a finalised changelog
366 entry, and then made later changes to that version.)
368 dgit push --overwrite
370 pseudo-merge (that is, something that looks like the result
371 of git merge -s ours) to stitch the archive's version into your own
372 git history, so that your push is a fast forward from the archive.
375 .BR gbp ", " dpm " or " unpatched ,
376 implying a split between the dgit view and the
377 maintainer view, the pseudo-merge will appear only in the dgit view.)
379 .BI --deliberately- something
380 Declare that you are deliberately doing
382 This can be used to override safety catches, including safety catches
383 which relate to distro-specific policies.
384 The use of --deliberately is declared and published in the signed tags
385 generated for you by dgit,
386 so that the archive software can give effect to your intent,
388 for the benefit humans looking at the history.
391 understood in the context of Debian are discussed below:
393 .BR --deliberately-not-fast-forward
394 Declare that you are deliberately rewinding history. When pushing to
395 Debian, use this when you are making a renewed upload of an entirely
396 new source package whose previous version was not accepted for release
397 from NEW because of problems with copyright or redistributibility.
399 .BR --deliberately-include-questionable-history
400 Declare that you are deliberately including, in the git history of
401 your current push, history which contains a previously-submitted
402 version of this package which was not approved (or has not yet been
403 approved) by the ftpmasters. When pushing to Debian, only use this
404 option after verifying that: none of the rejected-from-NEW (or
405 never-accepted) versions in the git history of your current push, were
406 rejected by ftpmaster for copyright or redistributability reasons.
408 .BR --deliberately-fresh-repo
409 Declare that you are deliberately rewinding history and want to
410 throw away the existing repo. Not relevant when pushing to Debian,
411 as the Debian server will do this automatically when necessary.
414 When fixing up source format `3.0 (quilt)' metadata, insist on
415 generating a linear patch stack: one new patch for each relevant
417 If such a stack cannot be generated, fail.
418 This is the default for Debian.
420 HEAD should be a series of plain commits
421 (not touching debian/patches/),
423 with as ancestor a patches-applied branch.
426 When fixing up source format `3.0 (quilt)' metadata, prefer to
427 generate a linear patch stack
428 (as with --quilt=auto)
429 but if that doesn't seem possible,
430 try to generate a single squashed patch for all the changes made in git
431 (as with --quilt=smash).
432 This is not a good idea for an NMU in Debian.
435 When fixing up source format `3.0 (quilt)' metadata,
436 generate a single additional patch for all the changes made in git.
437 This is not a good idea for an NMU in Debian.
439 (If HEAD has any in-tree patches already, they must apply cleanly.
440 This will be the case for any trees produced by dgit fetch or clone;
441 if you do not change the upstream version
442 nor make changes in debian/patches,
443 it will remain true.)
446 Check whether source format `3.0 (quilt)' metadata would need fixing
447 up, but, if it does, fail. You must then fix the metadata yourself
448 somehow before pushing. (NB that dpkg-source --commit will not work
449 because the dgit git tree does not have a
453 .BR --quilt=nocheck " | " --no-quilt-fixup
454 Do not check whether up source format `3.0 (quilt)' metadata needs
455 fixing up. If you use this option and the metadata did in fact need
456 fixing up, dgit push will fail.
458 .BR -- [ quilt= ] gbp " | " -- [ quilt= ] dpm " | " --quilt=unapplied
459 Tell dgit that you are using a nearly-dgit-compatible git branch,
461 .BR "maintainer view" ,
463 do not want your branch changed by dgit.
468 is for use with git-buildpackage.
469 Your HEAD is expected to be
470 a patches-unapplied git branch, except that it might contain changes
471 to upstream .gitignore files. This is the default for dgit gbp-build.
476 is for use with git-dpm.
477 Your HEAD is expected to be
478 a patches-applied git branch,
479 except that it might contain changes to upstream .gitignore files.
482 specifies that your HEAD is a patches-unapplied git branch (and
483 that any changes to upstream .gitignore files are represented as
484 patches in debian/patches).
486 With --quilt=gbp|dpm|unapplied,
487 dgit push (or precursors like quilt-fixup and build) will automatically
488 generate a conversion of your git branch into the right form.
489 dgit push will push the
490 dgit-compatible form (the
492 to the dgit git server.
493 The dgit view will be visible to you
494 in the dgit remote tracking branches, but your own branch will
496 dgit push will create a tag
498 for the maintainer view, and the dgit tag
499 .BI archive/debian/ version
501 dgit quilt-fixup will merely do some checks,
502 and cache the maintainer view.
504 .B If you have a branch like this it is essential to specify the appropriate --quilt= option!
505 This is because it is not always possible to tell: a patches-unapplied
506 git branch of a package with one patch, for example, looks very like
507 a patches-applied branch where the user has used git revert to
508 undo the patch, expecting to actually revert it.
509 However, if you fail to specify the right \-\-quilt option,
510 and you aren't too lucky, dgit will notice the problem and stop,
513 .BR -d "\fIdistro\fR | " --distro= \fIdistro\fR
514 Specifies that the suite to be operated on is part of distro
516 This overrides the default value found from the git config option
517 .BR dgit-suite. \fIsuite\fR .distro .
518 The only effect is that other configuration variables (used
519 for accessing the archive and dgit-repos) used are
520 .BR dgit-distro. \fIdistro\fR .* .
522 If your suite is part of a distro that dgit already knows about, you
523 can use this option to make dgit work even if your dgit doesn't know
524 about the suite. For example, specifying
526 will work when the suite is an unknown suite in the Debian archive.
528 To define a new distro it is necessary to define methods and URLs
529 for fetching (and, for dgit push, altering) a variety of information both
530 in the archive and in dgit-repos.
531 How to set this up is not yet documented.
534 Specifies the .changes file which is to be uploaded. By default
535 dgit push looks for single .changes file in the parent directory whose
536 filename suggests it is for the right package and version.
540 pathname contains slashes, the directory part is also used as
542 .BR --build-products-dir ;
543 otherwise, the changes file is expected in that directory (by
548 When doing a build, delete any changes files matching
549 .IB package _ version _*.changes
550 before starting. This ensures that
551 dgit push (and dgit sbuild) will be able to unambigously
552 identify the relevant changes files from the most recent build, even
553 if there have been previous builds with different tools or options.
554 The default is not to remove, but
555 .B \-\-no-rm-old-changes
556 can be used to override a previous \-\-rm-old-changes
557 or the .rm-old-changes configuration setting.
559 .BI --build-products-dir= directory
560 Specifies where to find the built files to be uploaded.
561 By default, dgit looks in the parent directory
565 Do not delete the destination directory if clone fails.
568 Prints debugging information to stderr. Repeating the option produces
569 more output (currently, up to -DDDD is meaningfully different).
572 Specifies a git configuration option, to be used for this run.
573 dgit itself is also controlled by git configuration options.
575 .RI \fB-v\fR version "|\fB_\fR | " \fB--since-version=\fR version |\fB_\fR
578 option to pass to dpkg-genchanges, during builds. Changes (from
579 debian/changelog) since this version will be included in the built
580 changes file, and hence in the upload. If this option is not
581 specified, dgit will query the archive and use the latest version
582 uploaded to the intended suite.
586 inhibits this, so that no -v option will be passed to dpkg-genchanges
587 (and as a result, only the last stanza from debian/changelog will
588 be used for the build and upload).
590 .RI \fB-m\fR maintaineraddress
591 Passed to dpkg-genchanges (eventually).
593 .RI \fB--ch:\fR option
594 Specifies a single additional option to pass, eventually, to
597 Options which are safe to pass include
598 .BR "-si -sa -sd -C" .
600 For other options the caveat below applies.
602 .RI \fB--curl:\fR option " | \fB--dput:\fR" option " |..."
603 Specifies a single additional option to pass to
608 .BR dpkg-buildpackage ,
609 .BR dpkg-genchanges ,
617 Can be repeated as necessary.
619 Use of this ability should not normally be necessary.
620 It is provided for working around bugs,
621 or other unusual situations.
622 If you use these options,
623 you may violate dgit's assumptions
624 about the behaviour of its subprograms
627 For dpkg-buildpackage, dpkg-genchanges, mergechanges and sbuild,
628 the option applies only when the program is invoked directly by dgit.
629 Usually, for passing options to dpkg-genchanges, you should use
630 .BR --ch: \fIoption\fR.
632 Specifying --git is not effective for some lower-level read-only git
633 operations performed by dgit, and also not when git is invoked by
634 another program run by dgit.
636 See notes below regarding ssh and dgit.
638 NB that --gpg:option is not supported (because debsign does not
644 distro config setting.
646 .RI \fB--curl=\fR program " | \fB--dput=\fR" program " |..."
647 Specifies alternative programs to use instead of
652 .BR dpkg-buildpackage ,
653 .BR dpkg-genchanges ,
665 .BR dpkg-buildpackage ,
666 .BR dpkg-genchanges ,
670 this applies only when the program is invoked directly by dgit.
674 specifies the command to run on the remote host when dgit
675 rpush needs to invoke a remote copy of itself. (dgit also reinvokes
676 itself as the EDITOR for dpkg-source --commit; this is done using
677 argv[0], and is not affected by --dgit=).
681 is used instead of gbp build or git-buildpackage. (The default is
682 the latter unless the former exists on PATH.)
685 is used instead of gbp pq.
687 unusually, the specified value is split on whitespace
688 to produce a command and possibly some options and/or arguments.
692 the default value is taken from the
696 environment variables, if set (see below). And, for ssh, when accessing the
697 archive and dgit-repos, this command line setting is overridden by the
699 .BI dgit-distro. distro .ssh
702 (which can in turn be overridden with -c). Also, when dgit is using
703 git to access dgit-repos, only git's idea of what ssh to use (eg,
707 .BI --existing-package= package
708 dgit push needs to canonicalise the suite name. Sometimes, dgit
709 lacks a way to ask the archive to do this without knowing the
710 name of an existing package. Without --new we can just use the
711 package we are trying to push. But with --new that will not work, so
714 or use the value of this option. This option is not needed with the
715 default mechanisms for accessing the archive.
718 Print a usage summary.
720 .BI --initiator-tempdir= directory
721 dgit rpush uses a temporary directory on the invoking (signing) host.
722 This option causes dgit to use
724 instead. Furthermore, the specified directory will be emptied,
725 removed and recreated before dgit starts, rather than removed
726 after dgit finishes. The directory specified must be an absolute
729 .BI --force- something
730 Instructs dgit to try to proceed despite detecting
731 what it thinks is going to be a fatal problem.
732 .B This is probably not going to work.
733 These options are provided as an escape hatch,
734 in case dgit is confused.
735 (They might also be useful for testing error cases.)
737 .B --force-unrepresentable
739 dgit thinks that your git tree contains changes
740 (relative to your .orig tarballs)
741 which dpkg-source is not able to represent.
742 Your build or push will probably fail later.
744 .B --force-unsupported-source-format
745 Carry on despite dgit not understanding your source package format.
746 dgit will probably mishandle it.
748 .B --force-dsc-changes-mismatch
749 Do not check whether .dsc and .changes match.
750 The archive will probably reject your upload.
752 .BR --force-import-gitapply-absurd " | " --force-import-gitapply-no-absurd
753 Force on or off the use of the absurd git-apply emulation
754 when running gbp pq import
755 when importing a package from a .dsc.
756 See Debian bug #841867.
757 .SH WORKFLOW - SIMPLE
758 It is always possible with dgit to clone or fetch a package, make
759 changes in git (using git-commit) on the suite branch
760 .RB ( "git checkout dgit/" \fIsuite\fR)
761 and then dgit push. You can use whatever gitish techniques you like
762 to construct the commits to push;
763 the only requirement is that what you push is a
764 descendant of the state of the archive, as provided by dgit in the
765 remote tracking branch
766 .BR remotes/dgit/dgit/ \fIsuite\fR.
768 If you are using dgit to do an NMU (in Debian),
769 and don't know about the
770 maintainers' preferred packaging workflows, you should make your
771 changes as a linear series of (logicially separated) commits on top of
772 what's already in the archive.
774 If you are lucky the other uploaders have also used dgit and
775 integrated the other relevant git history; if not you can fetch it
776 into your tree and cherry-pick etc. as you wish.
777 .SH WORKFLOW - INTEGRATING BETWEEN DGIT AND OTHER GIT HISTORY
778 If you are the maintainer of a package dealing with uploads made
779 without dgit, you will probably want to merge the synthetic commits
780 (made by dgit to represent the uploads) into your git history.
781 Normally you can just merge the dgit branch into your own master, or
782 indeed if you do your work on the dgit local suite branch
784 you can just use dgit pull.
786 However the first time dgit is used it will generate a new origin
787 commit from the archive which won't be linked into the rest of your
788 git history. You will need to merge this.
790 If last upload was in fact made with git, you should usually proceed
791 as follows: identify the commit which was actually used to build the
792 package. (Hopefully you have a tag for this.) Check out the dgit
794 .RB ( "git checkout dgit/" \fIsuite\fR)
795 and merge that other commit
796 .RB ( "git merge debian/" \fIversion\fR).
797 Hopefully this merge will be trivial because the two trees should
798 be very similar. The resulting branch head can be merged into your
800 .RB ( "git checkout master && git merge dgit/" \fIsuite\fR).
802 If last upload was not made with git, a different approach is required
803 to start using dgit. First, do
805 (or clone) to obtain a git history representation of what's in the
806 archive and record it in the
807 .BI remotes/dgit/dgit/ suite
808 tracking branch. Then somehow, using your other git history
809 plus appropriate diffs and cherry picks from the dgit remote tracking
810 branch, construct a git commit whose tree corresponds to the tree to use for the
813 between what's in the archive and what you intend to upload.
816 to actually upload the result.
818 If the commit-to-be-uploaded is not a descendant of the
819 dgit remote tracking branch, you will need to pass
823 dgit can be configured via the git config system.
824 You may set keys with git-config (either in system-global or per-tree
825 configuration), or provide
827 on the dgit command line.
829 Settings likely to be useful for an end user include:
831 .BR dgit-suite. \fIsuite\fR .distro " \fIdistro\fR"
832 Specifies the distro for a suite. dgit keys off the suite name (which
833 appears in changelogs etc.), and uses that to determine the distro
834 which is involved. The config used is thereafter that for the distro.
836 .BI dgit.default.distro " distro"
837 The default distro for an unknown suite.
841 .BR dgit-distro. \fIdistro\fR . *,
842 the default value used if there is no distro-specific setting.
844 .BR dgit-distro. \fIdistro\fR .clean-mode
845 One of the values for the command line --clean= option; used if
846 --clean is not specified.
848 .BR dgit-distro. \fIdistro\fR .quilt-mode
849 One of the values for the command line --quilt= option; used if
850 --quilt is not specified.
852 .BR dgit-distro. \fIdistro\fR .rm-old-changes
853 Boolean, used if neither \-\-rm-old-changes nor \-\-no-rm-old-changes
854 is specified. The default is not to remove.
856 .BR dgit-distro. \fIdistro\fR .readonly " " auto | a " | " true | t | y | 1 " | " false | f | n | 0
857 Whether you have push access to the distro.
858 For Debian, it is OK to use auto, which uses readonly mode if you are
859 not pushing right now;
860 but, setting this to false will avoid relying on the mirror of the dgit
861 git repository server.
863 .BI dgit-distro. distro .keyid
867 .BI dgit-distro. distro .mirror " url"
869 .BI dgit-distro. distro .username
870 Not relevant for Debian.
872 .BI dgit-distro. distro .upload-host
873 Might be useful if you have an intermediate queue server.
875 .BI dgit-distro. distro .user-name " " dgit-distro. distro .user-email
876 Values to configure for user.name and user.email in new git trees. If
877 not specified, the DEBFULLNAME and DEBEMAIL environment variables are
878 used, respectively. Only used if .setup-usermail is not disabled.
880 .BI dgit-distro. distro .setup-useremail
881 Whether to set user.name and user.email in new git trees.
882 True by default. Ignored for dgit setup-setup-useremail, which does it anyway.
884 .BI dgit-distro. distro .setup-mergechangelogs
885 Whether to setup a merge driver which uses dpkg-mergechangelogs for
886 debian/changelog. True by default. Ignored for dgit
887 setup-mergechangelogs, which does it anyway.
889 .BI dgit-distro. distro .cmd- cmd
890 Program to use instead of
893 .BR -- \fIcmd\fR = "... ."
895 .BI dgit-distro. distro .opts- cmd
896 Extra options to pass to
899 .BR -- \fIcmd\fR : "... ."
900 To pass several options, configure multiple values in git config
901 (with git config --add). The options for
902 .BI dgit.default.opts- cmd
903 .BI dgit-distro. distro /push.opts- cmd
904 and are all used, followed by options from dgit's command line.
905 .SH ACCESS CONFIGURATION
906 There are many other settings which specify how a particular distro's
907 services (archive and git) are provided. These should not normally be
908 adjusted, but are documented for the benefit of distros who wish to
911 .BR dgit-distro. \fIdistro\fR /push. *
912 If set, overrides corresponding non \fB/push\fR config when
917 .BI dgit-distro. distro .git-url
919 .BR dgit-distro. \fIdistro\fR .git-url [ -suffix ]
921 .BI dgit-distro. distro .git-proto
923 .BI dgit-distro. distro .git-path
925 .BR dgit-distro. \fIdistro\fR .git-check " " true | false | url | ssh-cmd
927 .BI dgit-distro. distro .git-check-suffix
929 .BR dgit-distro. \fIdistro\fR .diverts.divert " " new-distro | / \fIdistro-suffix\fR
931 .BI dgit-distro. distro .git-create " " ssh-cmd | true
933 .BR dgit-distro. \fIdistro\fR .archive-query " " ftpmasterapi: " | " madison: "\fIdistro\fR | " dummycat: "\fI/path\fR | " sshpsql: \fIuser\fR @ \fIhost\fR : \fIdbname\fR
935 .BR dgit-distro. \fIdistro\fR .archive-query- ( url | tls-key | curl-ca-args )
937 .BI dgit-distro. distro .madison-distro
939 .BI dgit-distro. distro .archive-query-default-component
941 .BI dgit-distro. distro .dgit-tag-format
943 .BI dgit-distro. distro .ssh
945 .BI dgit-distro. distro .sshpsql-dbname
947 .BR dgit-distro. \fIdistro\fR . ( git | sshpsql ) - ( user | host | user-force )
949 .BI dgit-distro. distro .backports-quirk
950 .SH ENVIRONMENT VARIABLES
952 .BR DGIT_SSH ", " GIT_SSH
953 specify an alternative default program (and perhaps arguments) to use
954 instead of ssh. DGIT_SSH is consulted first and may contain arguments;
955 if it contains any whitespace will be passed to the shell. GIT_SSH
956 specifies just the program; no arguments can be specified, so dgit
957 interprets it the same way as git does.
959 also the --ssh= and --ssh: options.
961 .BR DEBEMAIL ", " DEBFULLNAME
962 Default git user.email and user.name for new trees. See
963 .BR "dgit setup-new-tree" .
965 .BR gpg ", " dpkg- "..., " debsign ", " git ", " curl ", " dput ", " LWP::UserAgent
966 and other subprograms and modules used by dgit are affected by various
967 environment variables. Consult the documentaton for those programs
971 a `dgit rebase-prep' command or some such to turn a
972 fast-forwarding branch containing pseudo-merges
973 back into a rebasing patch stack.
974 It might have to leave a note
975 for a future dgit push.
977 If the dgit push fails halfway through,
978 it is not necessarily restartable and
980 It would be good to check that the proposed signing key is
981 available before starting work.
983 dgit's build functions, and dgit push, may make changes to
984 your current HEAD. Sadly this is necessary for packages in the `3.0
985 (quilt)' source format. This is ultimately due to what I consider
986 design problems in quilt and dpkg-source.
988 --dry-run does not always work properly, as not doing some of the git
989 fetches may result in subsequent actions being different. Doing a
990 non-dry-run dgit fetch first will help.
991 --damp-run is likely to work much better.
999 \fBgit-buildpackage\fP(1),
1000 \fBdpkg-buildpackage\fP(1),
1002 https://browse.dgit.debian.org/