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
130 passed on to sbuild. Changes files matching
131 .IB package _ version _*.changes
132 in the parent directory will be removed; the output is left in
133 .IR package \fB_\fR version \fB_multi.changes\fR.
135 Tagging, signing and actually uploading should be left to dgit push.
137 \fBdgit git-build\fR ...
140 with some suitable options. Options and arguments after git-build
141 will be passed on to git-buildpackage.
143 Tagging, signing and actually uploading should be left to dgit push.
145 \fBdgit push\fR [\fIsuite\fP]
146 Does an `upload', pushing the current HEAD to the archive (as a source
147 package) and to dgit-repos (as git commits). The package must already
148 have been built ready for upload, with the .dsc and .changes
149 left in the parent directory. It is normally best to do the build
150 with dgit too (eg with dgit sbuild): some existing build tools pass
151 unhelpful options to dpkg-source et al by default, which can result in
152 the built source package not being identical to the git tree.
154 In more detail: dgit push checks that the current HEAD corresponds to
155 the .dsc. It then pushes the HEAD to the suite's dgit-repos branch,
156 makes a signed git tag, edits the .dsc to contain the dgit metadata
157 field, runs debsign to sign the upload (.dsc and .changes), pushes the
158 signed tag, and finally uses dput to upload the .changes to the
161 dgit push always uses the package, suite and version specified in the
162 debian/changelog and the .dsc, which must agree. If the command line
163 specifies a suite then that must match too.
165 If dgit push fails while uploading, it is fine to simply retry the
166 dput on the .changes file at your leisure.
168 \fBdgit rpush\fR \fIbuild-host\fR\fB:\fR\fIbuild-dir\fR [\fIpush args...\fR]
169 Pushes the contents of the specified directory on a remote machine.
170 This is like running dgit push on build-host with build-dir as the
171 current directory; however, signing operations are done on the
172 invoking host. This allows you to do a push when the system which has
173 the source code and the build outputs has no access to the key:
175 1. Clone on build host (dgit clone)
177 2. Edit code on build host (edit, git commit)
179 3. Build package on build host (dgit build)
181 4. Test package on build host or elsewhere (dpkg -i, test)
183 5. Upload by invoking dgit rpush on host with your GPG key.
185 However, the build-host must be able to ssh to the dgit repos. If
186 this is not already the case, you must organise it separately, for
187 example by the use of ssh agent forwarding.
189 The remaining arguments are treated just as dgit push would handle
192 build-host and build\-dir can be passed as separate
193 arguments; this is assumed to be the case if the first argument
194 contains no : (except perhaps one in [ ], to support IPv6 address
197 You will need similar enough versions of dgit on the build-host and
198 the invocation host. The build-host needs gnupg installed, with your
199 public key in its keyring (but not your private key, obviously).
201 .B dgit setup-new-tree
202 Configure the current working tree the way that dgit clone would have
203 set it up. Like running
204 .B dgit setup-useremail
206 .B setup-mergechangelogs
207 (but only does each thing if dgit is configured to do it automatically).
208 You can use these in any git repository, not just ones used with
209 the other dgit operations.
211 .B dgit setup-useremail
212 Set the working tree's user.name and user.email from the
213 distro-specific dgit configuration
214 .RB ( dgit-distro. \fIdistro\fR .user-name " and " .user-email ),
215 or DEBFULLNAME or DEBEMAIL.
217 .B dgit setup-mergechangelogs
218 Configures a git merge helper for the file
221 .BR dpkg-mergechangelogs .
224 `3.0 (quilt)' format source packages need changes representing not
225 only in-tree but also as patches in debian/patches. dgit quilt-fixup
226 checks whether this has been done; if not, dgit will make appropriate
227 patches in debian/patches and also commit the resulting changes to
230 This is normally done automatically by dgit build and dgit push.
232 dgit will try to turn each relevant commit in your git history into a
233 new quilt patch. dgit cannot convert nontrivial merges, or certain
234 other kinds of more exotic history. If dgit can't find a suitable
235 linearisation of your history, by default it will fail, but you can
236 ask it to generate a single squashed patch instead.
239 Prints version information and exits.
241 .BI "dgit clone-dgit-repos-server" " destdir"
242 Tries to fetch a copy of the source code for the dgit-repos-server,
243 as actually being used on the dgit git server, as a git tree.
246 .BR --dry-run " | " -n
247 Go through the motions, fetching all information needed, but do not
248 actually update the output(s). For push, dgit does
249 the required checks and leaves the new .dsc in a temporary file,
250 but does not sign, tag, push or upload.
252 .BR --damp-run " | " -L
253 Go through many more of the motions: do everything that doesn't
254 involve either signing things, or making changes on the public
260 for signing the tag and the upload. The default comes from the
263 config setting (see CONFIGURATION, below), or failing that, the
264 uploader trailer line in debian/changelog.
267 does not sign tags or uploads (meaningful only with push).
271 Specifies that we should process source package
273 rather than looking in debian/control or debian/changelog.
274 Valid with dgit fetch and dgit pull, only.
276 .BR --clean=git " | " -wg
277 The source tree should be cleaned, before building a source package
278 with one of the build options, using
279 .BR "git clean -xdf" .
280 This will delete all files which are not tracked by git. Also, -wg
283 to dpkg-buildpackage, which prevents the package's own clean target
286 --clean=git is useful when the package's clean target is troublesome;
287 the downside is simply that git clean may delete files you forgot to
288 git add. --clean=git can also avoid needing the build-dependencies.
290 .BR --clean=git-ff " | " -wgf
291 The source tree should be cleaned, before building a source package
292 with one of the build options, using
293 .BR "git clean -xdff" .
296 but it also removes any subdirectories containing different git
297 trees (which only unusual packages are likely to create).
299 .BR --clean=check " | " -wc
300 Merely check that the tree is clean (does not contain uncommitted
301 files), before building a source package.
303 .BR --clean=none " | " -wn
304 Do not clean the tree before building a source package. If there are
305 files which are not in git, or if the build creates such files, a
306 subsequent dgit push will fail.
308 .BR --clean=dpkg-source " | " -wd
309 Use dpkg-buildpackage to do the clean, so that the source package
310 is cleaned by dpkg-source running the package's clean target.
311 This is the default. It requires the package's build dependencies.
313 .BR --clean=dpkg-source-d " | " -wdd
315 .B dpkg-buildpackage -d
316 to do the clean, so that the source package
317 is cleaned by dpkg-source running the package's clean target.
318 The build-dependencies are not checked (due to
320 which violates policy, but may work in practice.
323 The package is or may be new in this suite. Without this, dgit will
324 refuse to push. It may (for Debian, will) be unable to access the git
325 history for any packages which have been newly pushed and have not yet
329 Do not complain if the working tree does not match your git HEAD.
330 This can be useful with build, if you plan to commit later. (dgit
331 push will still ensure that the .dsc you upload and the git tree
332 you push are identical, so this option won't make broken pushes.)
334 .BI --deliberately- something
335 Declare that you are deliberately doing
337 This can be used to override safety catches, including safety catches
338 which relate to distro-specific policies. The meanings of
340 understood in the context of Debian are discussed below:
342 .BR --deliberately-not-fast-forward
343 Declare that you are deliberately rewinding history. When pushing to
344 Debian, use this when you are making a renewed upload of an entirely
345 new source package whose previous version was not accepted for release
346 from NEW because of problems with copyright or redistributibility.
348 .BR --deliberately-include-questionable-history
349 Declare that you are deliberately including, in the git history of
350 your current push, history which contains a previously-submitted
351 version of this package which was not approved (or has not yet been
352 approved) by the ftpmasters. When pushing to Debian, only use this
353 option after verifying that: none of the rejected-from-NEW (or
354 never-accepted) versions in the git history of your current push, were
355 rejected by ftpmaster for copyright or redistributability reasons.
357 .BR --deliberately-fresh-repo
358 Declare that you are deliberately rewinding history and want to
359 throw away the existing repo. Not relevant when pushing to Debian,
360 as the Debian server will do this automatically when necessary.
363 When fixing up source format `3.0 (quilt)' metadata, insist on
364 generating a linear patch stack. If such a stack cannot be generated,
365 fail. This is the default for Debian.
368 When fixing up source format `3.0 (quilt)' metadata, prefer to
369 generate a linear patch stack, but if that doesn't seem possible,
370 generate a single squashed patch for all the changes made in git.
371 This is not a good idea for an NMU in Debian.
374 When fixing up source format `3.0 (quilt)' metadata,
375 generate a single squashed patch for all the changes made in git.
376 This is not a good idea for an NMU in Debian.
379 Check whether source format `3.0 (quilt)' metadata would need fixing
380 up, but, if it does, fail. You must then fix the metadata yourself
381 somehow before pushing. (NB that dpkg-source --commit will not work
382 because the dgit git tree does not have a
386 .BR --quilt=nocheck " | " --no-quilt-fixup
387 Do not check whether up source format `3.0 (quilt)' metadata needs
388 fixing up. If you use this option and the metadata did in fact need
389 fixing up, dgit push will fail.
392 Prints debugging information to stderr. Repeating the option produces
393 more output (currently, up to -DDDD is meaningfully different).
396 Specifies a git configuration option, to be used for this run.
397 dgit itself is also controlled by git configuration options.
399 .RI \fB-v\fR version "|\fB_\fR | " \fB--since-version=\fR version |\fB_\fR
402 option to pass to dpkg-genchanges, during builds. Changes (from
403 debian/changelog) since this version will be included in the built
404 changes file, and hence in the upload. If this option is not
405 specified, dgit will query the archive and use the latest version
406 uploaded to the intended suite.
410 inhibits this, so that no -v option will be passed to dpkg-genchanges
411 (and as a result, only the last stanza from debian/changelog will
412 be used for the build and upload).
414 .RI \fB-m\fR maintaineraddress
415 Passed to dpkg-genchanges (eventually).
417 .RI \fB--ch:\fR option
418 Specifies a single additional option to pass, eventually, to
421 .RI \fB--curl=\fR program " | \fB--dput=\fR" program " |..."
422 Specifies alternative programs to use instead of
427 .BR dpkg-buildpackage ,
428 .BR dpkg-genchanges ,
436 For dpkg-buildpackage, dpkg-genchanges, mergechanges and sbuild,
437 this applies only when the program is invoked directly by dgit.
439 For dgit, specifies the command to run on the remote host when dgit
440 rpush needs to invoke a remote copy of itself. (dgit also reinvokes
441 itself as the EDITOR for dpkg-source --commit; this is done using
442 argv[0], and is not affected by --dgit=).
444 For ssh, the default value is taken from the
448 environment variables, if set (see below). And, for ssh, when accessing the
449 archive and dgit-repos, this command line setting is overridden by the
451 .BI dgit-distro. distro .ssh
454 (which can in turn be overridden with -c). Also, when dgit is using
455 git to access dgit-repos, only git's idea of what ssh to use (eg,
459 .RI \fB--curl:\fR option " | \fB--dput:\fR" option " |..."
460 Specifies a single additional option to pass to
465 .BR dpkg-buildpackage ,
466 .BR dpkg-genchanges ,
472 Can be repeated as necessary.
474 For dpkg-buildpackage, dpkg-genchanges, mergechanges and sbuild,
475 this applies only when the program is invoked directly by dgit.
476 Usually, for passing options to dpkg-genchanges, you should use
477 .BR --ch: \fIoption\fR.
479 See notes above regarding ssh and dgit.
481 NB that --gpg:option is not supported (because debsign does not
487 distro config setting.
489 .BR -d "\fIdistro\fR | " --distro= \fIdistro\fR
490 Specifies that the suite to be operated on is part of distro
492 This overrides the default value found from the git config option
493 .BR dgit-suite. \fIsuite\fR .distro .
494 The only effect is that other configuration variables (used
495 for accessing the archive and dgit-repos) used are
496 .BR dgit-distro. \fIdistro\fR .* .
498 If your suite is part of a distro that dgit already knows about, you
499 can use this option to make dgit work even if your dgit doesn't know
500 about the suite. For example, specifying
502 will work when the suite is an unknown suite in the Debian archive.
504 To define a new distro it is necessary to define methods and URLs
505 for fetching (and, for dgit push, altering) a variety of information both
506 in the archive and in dgit-repos.
507 How to set this up is not yet documented.
510 Specifies the .changes file which is to be uploaded. By default
511 dgit push looks for single .changes file in the parent directory whose
512 filename suggests it is for the right package and version - or,
513 if there is a _multi.changes file, dgit uses that.
517 pathname contains slashes, the directory part is also used as
519 .BR --build-products-dir ;
520 otherwise, the changes file is expected in that directory (by
524 .BI --build-products-dir= directory
525 Specifies where to find the built files to be uploaded.
526 By default, dgit looks in the parent directory
529 .BI --existing-package= package
530 dgit push needs to canonicalise the suite name. Sometimes, dgit
531 lacks a way to ask the archive to do this without knowing the
532 name of an existing package. Without --new we can just use the
533 package we are trying to push. But with --new that will not work, so
536 or use the value of this option. This option is not needed with the
537 default mechanisms for accessing the archive.
540 Print a usage summary.
542 .BI --initiator-tempdir= directory
543 dgit rpush uses a temporary directory on the invoking (signing) host.
544 This option causes dgit to use
546 instead. Furthermore, the specified directory will be emptied,
547 removed and recreated before dgit starts, rather than removed
548 after dgit finishes. The directory specified must be an absolute
552 Do not delete the destination directory if clone fails.
553 .SH WORKFLOW - SIMPLE
554 It is always possible with dgit to clone or fetch a package, make
555 changes in git (using git-commit) on the suite branch
556 .RB ( "git checkout dgit/" \fIsuite\fR)
557 and then dgit push. You can use whatever gitish techniques you like
558 to construct the commits to push;
559 the only requirement is that what you push is a
560 descendant of the state of the archive, as provided by dgit in the
561 remote tracking branch
562 .BR remotes/dgit/dgit/ \fIsuite\fR.
564 If you are using dgit to do an NMU (in Debian),
565 and don't know about the
566 maintainers' preferred packaging workflows, you should make your
567 changes as a linear series of (logicially separated) commits on top of
568 what's already in the archive.
570 If you are lucky the other uploaders have also used dgit and
571 integrated the other relevant git history; if not you can fetch it
572 into your tree and cherry-pick etc. as you wish.
573 .SH WORKFLOW - INTEGRATING BETWEEN DGIT AND OTHER GIT HISTORY
574 If you are the maintainer of a package dealing with uploads made
575 without dgit, you will probably want to merge the synthetic commits
576 (made by dgit to represent the uploads) into your git history.
577 Normally you can just merge the dgit branch into your own master, or
578 indeed if you do your work on the dgit local suite branch
580 you can just use dgit pull.
582 However the first time dgit is used it will generate a new origin
583 commit from the archive which won't be linked into the rest of your
584 git history. You will need to merge this.
586 If last upload was in fact made with git, you should usually proceed
587 as follows: identify the commit which was actually used to build the
588 package. (Hopefully you have a tag for this.) Check out the dgit
590 .RB ( "git checkout dgit/" \fIsuite\fR)
591 and merge that other commit
592 .RB ( "git merge debian/" \fIversion\fR).
593 Hopefully this merge will be trivial because the two trees should
594 be very similar. The resulting branch head can be merged into your
596 .RB ( "git checkout master && git merge dgit/" \fIsuite\fR).
598 If last upload was not made with git, a different approach is required
599 to start using dgit. First, do
601 (or clone) to obtain a git history representation of what's in the
602 archive and record it in the
603 .BI remotes/dgit/dgit/ suite
604 tracking branch. Then somehow, using your other git history
605 plus appropriate diffs and cherry picks from the dgit remote tracking
606 branch, construct a git commit whose tree corresponds to the tree to use for the
607 next upload. If that commit-to-be-uploaded is not a descendant of the
608 dig remote tracking branch, check it out and say
609 .BR "git merge -s ours remotes/dgit/dgit/" \fIsuite\fR;
610 that tells git that we are deliberately throwing away any differences
611 between what's in the archive and what you intend to upload.
614 to actually upload the result.
616 dgit can be configured via the git config system.
617 You may set keys with git-config (either in system-global or per-tree
618 configuration), or provide
620 on the dgit command line.
622 Settings likely to be useful for an end user include:
624 .BR dgit-suite. \fIsuite\fR .distro " \fIdistro\fR"
625 Specifies the distro for a suite. dgit keys off the suite name (which
626 appears in changelogs etc.), and uses that to determine the distro
627 which is involved. The config used is thereafter that for the distro.
629 .BI dgit.default.distro " distro"
630 The default distro for an unknown suite.
632 .BR dgit-distro. \fIdistro\fR .readonly " " auto | a " | " true | t | y | 1 " | " false | f | n | 0
633 Whether you have push access to the distro.
634 For Debian, it is OK to use auto, which uses readonly mode if you are
635 not pushing right now;
636 but, setting this to false will avoid relying on the mirror of the dgit
637 git repository server.
639 .BI dgit-distro. distro .keyid
643 .BI dgit-distro. distro .mirror " url"
645 .BI dgit-distro. distro .username
646 Not relevant for Debian.
648 .BI dgit-distro. distro .upload-host
649 Might be useful if you have an intermediate queue server.
651 .BI dgit-distro. distro .user-name " " dgit-distro. distro .user-email
652 Values to configure for user.name and user.email in new git trees. If
653 not specified, the DEBFULLNAME and DEBEMAIL environment variables are
654 used, respectively. Only used if .setup-usermail is not disabled.
656 .BI dgit-distro. distro .setup-useremail
657 Whether to set user.name and user.email in new git trees.
658 True by default. Ignored for dgit setup-setup-useremail, which does it anyway.
660 .BI dgit-distro. distro .setup-mergechangelogs
661 Whether to setup a merge driver which uses dpkg-mergechangelogs for
662 debian/changelog. True by default. Ignored for dgit
663 setup-mergechangelogs, which does it anyway.
665 .BI dgit-distro. distro .cmd- cmd
666 Program to use instead of
669 .BR -- \fIcmd\fR = "... ."
671 .BI dgit-distro. distro .opts- cmd
672 Extra options to pass to
675 .BR -- \fIcmd\fR : "... ."
676 To pass several options, configure multiple values in git config
677 (with git config --add). The options for
678 .BI dgit.default.opts- cmd
679 .BI dgit-distro. distro /push.opts- cmd
680 and are all used, followed by options from dgit's command line.
681 .SH ACCESS CONFIGURATION
682 There are many other settings which specify how a particular distro's
683 services (archive and git) are provided. These should not normally be
684 adjusted, but are documented for the benefit of distros who wish to
687 .BR dgit-distro. \fIdistro\fR /push. *
688 If set, overrides corresponding non \fB/push\fR config when
693 .BI dgit-distro. distro .git-url
695 .BR dgit-distro. \fIdistro\fR .git-url [ -suffix ]
697 .BI dgit-distro. distro .git-proto
699 .BI dgit-distro. distro .git-path
701 .BR dgit-distro. \fIdistro\fR .git-check " " true | false | url | ssh-cmd
703 .BI dgit-distro. distro .git-check-suffix
705 .BR dgit-distro. \fIdistro\fR .diverts.divert " " new-distro | / \fIdistro-suffix\fR
707 .BI dgit-distro. distro .git-create " " ssh-cmd | true
709 .BR dgit-distro. \fIdistro\fR .archive-query " " ftpmasterapi: " | " madison: "\fIdistro\fR | " dummycat: "\fI/path\fR | " sshpsql: \fIuser\fR @ \fIhost\fR : \fIdbname\fR
711 .BR dgit-distro. \fIdistro\fR .archive-query- ( url | tls-key | curl-ca-args )
713 .BI dgit-distro. distro .madison-distro
715 .BI dgit-distro. distro .archive-query-default-component
717 .BI dgit-distro. distro .ssh
719 .BI dgit-distro. distro .sshpsql-dbname
721 .BR dgit-distro. \fIdistro\fR . ( git | sshpsql ) - ( user | host | user-force )
723 .BI dgit-distro. distro .backports-quirk
727 .BR dgit-distro. \fIdistro\fR . *
728 .SH ENVIRONMENT VARIABLES
730 .BR DGIT_SSH ", " GIT_SSH
731 specify an alternative default program (and perhaps arguments) to use
732 instead of ssh. DGIT_SSH is consulted first and may contain arguments;
733 if it contains any whitespace will be passed to the shell. GIT_SSH
734 specifies just the program; no arguments can be specified, so dgit
735 interprets it the same way as git does.
737 also the --ssh= and --ssh: options.
739 .BR DEBEMAIL ", " DEBFULLNAME
740 Default git user.email and user.name for new trees. See
741 .BR "dgit setup-new-tree" .
743 .BR gpg ", " dpkg- "..., " debsign ", " git ", " curl ", " dput ", " LWP::UserAgent
744 and other subprograms and modules used by dgit are affected by various
745 environment variables. Consult the documentaton for those programs
748 dgit's git representation of format `3.0 (quilt)' source packages does
749 not represent the patch stack as git commits. Currently the patch
750 series representation cannot round trip between git and the archive.
751 Ideally dgit would represent a quilty package with an origin commit of
752 some kind followed by the patch stack as a series of commits followed
753 by a pseudo-merge (to make the branch fast-forwarding). This would
754 also mean a new `dgit rebase-prep' command or some such to turn such a
755 fast-forwarding branch back into a rebasing patch stack, and a `force'
756 option to dgit push (perhaps enabled automatically by a note left by
757 rebase-prep) which will make the required pseudo-merge.
759 If the dgit push fails halfway through, it should be restartable and
760 idempotent. However this is not true for the git tag operation.
761 Also, it would be good to check that the proposed signing key is
762 available before starting work.
764 dgit's handling of .orig.tar.gz is not very sophisticated. Ideally
765 the .orig.tar.gz could be transported via the git repo as git tags.
766 Doing this is made more complicated by the possibility of a `3.0
767 (quilt)' package with multiple .orig tarballs.
769 dgit's build functions, and dgit push, should not make any changes to
770 your current HEAD. Sadly this is necessary for packages in the `3.0
771 (quilt)' source format. This is ultimately due to what I consider
772 design problems in quilt and dpkg-source.
774 There should be an option which arranges for the `3.0 (quilt)'
775 autocommit(s) to not appear on your HEAD, but instead only in the
776 remote tracking suite branch.
778 The option parser requires values to be cuddled to the option name.
780 --dry-run does not always work properly, as not doing some of the git
781 fetches may result in subsequent actions being different. Doing a
782 non-dry-run dgit fetch first will help.
789 \fBgit-buildpackage\fP(1),
790 \fBdpkg-buildpackage\fP(1),
792 https://wiki.debian.org/Alioth