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: doing a straightforward NMU
40 dgit-maint-native(7) for maintainers of Debian-native packages
41 dgit-maint-merge(7) for maintainers who want a pure git workflow
42 dgit-maint-gbp(7) for maintainers already 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 adjusts the .changes to include any .origs which the archive lacks
163 and exclude .origs which the archive has
164 (so -sa and -sd are not needed when building for dgit push),
165 makes a signed git tag, edits the .dsc to contain the dgit metadata
166 field, runs debsign to sign the upload (.dsc and .changes), pushes the
167 signed tag, and finally uses dput to upload the .changes to the
170 dgit push always uses the package, suite and version specified in the
171 debian/changelog and the .dsc, which must agree. If the command line
172 specifies a suite then that must match too.
174 If dgit push fails while uploading, it is fine to simply retry the
175 dput on the .changes file at your leisure.
177 \fBdgit rpush\fR \fIbuild-host\fR\fB:\fR\fIbuild-dir\fR [\fIpush args...\fR]
178 Pushes the contents of the specified directory on a remote machine.
179 This is like running dgit push on build-host with build-dir as the
180 current directory; however, signing operations are done on the
181 invoking host. This allows you to do a push when the system which has
182 the source code and the build outputs has no access to the key:
184 1. Clone on build host (dgit clone)
186 2. Edit code on build host (edit, git commit)
188 3. Build package on build host (dgit build)
190 4. Test package on build host or elsewhere (dpkg -i, test)
192 5. Upload by invoking dgit rpush on host with your GPG key.
194 However, the build-host must be able to ssh to the dgit repos. If
195 this is not already the case, you must organise it separately, for
196 example by the use of ssh agent forwarding.
198 The remaining arguments are treated just as dgit push would handle
201 build-host and build\-dir can be passed as separate
202 arguments; this is assumed to be the case if the first argument
203 contains no : (except perhaps one in [ ], to support IPv6 address
206 You will need similar enough versions of dgit on the build-host and
207 the invocation host. The build-host needs gnupg installed, with your
208 public key in its keyring (but not your private key, obviously).
210 .B dgit setup-new-tree
211 Configure the current working tree the way that dgit clone would have
212 set it up. Like running
213 .B dgit setup-useremail
215 .B setup-mergechangelogs
216 (but only does each thing if dgit is configured to do it automatically).
217 You can use these in any git repository, not just ones used with
218 the other dgit operations.
220 .B dgit setup-useremail
221 Set the working tree's user.name and user.email from the
222 distro-specific dgit configuration
223 .RB ( dgit-distro. \fIdistro\fR .user-name " and " .user-email ),
224 or DEBFULLNAME or DEBEMAIL.
226 .B dgit setup-mergechangelogs
227 Configures a git merge helper for the file
230 .BR dpkg-mergechangelogs .
233 `3.0 (quilt)' format source packages need changes representing not
234 only in-tree but also as patches in debian/patches. dgit quilt-fixup
235 checks whether this has been done; if not, dgit will make appropriate
236 patches in debian/patches and also commit the resulting changes to
239 This is normally done automatically by dgit build and dgit push.
241 dgit will try to turn each relevant commit in your git history into a
242 new quilt patch. dgit cannot convert nontrivial merges, or certain
243 other kinds of more exotic history. If dgit can't find a suitable
244 linearisation of your history, by default it will fail, but you can
245 ask it to generate a single squashed patch instead.
247 \fBdgit import-dsc\fR [\fIsub-options\fR] \fI../path/to/.dsc\fR [\fB+\fR|\fB..\fR]branch
248 Import a Debian-format source package,
249 specified by its .dsc,
251 the way dgit fetch would do.
253 This does about half the work of dgit fetch:
254 it will convert the .dsc into a new, orphan git branch.
255 Since dgit has no access to a corresponding source package archive
256 or knowledge of the history
257 it does not consider whether this version is newer
258 than any previous import
259 or corresponding git branches;
260 and it therefore does not
261 make a pseudomerge to bind the import
262 into any existing git history.
264 There is only only sub-option:
266 .B --require-valid-signature
267 causes dgit to insist that the signature on the .dsc is valid
268 (using the same criteria as dpkg-source -x).
269 Otherwise, dgit tries to verify the signature but
270 the outcome is reported only as messages to stderr.
276 then if it already exists, it will be simply ovewritten,
277 no matter its existing contents.
282 then if it already exists
283 and dgit actually imports the dsc
284 (rather than simply reading the git commit out of the Dgit field),
285 dgit will make a pseudomerge
286 so that the result is necessarily fast forward
287 from the existing branch.
288 Otherwise, if branch already exists,
289 dgit will stop with an error message.
293 does not start with refs/, refs/heads/ is prepended.
294 The specified branch is unconditionally updated.
296 If the specified .dsc contains a Dgit field,
297 dgit will simply make a branch of that commit.
298 If you cannot manage to find that commit anywhere,
299 consider --force-import-dsc-with-dgit-field.
302 Prints version information and exits.
304 .BI "dgit clone-dgit-repos-server" " destdir"
305 Tries to fetch a copy of the source code for the dgit-repos-server,
306 as actually being used on the dgit git server, as a git tree.
309 .BR --dry-run " | " -n
310 Go through the motions, fetching all information needed, but do not
311 actually update the output(s). For push, dgit does
312 the required checks and leaves the new .dsc in a temporary file,
313 but does not sign, tag, push or upload.
315 .BR --damp-run " | " -L
316 Go through many more of the motions: do everything that doesn't
317 involve either signing things, or making changes on the public
323 for signing the tag and the upload. The default comes from the
326 config setting (see CONFIGURATION, below), or failing that, the
327 uploader trailer line in debian/changelog.
330 does not sign tags or uploads (meaningful only with push).
334 Specifies that we should process source package
336 rather than looking in debian/control or debian/changelog.
337 Valid with dgit fetch and dgit pull, only.
339 .BR --clean=git " | " -wg
342 to clean the working tree,
343 rather than running the package's rules clean target.
345 This will delete all files which are not tracked by git.
346 (Including any files you forgot to git add.)
349 options other than dpkg-source
350 are useful when the package's clean target is troublesome, or
351 to avoid needing the build-dependencies.
353 .BR --clean=git-ff " | " -wgf
355 .BR "git clean -xdff"
356 to clean the working tree.
359 but it also removes any subdirectories containing different git
360 trees (which only unusual packages are likely to create).
362 .BR --clean=check " | " -wc
363 Merely check that the tree is clean (does not contain uncommitted
365 Avoids running rules clean,
366 and can avoid needing the build-dependencies.
368 .BR --clean=none " | " -wn
369 Do not clean the tree, nor check that it is clean.
370 Avoids running rules clean,
371 and can avoid needing the build-dependencies.
373 files which are not in git, or if the build creates such files, a
374 subsequent dgit push will fail.
376 .BR --clean=dpkg-source " | " -wd
377 Use dpkg-buildpackage to do the clean, so that the source package
378 is cleaned by dpkg-source running the package's clean target.
380 Requires the package's build dependencies.
382 .BR --clean=dpkg-source-d " | " -wdd
384 .B dpkg-buildpackage -d
386 so that the source package
387 is cleaned by dpkg-source running the package's clean target.
388 The build-dependencies are not checked (due to
390 which violates policy, but may work in practice.
393 The package is or may be new in this suite. Without this, dgit will
394 refuse to push. It may (for Debian, will) be unable to access the git
395 history for any packages which have been newly pushed and have not yet
399 Do not complain if the working tree does not match your git HEAD.
400 This can be useful with build, if you plan to commit later. (dgit
401 push will still ensure that the .dsc you upload and the git tree
402 you push are identical, so this option won't make broken pushes.)
404 .BR --overwrite =\fIprevious-version\fR
405 Declare that even though your git branch is not a descendant
406 of the version in the archive
407 according to the revision history,
408 it really does contain
409 all the (wanted) changes from that version.
411 This option is useful if you are the maintainer, and you have
412 incorporated NMU changes into your own git workflow in a way that
413 doesn't make your branch a fast forward from the NMU.
416 ought to be the version currently in the archive. If
419 specified, dgit will check that the version in the archive is
420 mentioned in your debian/changelog.
421 (This will avoid losing
422 changes unless someone committed to git a finalised changelog
423 entry, and then made later changes to that version.)
425 dgit push --overwrite
427 pseudo-merge (that is, something that looks like the result
428 of git merge -s ours) to stitch the archive's version into your own
429 git history, so that your push is a fast forward from the archive.
432 .BR gbp ", " dpm " or " unpatched ,
433 implying a split between the dgit view and the
434 maintainer view, the pseudo-merge will appear only in the dgit view.)
436 .BR --delayed =\fIdays\fR
437 Upload to a DELAYED queue.
440 If the maintainer responds by cancelling
441 your upload from the queue,
442 and does not make an upload of their own,
443 this will not rewind the git branch on the dgit git server.
444 Other dgit users will then see your push
445 (with a warning message from dgit)
446 even though the maintainer wanted to abolish it.
447 Such users might unwittingly reintroduce your changes.
449 If this situation arises,
450 someone should make a suitable dgit push
451 to update the contents of dgit-repos
452 to a version without the controversial changes.
454 .BR --dgit-view-save= \fIbranch\fR|\fIref\fR
455 Specifies that when a split view quilt mode is in operation,
457 (or looks up in its cache)
458 a dgit view corresponding to your HEAD,
459 the dgit view will be left in
461 The specified ref is unconditionally overwritten,
462 so don't specify a branch you want to keep.
464 This option is effective only with the following operations:
465 quilt-fixup; push; all builds.
466 And it is only effective with
471 If ref does not start with refs/
472 it is taken to to be a branch -
473 i.e. refs/heads/ is prepended.
475 .BI --deliberately- something
476 Declare that you are deliberately doing
478 This can be used to override safety catches, including safety catches
479 which relate to distro-specific policies.
480 The use of --deliberately is declared and published in the signed tags
481 generated for you by dgit,
482 so that the archive software can give effect to your intent,
484 for the benefit humans looking at the history.
487 understood in the context of Debian are discussed below:
489 .BR --deliberately-not-fast-forward
490 Declare that you are deliberately rewinding history. When pushing to
491 Debian, use this when you are making a renewed upload of an entirely
492 new source package whose previous version was not accepted for release
493 from NEW because of problems with copyright or redistributibility.
495 .BR --deliberately-include-questionable-history
496 Declare that you are deliberately including, in the git history of
497 your current push, history which contains a previously-submitted
498 version of this package which was not approved (or has not yet been
499 approved) by the ftpmasters. When pushing to Debian, only use this
500 option after verifying that: none of the rejected-from-NEW (or
501 never-accepted) versions in the git history of your current push, were
502 rejected by ftpmaster for copyright or redistributability reasons.
504 .BR --deliberately-fresh-repo
505 Declare that you are deliberately rewinding history and want to
506 throw away the existing repo. Not relevant when pushing to Debian,
507 as the Debian server will do this automatically when necessary.
510 When fixing up source format `3.0 (quilt)' metadata, insist on
511 generating a linear patch stack: one new patch for each relevant
513 If such a stack cannot be generated, fail.
514 This is the default for Debian.
516 HEAD should be a series of plain commits
517 (not touching debian/patches/),
519 with as ancestor a patches-applied branch.
522 When fixing up source format `3.0 (quilt)' metadata, prefer to
523 generate a linear patch stack
524 (as with --quilt=auto)
525 but if that doesn't seem possible,
526 try to generate a single squashed patch for all the changes made in git
527 (as with --quilt=smash).
528 This is not a good idea for an NMU in Debian.
531 When fixing up source format `3.0 (quilt)' metadata,
532 generate a single additional patch for all the changes made in git.
533 This is not a good idea for an NMU in Debian.
535 (If HEAD has any in-tree patches already, they must apply cleanly.
536 This will be the case for any trees produced by dgit fetch or clone;
537 if you do not change the upstream version
538 nor make changes in debian/patches,
539 it will remain true.)
542 Check whether source format `3.0 (quilt)' metadata would need fixing
543 up, but, if it does, fail. You must then fix the metadata yourself
544 somehow before pushing. (NB that dpkg-source --commit will not work
545 because the dgit git tree does not have a
549 .BR --quilt=nocheck " | " --no-quilt-fixup
550 Do not check whether up source format `3.0 (quilt)' metadata needs
551 fixing up. If you use this option and the metadata did in fact need
552 fixing up, dgit push will fail.
554 .BR -- [ quilt= ] gbp " | " -- [ quilt= ] dpm " | " --quilt=unapplied
555 Tell dgit that you are using a nearly-dgit-compatible git branch,
557 .BR "maintainer view" ,
559 do not want your branch changed by dgit.
564 is for use with git-buildpackage.
565 Your HEAD is expected to be
566 a patches-unapplied git branch, except that it might contain changes
567 to upstream .gitignore files. This is the default for dgit gbp-build.
572 is for use with git-dpm.
573 Your HEAD is expected to be
574 a patches-applied git branch,
575 except that it might contain changes to upstream .gitignore files.
578 specifies that your HEAD is a patches-unapplied git branch (and
579 that any changes to upstream .gitignore files are represented as
580 patches in debian/patches).
582 With --quilt=gbp|dpm|unapplied,
583 dgit push (or precursors like quilt-fixup and build) will automatically
584 generate a conversion of your git branch into the right form.
585 dgit push will push the
586 dgit-compatible form (the
588 to the dgit git server.
589 The dgit view will be visible to you
590 in the dgit remote tracking branches, but your own branch will
592 dgit push will create a tag
594 for the maintainer view, and the dgit tag
595 .BI archive/debian/ version
597 dgit quilt-fixup will merely do some checks,
598 and cache the maintainer view.
600 .B If you have a branch like this it is essential to specify the appropriate --quilt= option!
601 This is because it is not always possible to tell: a patches-unapplied
602 git branch of a package with one patch, for example, looks very like
603 a patches-applied branch where the user has used git revert to
604 undo the patch, expecting to actually revert it.
605 However, if you fail to specify the right \-\-quilt option,
606 and you aren't too lucky, dgit will notice the problem and stop,
609 .BR -d "\fIdistro\fR | " --distro= \fIdistro\fR
610 Specifies that the suite to be operated on is part of distro
612 This overrides the default value found from the git config option
613 .BR dgit-suite. \fIsuite\fR .distro .
614 The only effect is that other configuration variables (used
615 for accessing the archive and dgit-repos) used are
616 .BR dgit-distro. \fIdistro\fR .* .
618 If your suite is part of a distro that dgit already knows about, you
619 can use this option to make dgit work even if your dgit doesn't know
620 about the suite. For example, specifying
622 will work when the suite is an unknown suite in the Debian archive.
624 To define a new distro it is necessary to define methods and URLs
625 for fetching (and, for dgit push, altering) a variety of information both
626 in the archive and in dgit-repos.
627 How to set this up is not yet documented.
630 Specifies the .changes file which is to be uploaded. By default
631 dgit push looks for single .changes file in the parent directory whose
632 filename suggests it is for the right package and version.
636 pathname contains slashes, the directory part is also used as
638 .BR --build-products-dir ;
639 otherwise, the changes file is expected in that directory (by
644 When doing a build, delete any changes files matching
645 .IB package _ version _*.changes
646 before starting. This ensures that
647 dgit push (and dgit sbuild) will be able to unambigously
648 identify the relevant changes files from the most recent build, even
649 if there have been previous builds with different tools or options.
650 The default is not to remove, but
651 .B \-\-no-rm-old-changes
652 can be used to override a previous \-\-rm-old-changes
653 or the .rm-old-changes configuration setting.
655 .BI --build-products-dir= directory
656 Specifies where to find the built files to be uploaded.
657 By default, dgit looks in the parent directory
661 Do not delete the destination directory if clone fails.
664 Prints debugging information to stderr. Repeating the option produces
665 more output (currently, up to -DDDD is meaningfully different).
668 Specifies a git configuration option, to be used for this run.
669 dgit itself is also controlled by git configuration options.
671 .RI \fB-v\fR version "|\fB_\fR | " \fB--since-version=\fR version |\fB_\fR
674 option to pass to dpkg-genchanges, during builds. Changes (from
675 debian/changelog) since this version will be included in the built
676 changes file, and hence in the upload. If this option is not
677 specified, dgit will query the archive and use the latest version
678 uploaded to the intended suite.
682 inhibits this, so that no -v option will be passed to dpkg-genchanges
683 (and as a result, only the last stanza from debian/changelog will
684 be used for the build and upload).
686 .RI \fB-m\fR maintaineraddress
687 Passed to dpkg-genchanges (eventually).
689 .RI \fB--ch:\fR option
690 Specifies a single additional option to pass, eventually, to
693 Options which are safe to pass include
697 although these should never be necessary with Debian since dgit
698 automatically calculates whether .origs need to be uploaded.)
700 For other options the caveat below applies.
702 .RI \fB--curl:\fR option " | \fB--dput:\fR" option " |..."
703 Specifies a single additional option to pass to
708 .BR dpkg-buildpackage ,
709 .BR dpkg-genchanges ,
717 Can be repeated as necessary.
719 Use of this ability should not normally be necessary.
720 It is provided for working around bugs,
721 or other unusual situations.
722 If you use these options,
723 you may violate dgit's assumptions
724 about the behaviour of its subprograms
727 For dpkg-buildpackage, dpkg-genchanges, mergechanges and sbuild,
728 the option applies only when the program is invoked directly by dgit.
729 Usually, for passing options to dpkg-genchanges, you should use
730 .BR --ch: \fIoption\fR.
732 Specifying --git is not effective for some lower-level read-only git
733 operations performed by dgit, and also not when git is invoked by
734 another program run by dgit.
736 See notes below regarding ssh and dgit.
738 NB that --gpg:option is not supported (because debsign does not
744 distro config setting.
746 .RI \fB--curl=\fR program " | \fB--dput=\fR" program " |..."
747 Specifies alternative programs to use instead of
752 .BR dpkg-buildpackage ,
753 .BR dpkg-genchanges ,
765 .BR dpkg-buildpackage ,
766 .BR dpkg-genchanges ,
770 this applies only when the program is invoked directly by dgit.
774 specifies the command to run on the remote host when dgit
775 rpush needs to invoke a remote copy of itself. (dgit also reinvokes
776 itself as the EDITOR for dpkg-source --commit; this is done using
777 argv[0], and is not affected by --dgit=).
781 is used instead of gbp build or git-buildpackage. (The default is
782 the latter unless the former exists on PATH.)
785 is used instead of gbp pq.
787 unusually, the specified value is split on whitespace
788 to produce a command and possibly some options and/or arguments.
792 the default value is taken from the
796 environment variables, if set (see below). And, for ssh, when accessing the
797 archive and dgit-repos, this command line setting is overridden by the
799 .BI dgit-distro. distro .ssh
802 (which can in turn be overridden with -c). Also, when dgit is using
803 git to access dgit-repos, only git's idea of what ssh to use (eg,
807 .BI --existing-package= package
808 dgit push needs to canonicalise the suite name. Sometimes, dgit
809 lacks a way to ask the archive to do this without knowing the
810 name of an existing package. Without --new we can just use the
811 package we are trying to push. But with --new that will not work, so
814 or use the value of this option. This option is not needed with the
815 default mechanisms for accessing the archive.
818 Print a usage summary.
820 .BI --initiator-tempdir= directory
821 dgit rpush uses a temporary directory on the invoking (signing) host.
822 This option causes dgit to use
824 instead. Furthermore, the specified directory will be emptied,
825 removed and recreated before dgit starts, rather than removed
826 after dgit finishes. The directory specified must be an absolute
829 .BI --force- something
830 Instructs dgit to try to proceed despite detecting
831 what it thinks is going to be a fatal problem.
832 .B This is probably not going to work.
833 These options are provided as an escape hatch,
834 in case dgit is confused.
835 (They might also be useful for testing error cases.)
837 .B --import-dsc-with-dgit-field
838 Tell dgit import-dsc to treat a .dsc with a Dgit field
840 The result is a fresh import,
841 discarding the git history
842 that the person who pushed that .dsc was working with.
844 .B --force-unrepresentable
846 dgit thinks that your git tree contains changes
847 (relative to your .orig tarballs)
848 which dpkg-source is not able to represent.
849 Your build or push will probably fail later.
851 .B --force-changes-origs-exactly
852 Use the set of .origs specified in your .changes, exactly,
853 without regard to what is in the archive already.
854 The archive may well reject your upload.
856 .B --force-unsupported-source-format
857 Carry on despite dgit not understanding your source package format.
858 dgit will probably mishandle it.
860 .B --force-dsc-changes-mismatch
861 Do not check whether .dsc and .changes match.
862 The archive will probably reject your upload.
864 .BR --force-import-gitapply-absurd " | " --force-import-gitapply-no-absurd
865 Force on or off the use of the absurd git-apply emulation
866 when running gbp pq import
867 when importing a package from a .dsc.
868 See Debian bug #841867.
870 dgit can be configured via the git config system.
871 You may set keys with git-config (either in system-global or per-tree
872 configuration), or provide
874 on the dgit command line.
876 Settings likely to be useful for an end user include:
878 .BR dgit-suite. \fIsuite\fR .distro " \fIdistro\fR"
879 Specifies the distro for a suite. dgit keys off the suite name (which
880 appears in changelogs etc.), and uses that to determine the distro
881 which is involved. The config used is thereafter that for the distro.
883 .BI dgit.default.distro " distro"
884 The default distro for an unknown suite.
888 .BR dgit-distro. \fIdistro\fR . *,
889 the default value used if there is no distro-specific setting.
891 .BR dgit-distro. \fIdistro\fR .clean-mode
892 One of the values for the command line --clean= option; used if
893 --clean is not specified.
895 .BR dgit-distro. \fIdistro\fR .quilt-mode
896 One of the values for the command line --quilt= option; used if
897 --quilt is not specified.
899 .BR dgit-distro. \fIdistro\fR .rm-old-changes
900 Boolean, used if neither \-\-rm-old-changes nor \-\-no-rm-old-changes
901 is specified. The default is not to remove.
903 .BR dgit-distro. \fIdistro\fR .readonly " " auto | a " | " true | t | y | 1 " | " false | f | n | 0
904 Whether you have push access to the distro.
905 For Debian, it is OK to use auto, which uses readonly mode if you are
906 not pushing right now;
907 but, setting this to false will avoid relying on the mirror of the dgit
908 git repository server.
910 .BI dgit-distro. distro .keyid
914 .BI dgit-distro. distro .mirror " url"
916 .BI dgit-distro. distro .username
917 Not relevant for Debian.
919 .BI dgit-distro. distro .upload-host
920 Might be useful if you have an intermediate queue server.
922 .BI dgit-distro. distro .user-name " " dgit-distro. distro .user-email
923 Values to configure for user.name and user.email in new git trees. If
924 not specified, the DEBFULLNAME and DEBEMAIL environment variables are
925 used, respectively. Only used if .setup-usermail is not disabled.
927 .BI dgit-distro. distro .setup-useremail
928 Whether to set user.name and user.email in new git trees.
929 True by default. Ignored for dgit setup-setup-useremail, which does it anyway.
931 .BI dgit-distro. distro .setup-mergechangelogs
932 Whether to setup a merge driver which uses dpkg-mergechangelogs for
933 debian/changelog. True by default. Ignored for dgit
934 setup-mergechangelogs, which does it anyway.
936 .BI dgit-distro. distro .cmd- cmd
937 Program to use instead of
940 .BR -- \fIcmd\fR = "... ."
942 .BI dgit-distro. distro .opts- cmd
943 Extra options to pass to
946 .BR -- \fIcmd\fR : "... ."
947 To pass several options, configure multiple values in git config
948 (with git config --add). The options for
949 .BI dgit.default.opts- cmd
950 .BI dgit-distro. distro /push.opts- cmd
951 and are all used, followed by options from dgit's command line.
952 .SH ACCESS CONFIGURATION
953 There are many other settings which specify how a particular distro's
954 services (archive and git) are provided. These should not normally be
955 adjusted, but are documented for the benefit of distros who wish to
958 .BR dgit-distro. \fIdistro\fR /push. *
959 If set, overrides corresponding non \fB/push\fR config when
964 .BI dgit-distro. distro .git-url
966 .BR dgit-distro. \fIdistro\fR .git-url [ -suffix ]
968 .BI dgit-distro. distro .git-proto
970 .BI dgit-distro. distro .git-path
972 .BR dgit-distro. \fIdistro\fR .git-check " " true | false | url | ssh-cmd
974 .BI dgit-distro. distro .git-check-suffix
976 .BR dgit-distro. \fIdistro\fR .diverts.divert " " new-distro | / \fIdistro-suffix\fR
978 .BI dgit-distro. distro .git-create " " ssh-cmd | true
980 .BR dgit-distro. \fIdistro\fR .archive-query " " ftpmasterapi: " | " madison: "\fIdistro\fR | " dummycat: "\fI/path\fR | " sshpsql: \fIuser\fR @ \fIhost\fR : \fIdbname\fR
982 .BR dgit-distro. \fIdistro\fR .archive-query- ( url | tls-key | curl-ca-args )
984 .BI dgit-distro. distro .madison-distro
986 .BI dgit-distro. distro .archive-query-default-component
988 .BI dgit-distro. distro .dgit-tag-format
990 .BI dgit-distro. distro .ssh
992 .BI dgit-distro. distro .sshpsql-dbname
994 .BR dgit-distro. \fIdistro\fR . ( git | sshpsql ) - ( user | host | user-force )
996 .BI dgit-distro. distro .backports-quirk
997 .SH ENVIRONMENT VARIABLES
999 .BR DGIT_SSH ", " GIT_SSH
1000 specify an alternative default program (and perhaps arguments) to use
1001 instead of ssh. DGIT_SSH is consulted first and may contain arguments;
1002 if it contains any whitespace will be passed to the shell. GIT_SSH
1003 specifies just the program; no arguments can be specified, so dgit
1004 interprets it the same way as git does.
1006 also the --ssh= and --ssh: options.
1008 .BR DEBEMAIL ", " DEBFULLNAME
1009 Default git user.email and user.name for new trees. See
1010 .BR "dgit setup-new-tree" .
1012 .BR gpg ", " dpkg- "..., " debsign ", " git ", " curl ", " dput ", " LWP::UserAgent
1013 and other subprograms and modules used by dgit are affected by various
1014 environment variables. Consult the documentaton for those programs
1018 a `dgit rebase-prep' command or some such to turn a
1019 fast-forwarding branch containing pseudo-merges
1020 back into a rebasing patch stack.
1021 It might have to leave a note
1022 for a future dgit push.
1024 If the dgit push fails halfway through,
1025 it is not necessarily restartable and
1027 It would be good to check that the proposed signing key is
1028 available before starting work.
1030 dgit's build functions, and dgit push, may make changes to
1031 your current HEAD. Sadly this is necessary for packages in the `3.0
1032 (quilt)' source format. This is ultimately due to what I consider
1033 design problems in quilt and dpkg-source.
1035 --dry-run does not always work properly, as not doing some of the git
1036 fetches may result in subsequent actions being different. Doing a
1037 non-dry-run dgit fetch first will help.
1038 --damp-run is likely to work much better.
1045 \fBgit-config\fP(1),
1046 \fBgit-buildpackage\fP(1),
1047 \fBdpkg-buildpackage\fP(1),
1049 https://browse.dgit.debian.org/