1 .TH dgit 1 "" "Debian Project" "dgit"
3 dgit \- git integration with the Debian archive
7 [\fIdgit\-opts\fP] \fBclone\fP [\fIdgit\-opts\fP]
8 \fIpackage\fP [\fIsuite\fP] [\fB./\fP\fIdir|\fB/\fP\fIdir\fR]
11 [\fIdgit\-opts\fP] \fBfetch\fP|\fBpull\fP [\fIdgit\-opts\fP]
15 [\fIdgit\-opts\fP] \fBbuild\fP|\fBsbuild\fP|\fBbuild-source\fP
19 [\fIdgit\-opts\fP] \fBpush\fP [\fIdgit\-opts\fP]
23 [\fIdgit\-opts\fP] \fBrpush\fR \fIbuild-host\fR\fB:\fR\fIbuild-dir\fR
27 [\fIdgit\-opts\fP] \fIaction\fR ...
30 allows you to treat the Debian archive as if it were a git
31 repository. See \fBdgit\fP(7) for detailed information about the data
32 model, common problems likely to arise with certain kinds of package,
35 The usual workflow is:
37 1. \fBdgit clone\fR or \fBfetch\fR;
39 2. make, do dev tests, and commit changes in git as desired;
41 3. build packages for upload, using e.g. \fBdgit sbuild\fR
43 4. do pre-upload tests of the proposed upload;
48 \fBdgit clone\fR \fIpackage\fP [\fIsuite\fP] [\fB./\fP\fIdir|\fB/\fP\fIdir\fR]
49 Consults the archive and dgit-repos to construct the git view of
56 in a new directory (named
59 also, downloads any necessary orig tarballs.
61 The suite's git tip is
62 left on the local branch
64 ready for work, and on the corresponding dgit remote tracking branch.
67 remote will be set up to point to the package's dgit-repos tree
68 for the distro to which
72 For your convenience, the
74 remote will be set up from the package's Vcs-Git field, if there is
75 one - but note that in the general case the history found there may be
76 different to or even disjoint from dgit's view.
78 \fBdgit fetch\fR [\fIsuite\fP]
79 Consults the archive and git-repos to update the git view of
80 history for a specific suite (and downloads any necessary orig
81 tarballs), and updates the remote tracking branch
82 .BR remotes/dgit/dgit/ \fIsuite\fR.
83 If the current branch is
85 then dgit fetch defaults to
87 otherwise it parses debian/changelog and uses the suite specified
90 \fBdgit pull\fR [\fIsuite\fP]
91 Does dgit fetch, and then merges the new head of the remote tracking
93 .BI remotes/dgit/dgit/ suite
94 into the current branch.
99 with some suitable options. Options and arguments after build
100 will be passed on to dpkg-buildpackage. It is not necessary to use
101 dgit build when using dgit; it is OK to use any approach which ensures
102 that the generated source package corresponds to the relevant git
105 Tagging, signing and actually uploading should be left to dgit push.
107 \fBdgit build-source\fR ...
108 Builds the source package, and a changes file for a prospective
109 source-only upload, using
111 The output is left in
112 .IR package \fB_\fR version \fB.dsc\fR
114 .IR package \fB_\fR version \fB_source.changes\fR.
116 Tagging, signing and actually uploading should be left to dgit push.
119 Cleans the current working tree (according to the --clean= option in
123 Print a usage summary.
125 \fBdgit sbuild\fR ...
126 Constructs the source package, uses
128 to do a binary build, and uses mergechanges to merge the source and
129 binary changes files. Options and arguments after sbuild will be
131 The output is left in
132 .IR package \fB_\fR version \fB_multi.changes\fR.
134 Tagging, signing and actually uploading should be left to dgit push.
136 \fBdgit gbp-build\fR ...
139 with some suitable options. Options and arguments after gbp-build
140 will be passed on to git-buildpackage.
142 By default this uses \-\-quilt=gbp, so HEAD should be a
143 git-buildpackage style branch, not a patches-applied branch.
145 Tagging, signing and actually uploading should be left to dgit push.
147 \fBdgit push\fR [\fIsuite\fP]
148 Does an `upload', pushing the current HEAD to the archive (as a source
149 package) and to dgit-repos (as git commits). The package must already
150 have been built ready for upload, with the .dsc and .changes
151 left in the parent directory. It is normally best to do the build
152 with dgit too (eg with dgit sbuild): some existing build tools pass
153 unhelpful options to dpkg-source et al by default, which can result in
154 the built source package not being identical to the git tree.
156 In more detail: dgit push checks that the current HEAD corresponds to
157 the .dsc. It then pushes the HEAD to the suite's dgit-repos branch,
158 makes a signed git tag, edits the .dsc to contain the dgit metadata
159 field, runs debsign to sign the upload (.dsc and .changes), pushes the
160 signed tag, and finally uses dput to upload the .changes to the
163 dgit push always uses the package, suite and version specified in the
164 debian/changelog and the .dsc, which must agree. If the command line
165 specifies a suite then that must match too.
167 If dgit push fails while uploading, it is fine to simply retry the
168 dput on the .changes file at your leisure.
170 \fBdgit rpush\fR \fIbuild-host\fR\fB:\fR\fIbuild-dir\fR [\fIpush args...\fR]
171 Pushes the contents of the specified directory on a remote machine.
172 This is like running dgit push on build-host with build-dir as the
173 current directory; however, signing operations are done on the
174 invoking host. This allows you to do a push when the system which has
175 the source code and the build outputs has no access to the key:
177 1. Clone on build host (dgit clone)
179 2. Edit code on build host (edit, git commit)
181 3. Build package on build host (dgit build)
183 4. Test package on build host or elsewhere (dpkg -i, test)
185 5. Upload by invoking dgit rpush on host with your GPG key.
187 However, the build-host must be able to ssh to the dgit repos. If
188 this is not already the case, you must organise it separately, for
189 example by the use of ssh agent forwarding.
191 The remaining arguments are treated just as dgit push would handle
194 build-host and build\-dir can be passed as separate
195 arguments; this is assumed to be the case if the first argument
196 contains no : (except perhaps one in [ ], to support IPv6 address
199 You will need similar enough versions of dgit on the build-host and
200 the invocation host. The build-host needs gnupg installed, with your
201 public key in its keyring (but not your private key, obviously).
203 .B dgit setup-new-tree
204 Configure the current working tree the way that dgit clone would have
205 set it up. Like running
206 .B dgit setup-useremail
208 .B setup-mergechangelogs
209 (but only does each thing if dgit is configured to do it automatically).
210 You can use these in any git repository, not just ones used with
211 the other dgit operations.
213 .B dgit setup-useremail
214 Set the working tree's user.name and user.email from the
215 distro-specific dgit configuration
216 .RB ( dgit-distro. \fIdistro\fR .user-name " and " .user-email ),
217 or DEBFULLNAME or DEBEMAIL.
219 .B dgit setup-mergechangelogs
220 Configures a git merge helper for the file
223 .BR dpkg-mergechangelogs .
226 `3.0 (quilt)' format source packages need changes representing not
227 only in-tree but also as patches in debian/patches. dgit quilt-fixup
228 checks whether this has been done; if not, dgit will make appropriate
229 patches in debian/patches and also commit the resulting changes to
232 This is normally done automatically by dgit build and dgit push.
234 dgit will try to turn each relevant commit in your git history into a
235 new quilt patch. dgit cannot convert nontrivial merges, or certain
236 other kinds of more exotic history. If dgit can't find a suitable
237 linearisation of your history, by default it will fail, but you can
238 ask it to generate a single squashed patch instead.
241 Prints version information and exits.
243 .BI "dgit clone-dgit-repos-server" " destdir"
244 Tries to fetch a copy of the source code for the dgit-repos-server,
245 as actually being used on the dgit git server, as a git tree.
248 .BR --dry-run " | " -n
249 Go through the motions, fetching all information needed, but do not
250 actually update the output(s). For push, dgit does
251 the required checks and leaves the new .dsc in a temporary file,
252 but does not sign, tag, push or upload.
254 .BR --damp-run " | " -L
255 Go through many more of the motions: do everything that doesn't
256 involve either signing things, or making changes on the public
262 for signing the tag and the upload. The default comes from the
265 config setting (see CONFIGURATION, below), or failing that, the
266 uploader trailer line in debian/changelog.
269 does not sign tags or uploads (meaningful only with push).
273 Specifies that we should process source package
275 rather than looking in debian/control or debian/changelog.
276 Valid with dgit fetch and dgit pull, only.
278 .BR --clean=git " | " -wg
281 to clean the working tree,
282 rather than running the package's rules clean target.
284 This will delete all files which are not tracked by git.
285 (Including any files you forgot to git add.)
288 options other than dpkg-source
289 are useful when the package's clean target is troublesome, or
290 to avoid needing the build-dependencies.
292 .BR --clean=git-ff " | " -wgf
294 .BR "git clean -xdff"
295 to clean the working tree.
298 but it also removes any subdirectories containing different git
299 trees (which only unusual packages are likely to create).
301 .BR --clean=check " | " -wc
302 Merely check that the tree is clean (does not contain uncommitted
304 Avoids running rules clean,
305 and can avoid needing the build-dependencies.
307 .BR --clean=none " | " -wn
308 Do not clean the tree, nor check that it is clean.
309 Avoids running rules clean,
310 and can avoid needing the build-dependencies.
312 files which are not in git, or if the build creates such files, a
313 subsequent dgit push will fail.
315 .BR --clean=dpkg-source " | " -wd
316 Use dpkg-buildpackage to do the clean, so that the source package
317 is cleaned by dpkg-source running the package's clean target.
319 Requires the package's build dependencies.
321 .BR --clean=dpkg-source-d " | " -wdd
323 .B dpkg-buildpackage -d
325 so that the source package
326 is cleaned by dpkg-source running the package's clean target.
327 The build-dependencies are not checked (due to
329 which violates policy, but may work in practice.
332 The package is or may be new in this suite. Without this, dgit will
333 refuse to push. It may (for Debian, will) be unable to access the git
334 history for any packages which have been newly pushed and have not yet
338 Do not complain if the working tree does not match your git HEAD.
339 This can be useful with build, if you plan to commit later. (dgit
340 push will still ensure that the .dsc you upload and the git tree
341 you push are identical, so this option won't make broken pushes.)
343 .BR --overwrite =\fIprevious-version\fR
344 Declare that even though your git branch is not a descendant
345 of the version in the archive
346 according to the revision history,
347 it really does contain
348 all the (wanted) changes from that version.
350 This option is useful if you are the maintainer, and you have
351 incorporated NMU changes into your own git workflow in a way that
352 doesn't make your branch a fast forward from the NMU.
355 ought to be the version currently in the archive. If
358 specified, dgit will check that the version in the archive is
359 mentioned in your debian/changelog.
360 (This will avoid losing
361 changes unless someone committed to git a finalised changelog
362 entry, and then made later changes to that version.)
364 dgit push --overwrite
366 pseudo-merge (that is, something that looks like the result
367 of git merge -s ours) to stitch the archive's version into your own
368 git history, so that your push is a fast forward from the archive.
371 .BR gbp ", " dpm " or " unpatched ,
372 implying a split between the dgit view and the
373 maintainer view, the pseudo-merge will appear only in the dgit view.)
375 .BI --deliberately- something
376 Declare that you are deliberately doing
378 This can be used to override safety catches, including safety catches
379 which relate to distro-specific policies. The meanings of
381 understood in the context of Debian are discussed below:
383 .BR --deliberately-not-fast-forward
384 Declare that you are deliberately rewinding history. When pushing to
385 Debian, use this when you are making a renewed upload of an entirely
386 new source package whose previous version was not accepted for release
387 from NEW because of problems with copyright or redistributibility.
389 .BR --deliberately-include-questionable-history
390 Declare that you are deliberately including, in the git history of
391 your current push, history which contains a previously-submitted
392 version of this package which was not approved (or has not yet been
393 approved) by the ftpmasters. When pushing to Debian, only use this
394 option after verifying that: none of the rejected-from-NEW (or
395 never-accepted) versions in the git history of your current push, were
396 rejected by ftpmaster for copyright or redistributability reasons.
398 .BR --deliberately-fresh-repo
399 Declare that you are deliberately rewinding history and want to
400 throw away the existing repo. Not relevant when pushing to Debian,
401 as the Debian server will do this automatically when necessary.
404 When fixing up source format `3.0 (quilt)' metadata, insist on
405 generating a linear patch stack: one new patch for each relevant
407 If such a stack cannot be generated, fail.
408 This is the default for Debian.
410 HEAD should be a series of plain commits
411 (not touching debian/patches/),
413 with as ancestor a patches-applied branch.
416 When fixing up source format `3.0 (quilt)' metadata, prefer to
417 generate a linear patch stack
418 (as with --quilt=auto)
419 but if that doesn't seem possible,
420 try to generate a single squashed patch for all the changes made in git
421 (as with --quilt=smash).
422 This is not a good idea for an NMU in Debian.
425 When fixing up source format `3.0 (quilt)' metadata,
426 generate a single additional patch for all the changes made in git.
427 This is not a good idea for an NMU in Debian.
429 (If HEAD has any in-tree patches already, they must apply cleanly.
430 This will be the case for any trees produced by dgit fetch or clone;
431 if you do not change the upstream version
432 nor make changes in debian/patches,
433 it will remain true.)
436 Check whether source format `3.0 (quilt)' metadata would need fixing
437 up, but, if it does, fail. You must then fix the metadata yourself
438 somehow before pushing. (NB that dpkg-source --commit will not work
439 because the dgit git tree does not have a
443 .BR --quilt=nocheck " | " --no-quilt-fixup
444 Do not check whether up source format `3.0 (quilt)' metadata needs
445 fixing up. If you use this option and the metadata did in fact need
446 fixing up, dgit push will fail.
448 .BR --quilt=gbp " | " --quilt=dpm " | " --quilt=unapplied
449 Tell dgit that you are using a nearly-dgit-compatible git branch,
451 .BR "maintainer view" ,
453 do not want your branch changed by dgit.
456 is for use with git-buildpackage.
457 Your HEAD is expected to be
458 a patches-unapplied git branch, except that it might contain changes
459 to upstream .gitignore files. This is the default for dgit gbp-build.
462 is for use with git-dpm.
463 Your HEAD is expected to be
464 a patches-applied git branch,
465 except that it might contain changes to upstream .gitignore files.
468 specifies that your HEAD is a patches-unapplied git branch (and
469 that any changes to upstream .gitignore files are represented as
470 patches in debian/patches).
472 With --quilt=gbp|dpm|unapplied,
473 dgit push (or precursors like quilt-fixup and build) will automatically
474 generate a conversion of your git branch into the right form.
475 dgit push will push the
476 dgit-compatible form (the
478 to the dgit git server.
479 The dgit view will be visible to you
480 in the dgit remote tracking branches, but your own branch will
482 dgit push will create a tag
484 for the maintainer view, and the dgit tag
485 .BI archive/debian/ version
487 dgit quilt-fixup will merely do some checks,
488 and cache the maintainer view.
490 .B If you have a branch like this it is essential to specify the appropriate --quilt= option!
491 This is because it is not always possible to tell: a patches-unapplied
492 git branch of a package with one patch, for example, looks very like
493 a patches-applied branch where the user has used git revert to
494 undo the patch, expecting to actually revert it.
495 However, if you fail to specify the right \-\-quilt option,
496 and you aren't too lucky, dgit will notice the problem and stop,
500 Prints debugging information to stderr. Repeating the option produces
501 more output (currently, up to -DDDD is meaningfully different).
504 Specifies a git configuration option, to be used for this run.
505 dgit itself is also controlled by git configuration options.
507 .RI \fB-v\fR version "|\fB_\fR | " \fB--since-version=\fR version |\fB_\fR
510 option to pass to dpkg-genchanges, during builds. Changes (from
511 debian/changelog) since this version will be included in the built
512 changes file, and hence in the upload. If this option is not
513 specified, dgit will query the archive and use the latest version
514 uploaded to the intended suite.
518 inhibits this, so that no -v option will be passed to dpkg-genchanges
519 (and as a result, only the last stanza from debian/changelog will
520 be used for the build and upload).
522 .RI \fB-m\fR maintaineraddress
523 Passed to dpkg-genchanges (eventually).
525 .RI \fB--ch:\fR option
526 Specifies a single additional option to pass, eventually, to
529 .RI \fB--curl:\fR option " | \fB--dput:\fR" option " |..."
530 Specifies a single additional option to pass to
535 .BR dpkg-buildpackage ,
536 .BR dpkg-genchanges ,
544 Can be repeated as necessary.
546 Use of this ability should not normally be necessary.
547 It is provided for working around bugs,
548 or other unusual situations.
549 If you use these options,
550 you may violate dgit's assumptions
551 about the behaviour of its subprograms
554 For dpkg-buildpackage, dpkg-genchanges, mergechanges and sbuild,
555 the option applies only when the program is invoked directly by dgit.
556 Usually, for passing options to dpkg-genchanges, you should use
557 .BR --ch: \fIoption\fR.
559 Specifying --git is not effective for some lower-level read-only git
560 operations performed by dgit, and also not when git is invoked by
561 another program run by dgit.
563 See notes below regarding ssh and dgit.
565 NB that --gpg:option is not supported (because debsign does not
571 distro config setting.
573 .RI \fB--curl=\fR program " | \fB--dput=\fR" program " |..."
574 Specifies alternative programs to use instead of
579 .BR dpkg-buildpackage ,
580 .BR dpkg-genchanges ,
592 .BR dpkg-buildpackage ,
593 .BR dpkg-genchanges ,
597 this applies only when the program is invoked directly by dgit.
601 specifies the command to run on the remote host when dgit
602 rpush needs to invoke a remote copy of itself. (dgit also reinvokes
603 itself as the EDITOR for dpkg-source --commit; this is done using
604 argv[0], and is not affected by --dgit=).
608 is used instead of gbp build or git-buildpackage. (The default is
609 the latter unless the former exists on PATH.)
612 is used instead of gbp pq.
614 unusually, the specified value is split on whitespace
615 to produce a command and possibly some options and/or arguments.
619 the default value is taken from the
623 environment variables, if set (see below). And, for ssh, when accessing the
624 archive and dgit-repos, this command line setting is overridden by the
626 .BI dgit-distro. distro .ssh
629 (which can in turn be overridden with -c). Also, when dgit is using
630 git to access dgit-repos, only git's idea of what ssh to use (eg,
634 .BR -d "\fIdistro\fR | " --distro= \fIdistro\fR
635 Specifies that the suite to be operated on is part of distro
637 This overrides the default value found from the git config option
638 .BR dgit-suite. \fIsuite\fR .distro .
639 The only effect is that other configuration variables (used
640 for accessing the archive and dgit-repos) used are
641 .BR dgit-distro. \fIdistro\fR .* .
643 If your suite is part of a distro that dgit already knows about, you
644 can use this option to make dgit work even if your dgit doesn't know
645 about the suite. For example, specifying
647 will work when the suite is an unknown suite in the Debian archive.
649 To define a new distro it is necessary to define methods and URLs
650 for fetching (and, for dgit push, altering) a variety of information both
651 in the archive and in dgit-repos.
652 How to set this up is not yet documented.
655 Specifies the .changes file which is to be uploaded. By default
656 dgit push looks for single .changes file in the parent directory whose
657 filename suggests it is for the right package and version.
661 pathname contains slashes, the directory part is also used as
663 .BR --build-products-dir ;
664 otherwise, the changes file is expected in that directory (by
669 When doing a build, delete any changes files matching
670 .IB package _ version _*.changes
671 before starting. This ensures that
672 dgit push (and dgit sbuild) will be able to unambigously
673 identify the relevant changes files from the most recent build, even
674 if there have been previous builds with different tools or options.
675 The default is not to remove, but
676 .B \-\-no-rm-old-changes
677 can be used to override a previous \-\-rm-old-changes
678 or the .rm-old-changes configuration setting.
680 .BI --build-products-dir= directory
681 Specifies where to find the built files to be uploaded.
682 By default, dgit looks in the parent directory
685 .BI --existing-package= package
686 dgit push needs to canonicalise the suite name. Sometimes, dgit
687 lacks a way to ask the archive to do this without knowing the
688 name of an existing package. Without --new we can just use the
689 package we are trying to push. But with --new that will not work, so
692 or use the value of this option. This option is not needed with the
693 default mechanisms for accessing the archive.
696 Print a usage summary.
698 .BI --initiator-tempdir= directory
699 dgit rpush uses a temporary directory on the invoking (signing) host.
700 This option causes dgit to use
702 instead. Furthermore, the specified directory will be emptied,
703 removed and recreated before dgit starts, rather than removed
704 after dgit finishes. The directory specified must be an absolute
708 Do not delete the destination directory if clone fails.
709 .SH WORKFLOW - SIMPLE
710 It is always possible with dgit to clone or fetch a package, make
711 changes in git (using git-commit) on the suite branch
712 .RB ( "git checkout dgit/" \fIsuite\fR)
713 and then dgit push. You can use whatever gitish techniques you like
714 to construct the commits to push;
715 the only requirement is that what you push is a
716 descendant of the state of the archive, as provided by dgit in the
717 remote tracking branch
718 .BR remotes/dgit/dgit/ \fIsuite\fR.
720 If you are using dgit to do an NMU (in Debian),
721 and don't know about the
722 maintainers' preferred packaging workflows, you should make your
723 changes as a linear series of (logicially separated) commits on top of
724 what's already in the archive.
726 If you are lucky the other uploaders have also used dgit and
727 integrated the other relevant git history; if not you can fetch it
728 into your tree and cherry-pick etc. as you wish.
729 .SH WORKFLOW - INTEGRATING BETWEEN DGIT AND OTHER GIT HISTORY
730 If you are the maintainer of a package dealing with uploads made
731 without dgit, you will probably want to merge the synthetic commits
732 (made by dgit to represent the uploads) into your git history.
733 Normally you can just merge the dgit branch into your own master, or
734 indeed if you do your work on the dgit local suite branch
736 you can just use dgit pull.
738 However the first time dgit is used it will generate a new origin
739 commit from the archive which won't be linked into the rest of your
740 git history. You will need to merge this.
742 If last upload was in fact made with git, you should usually proceed
743 as follows: identify the commit which was actually used to build the
744 package. (Hopefully you have a tag for this.) Check out the dgit
746 .RB ( "git checkout dgit/" \fIsuite\fR)
747 and merge that other commit
748 .RB ( "git merge debian/" \fIversion\fR).
749 Hopefully this merge will be trivial because the two trees should
750 be very similar. The resulting branch head can be merged into your
752 .RB ( "git checkout master && git merge dgit/" \fIsuite\fR).
754 If last upload was not made with git, a different approach is required
755 to start using dgit. First, do
757 (or clone) to obtain a git history representation of what's in the
758 archive and record it in the
759 .BI remotes/dgit/dgit/ suite
760 tracking branch. Then somehow, using your other git history
761 plus appropriate diffs and cherry picks from the dgit remote tracking
762 branch, construct a git commit whose tree corresponds to the tree to use for the
765 between what's in the archive and what you intend to upload.
768 to actually upload the result.
770 If the commit-to-be-uploaded is not a descendant of the
771 dgit remote tracking branch, you will need to pass
775 dgit can be configured via the git config system.
776 You may set keys with git-config (either in system-global or per-tree
777 configuration), or provide
779 on the dgit command line.
781 Settings likely to be useful for an end user include:
783 .BR dgit-suite. \fIsuite\fR .distro " \fIdistro\fR"
784 Specifies the distro for a suite. dgit keys off the suite name (which
785 appears in changelogs etc.), and uses that to determine the distro
786 which is involved. The config used is thereafter that for the distro.
788 .BI dgit.default.distro " distro"
789 The default distro for an unknown suite.
793 .BR dgit-distro. \fIdistro\fR . *,
794 the default value used if there is no distro-specific setting.
796 .BR dgit-distro. \fIdistro\fR .clean-mode
797 One of the values for the command line --clean= option; used if
798 --clean is not specified.
800 .BR dgit-distro. \fIdistro\fR .quilt-mode
801 One of the values for the command line --quilt= option; used if
802 --quilt is not specified.
804 .BR dgit-distro. \fIdistro\fR .rm-old-changes
805 Boolean, used if neither \-\-rm-old-changes nor \-\-no-rm-old-changes
806 is specified. The default is not to remove.
808 .BR dgit-distro. \fIdistro\fR .readonly " " auto | a " | " true | t | y | 1 " | " false | f | n | 0
809 Whether you have push access to the distro.
810 For Debian, it is OK to use auto, which uses readonly mode if you are
811 not pushing right now;
812 but, setting this to false will avoid relying on the mirror of the dgit
813 git repository server.
815 .BI dgit-distro. distro .keyid
819 .BI dgit-distro. distro .mirror " url"
821 .BI dgit-distro. distro .username
822 Not relevant for Debian.
824 .BI dgit-distro. distro .upload-host
825 Might be useful if you have an intermediate queue server.
827 .BI dgit-distro. distro .user-name " " dgit-distro. distro .user-email
828 Values to configure for user.name and user.email in new git trees. If
829 not specified, the DEBFULLNAME and DEBEMAIL environment variables are
830 used, respectively. Only used if .setup-usermail is not disabled.
832 .BI dgit-distro. distro .setup-useremail
833 Whether to set user.name and user.email in new git trees.
834 True by default. Ignored for dgit setup-setup-useremail, which does it anyway.
836 .BI dgit-distro. distro .setup-mergechangelogs
837 Whether to setup a merge driver which uses dpkg-mergechangelogs for
838 debian/changelog. True by default. Ignored for dgit
839 setup-mergechangelogs, which does it anyway.
841 .BI dgit-distro. distro .cmd- cmd
842 Program to use instead of
845 .BR -- \fIcmd\fR = "... ."
847 .BI dgit-distro. distro .opts- cmd
848 Extra options to pass to
851 .BR -- \fIcmd\fR : "... ."
852 To pass several options, configure multiple values in git config
853 (with git config --add). The options for
854 .BI dgit.default.opts- cmd
855 .BI dgit-distro. distro /push.opts- cmd
856 and are all used, followed by options from dgit's command line.
857 .SH ACCESS CONFIGURATION
858 There are many other settings which specify how a particular distro's
859 services (archive and git) are provided. These should not normally be
860 adjusted, but are documented for the benefit of distros who wish to
863 .BR dgit-distro. \fIdistro\fR /push. *
864 If set, overrides corresponding non \fB/push\fR config when
869 .BI dgit-distro. distro .git-url
871 .BR dgit-distro. \fIdistro\fR .git-url [ -suffix ]
873 .BI dgit-distro. distro .git-proto
875 .BI dgit-distro. distro .git-path
877 .BR dgit-distro. \fIdistro\fR .git-check " " true | false | url | ssh-cmd
879 .BI dgit-distro. distro .git-check-suffix
881 .BR dgit-distro. \fIdistro\fR .diverts.divert " " new-distro | / \fIdistro-suffix\fR
883 .BI dgit-distro. distro .git-create " " ssh-cmd | true
885 .BR dgit-distro. \fIdistro\fR .archive-query " " ftpmasterapi: " | " madison: "\fIdistro\fR | " dummycat: "\fI/path\fR | " sshpsql: \fIuser\fR @ \fIhost\fR : \fIdbname\fR
887 .BR dgit-distro. \fIdistro\fR .archive-query- ( url | tls-key | curl-ca-args )
889 .BI dgit-distro. distro .madison-distro
891 .BI dgit-distro. distro .archive-query-default-component
893 .BI dgit-distro. distro .dgit-tag-format
895 .BI dgit-distro. distro .ssh
897 .BI dgit-distro. distro .sshpsql-dbname
899 .BR dgit-distro. \fIdistro\fR . ( git | sshpsql ) - ( user | host | user-force )
901 .BI dgit-distro. distro .backports-quirk
902 .SH ENVIRONMENT VARIABLES
904 .BR DGIT_SSH ", " GIT_SSH
905 specify an alternative default program (and perhaps arguments) to use
906 instead of ssh. DGIT_SSH is consulted first and may contain arguments;
907 if it contains any whitespace will be passed to the shell. GIT_SSH
908 specifies just the program; no arguments can be specified, so dgit
909 interprets it the same way as git does.
911 also the --ssh= and --ssh: options.
913 .BR DEBEMAIL ", " DEBFULLNAME
914 Default git user.email and user.name for new trees. See
915 .BR "dgit setup-new-tree" .
917 .BR gpg ", " dpkg- "..., " debsign ", " git ", " curl ", " dput ", " LWP::UserAgent
918 and other subprograms and modules used by dgit are affected by various
919 environment variables. Consult the documentaton for those programs
922 dgit's git representation of format `3.0 (quilt)' source packages does
923 not represent the patch stack as git commits. Currently the patch
924 series representation cannot round trip between git and the archive.
925 Ideally dgit would represent a quilty package with an origin commit of
926 some kind followed by the patch stack as a series of commits followed
927 by a pseudo-merge (to make the branch fast-forwarding). This would
928 also mean a new `dgit rebase-prep' command or some such to turn such a
929 fast-forwarding branch back into a rebasing patch stack, and a `force'
930 option to dgit push (perhaps enabled automatically by a note left by
931 rebase-prep) which will make the required pseudo-merge.
933 If the dgit push fails halfway through, it should be restartable and
934 idempotent. However this is not true for the git tag operation.
935 Also, it would be good to check that the proposed signing key is
936 available before starting work.
938 dgit's handling of .orig.tar.gz is not very sophisticated. Ideally
939 the .orig.tar.gz could be transported via the git repo as git tags.
940 Doing this is made more complicated by the possibility of a `3.0
941 (quilt)' package with multiple .orig tarballs.
943 dgit's build functions, and dgit push, should not make any changes to
944 your current HEAD. Sadly this is necessary for packages in the `3.0
945 (quilt)' source format. This is ultimately due to what I consider
946 design problems in quilt and dpkg-source.
948 There should be an option which arranges for the `3.0 (quilt)'
949 autocommit(s) to not appear on your HEAD, but instead only in the
950 remote tracking suite branch.
952 --dry-run does not always work properly, as not doing some of the git
953 fetches may result in subsequent actions being different. Doing a
954 non-dry-run dgit fetch first will help.
961 \fBgit-buildpackage\fP(1),
962 \fBdpkg-buildpackage\fP(1),
964 https://browse.dgit.debian.org/