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 treats the Debian archive as a version control system, and
31 bidirectionally gateways between the archive and git. The git view of
32 the package can contain the usual upstream git history, and will be
33 augmented by commits representing uploads done by other developers not
34 using dgit. This git history is stored in a canonical location known
37 which lives outside the Debian archive (currently, on Alioth).
39 The usual workflow is: 1. clone or fetch; 2. make and commit changes
40 in git as desired; 3. run dgit build, dgit sbuild or dgit
41 build-source, or generate the source and binary packages for upload
42 some other way; 4. do pre-upload tests of the proposed upload; 5. run
45 \fBdgit clone\fR \fIpackage\fP [\fIsuite\fP] [\fB./\fP\fIdir|\fB/\fP\fIdir\fR]
46 Consults the archive and dgit-repos to construct the git view of
53 in a new directory (named
56 also, downloads any necessary orig tarballs.
58 The suite's git tip is
59 left on the local branch
61 ready for work, and on the corresponding dgit remote tracking branch.
64 remote will be set up to point to the package's dgit-repos tree
65 for the distro to which
69 For your convenience, the
71 remote will be set up from the package's Vcs-Git field, if there is
72 one - but note that in the general case the history found there may be
73 different to or even disjoint from dgit's view.
75 \fBdgit fetch\fR [\fIsuite\fP]
76 Consults the archive and git-repos to update the git view of
77 history for a specific suite (and downloads any necessary orig
78 tarballs), and updates the remote tracking branch
79 .BR remotes/dgit/dgit/ \fIsuite\fR.
80 If the current branch is
82 then dgit fetch defaults to
84 otherwise it parses debian/changelog and uses the suite specified
87 \fBdgit pull\fR [\fIsuite\fP]
88 Does dgit fetch, and then merges the new head of the remote tracking
90 .BI remotes/dgit/dgit/ suite
91 into the current branch.
96 with some suitable options. Options and argumments after build
97 will be passed on to dpkg-buildpackage. It is not necessary to use
98 dgit build when using dgit; it is OK to use any approach which ensures
99 that the generated source package corresponds to the relevant git
102 Tagging, signing and actually uploading should be left to dgit push.
104 \fBdgit build-source\fR ...
105 Builds the source package, and a changes file for a prospective
106 source-only upload, using
108 The output is left in
109 .IR package \fB_\fR version \fB.dsc\fR
111 .IR package \fB_\fR version \fB_source.changes\fR.
113 Tagging, signing and actually uploading should be left to dgit push.
116 Cleans the current working tree (according to the --clean= option in
120 Print a usage summary.
122 \fBdgit sbuild\fR ...
123 Constructs the source package, uses
125 to do a binary build, and uses mergechanges to merge the source and
126 binary changes files. Options and argumments after sbuild will be
127 passed on to sbuild. Changes files matching
128 .IB package _ version _*.changes
129 in the parent directory will be removed; the output is left in
130 .IR package \fB_\fR version \fB_multi.changes\fR.
132 Tagging, signing and actually uploading should be left to dgit push.
134 \fBdgit git-build\fR ...
137 with some suitable options. Options and argumments after git-build
138 will be passed on to git-buildpackage.
140 Tagging, signing and actually uploading should be left to dgit push.
142 \fBdgit push\fR [\fIsuite\fP]
143 Does an `upload', pushing the current HEAD to the archive (as a source
144 package) and to dgit-repos (as git commits). The package must already
145 have been built ready for upload, with the .dsc and .changes
146 left in the parent directory. It is normally best to do the build
147 with dgit too (eg with dgit sbuild): some existing build tools pass
148 unhelpful options to dpkg-source et al by default, which can result in
149 the built source package not being identical to the git tree.
151 In more detail: dgit push checks that the current HEAD corresponds to
152 the .dsc. It then pushes the HEAD to the suite's dgit-repos branch,
153 makes a signed git tag, edits the .dsc to contain the dgit metadata
154 field, runs debsign to sign the upload (.dsc and .changes), pushes the
155 signed tag, and finally uses dput to upload the .changes to the
158 dgit push always uses the package, suite and version specified in the
159 debian/changelog and the .dsc, which must agree. If the command line
160 specifies a suite then that must match too.
162 If dgit push fails while uploading, it is fine to simply retry the
163 dput on the .changes file at your leisure.
165 \fBdgit rpush\fR \fIbuild-host\fR\fB:\fR\fIbuild-dir\fR [\fIpush args...\fR]
166 Pushes the contents of the specified directory on a remote machine.
167 This is like running dgit push on build-host with build-dir as the
168 current directory; however, signing operations are done on the
169 invoking host. This allows you to do a push when the system which has
170 the source code and the build outputs has no access to the key:
172 1. Clone on build host (dgit clone)
174 2. Edit code on build host (edit, git commit)
176 3. Build package on build host (dgit build)
178 4. Test package on build host or elsewhere (dpkg -i, test)
180 5. Upload by invoking dgit rpush on host with your GPG key.
182 However, the build-host must be able to ssh to the dgit repos. If
183 this is not already the case, you must organise it separately, for
184 example by the use of ssh agent forwarding.
186 The remaining arguments are treated just as dgit push would handle
189 build-host and build\-dir can be passed as separate
190 arguments; this is assumed to be the case if the first argument
191 contains no : (except perhaps one in [ ], to support IPv6 address
194 You will need similar enough versions of dgit on the build-host and
195 the invocation host. The build-host needs gnupg installed, with your
196 public key in its keyring (but not your private key, obviously).
199 `3.0 (quilt)' format source packages need changes representing not
200 only in-tree but also as patches in debian/patches. dgit quilt-fixup
201 checks whether this has been done; if not, dgit will make appropriate
202 patches in debian/patches and also commit the resulting changes to
205 This is normally done automatically by dgit build and dgit push.
207 dgit will try to turn each relevant commit in your git history into a
208 new quilt patch. dgit cannot convert nontrivial merges, or certain
209 other kinds of more exotic history. If dgit can't find a suitable
210 linearisation of your history, by default it will fail, but you can
211 ask it to generate a single squashed patch instead.
214 Prints version information and exits.
216 .BI "dgit clone-dgit-repos-server" " destdir"
217 Tries to fetch a copy of the source code for the dgit-repos-server,
218 as actually being used on the dgit git server, as a git tree.
222 Go through the motions, fetching all information needed, but do not
223 actually update the output(s). For push, dgit does
224 the required checks and leaves the new .dsc in a temporary file,
225 but does not sign, tag, push or upload.
228 Go through many more of the motions: do everything that doesn't
229 involve either signing things, or making changes on the public
235 for signing the tag and the upload.
238 does not sign tags or uploads (meaningful only with push).
242 Specifies that we should process source package
244 rather than looking in debian/control or debian/changelog.
245 Valid with dgit fetch and dgit pull, only.
247 .BR --clean=git | -wg
248 The source tree should be cleaned, before building a source package
249 with one of the build options, using
250 .BR "git clean -xdf" .
251 This will delete all files which are not tracked by git. Also, -wg
254 to dpkg-buildpackage, which prevents the package's own clean target
257 --clean=git is useful when the package's clean target is troublesome;
258 the downside is simply that git clean may delete files you forgot to
261 .BR --clean=none | -wn
262 Do not clean the tree before building a source package. If there are
263 files which are not in git, or if the build creates such files, a
264 subsequent dgit push will fail.
266 .BR --clean=dpkg-source | -wd
267 Use dpkg-buildpackage to do the clean, so that the source package
268 is cleaned by dpkg-source running the package's clean target.
269 This is the default. It requires the package's build dependencies.
272 The package may be new in this suite. Without this, dgit will
276 Do not complain if the working tree does not match your git HEAD.
277 This can be useful with build, if you plan to commit later. (dgit
278 push will still ensure that the .dsc you upload and the git tree
279 you push are identical, so this option won't make broken pushes.)
281 .BI --deliberately- something
282 Declare that you are deliberately doing
284 This can be used to override safety catches, including safety catches
285 which relate to distro-specific policies. The meanings of
287 understood in the context of Debian are discussed below:
289 .BR --deliberately-not-fast-forward
290 Declare that you are deliberately rewinding history. When pushing to
291 Debian, use this when you are making a renewed upload of an entirely
292 new source package whose previous version was not accepted for release
293 from NEW because of problems with copyright or redistributibility.
295 .BR --deliberately-include-questionable-history
296 Declare that you are deliberately including, in the git history of
297 your current push, history which contains a previously-submitted
298 version of this package which was not approved (or has not yet been
299 approved) by the ftpmasters. When pushing to Debian, only use this
300 option after verifying that: none of the rejected-from-NEW (or
301 never-accepted) versions in the git history of your current push, were
302 rejected by ftpmaster for copyright or redistributability reasons.
304 .BR --deliberately-fresh-repo
305 Declare that you are deliberately rewinding history and want to
306 throw away the existing repo. Not relevant when pushing to Debian,
307 as the Debian server will do this automatically when necessary.
310 When fixing up source format `3.0 (quilt)' metadata, insist on
311 generating a linear patch stack. If such a stack cannot be generated,
315 When fixing up source format `3.0 (quilt)' metadata, prefer to
316 generate a linear patch stack, but if that doesn't seem possible,
317 generate a single squashed patch for all the changes made in git.
318 This is not a good idea for an NMU in Debian.
321 When fixing up source format `3.0 (quilt)' metadata,
322 generate a single squashed patch for all the changes made in git.
323 This is not a good idea for an NMU in Debian.
326 Check whether source format `3.0 (quilt)' metadata would need fixing
327 up, but, if it does, fail. You must then fix the metadata yourself
328 somehow before pushing. (NB that dpkg-source --commit will not work
329 because the dgit git tree does not have a
333 .BR --quilt=nocheck | --no-quilt-fixup
334 Do not check whether up source format `3.0 (quilt)' metadata needs
335 fixing up. If you use this option and the metadata did in fact need
336 fixing up, dgit push will fail.
339 Prints debugging information to stderr. Repeating the option produces
340 more output (currently, up to -DD is meaningfully different).
343 Specifies a git configuration option. dgit itself is also controlled
344 by git configuration options.
346 .RI \fB-v\fR version "|\fB_\fR | " \fB--since-version=\fR version |\fB_\fR
349 option to pass to dpkg-genchanges, during builds. Changes (from
350 debian/changelog) since this version will be included in the built
351 changes file, and hence in the upload. If this option is not
352 specified, dgit will query the archive and use the latest version
353 uploaded to the intended suite.
357 inhibits this, so that no -v option will be passed to dpkg-genchanges
358 (and as a result, only the last stanza from debian/changelog will
359 be used for the build and upload).
361 .RI \fB-m\fR maintaineraddress
362 Passed to dpkg-genchanges (eventually).
364 .RI \fB--ch:\fR option
365 Specifies a single additional option to pass, eventually, to
368 .RI \fB--curl=\fR program |\fB--dput=\fR program |...
369 Specifies alternative programs to use instead of
374 .BR dpkg-buildpackage ,
375 .BR dpkg-genchanges ,
383 For dpkg-buildpackage, dpkg-genchanges, mergechanges and sbuild,
384 this applies only when the program is invoked directly by dgit.
386 For dgit, specifies the command to run on the remote host when dgit
387 rpush needs to invoke a remote copy of itself. (dgit also reinvokes
388 itself as the EDITOR for dpkg-source --commit; this is done using
389 argv[0], and is not affected by --dgit=).
391 For ssh, the default value is taken from the
395 environment variables, if set (see below). And, for ssh, when accessing the
396 archive and dgit-repos, this command line setting is overridden by the
398 .BI dgit-distro. distro .ssh
401 (which can in turn be overridden with -c). Also, when dgit is using
402 git to access dgit-repos, only git's idea of what ssh to use (eg,
406 .RI \fB--curl:\fR option |\fB--dput:\fR option |...
407 Specifies a single additional option to pass to
412 .BR dpkg-buildpackage ,
413 .BR dpkg-genchanges ,
419 Can be repeated as necessary.
421 For dpkg-buildpackage, dpkg-genchanges, mergechanges and sbuild,
422 this applies only when the program is invoked directly by dgit.
423 Usually, for passing options to dpkg-genchanges, you should use
424 .BR --ch: \fIoption\fR.
426 See notes above regarding ssh and dgit.
428 NB that --gpg:option is not supported (because debsign does not
429 have that facility). But see -k.
431 .BR -d "\fIdistro\fR | " --distro= \fIdistro\fR
432 Specifies that the suite to be operated on is part of distro
434 This overrides the default value found from the git config option
435 .BR dgit-suite. \fIsuite\fR .distro .
436 The only effect is that other configuration variables (used
437 for accessing the archive and dgit-repos) used are
438 .BR dgit-distro. \fIdistro\fR .* .
440 If your suite is part of a distro that dgit already knows about, you
441 can use this option to make dgit work even if your dgit doesn't know
442 about the suite. For example, specifying
444 will work when the suite is an unknown suite in the Debian archive.
446 To define a new distro it is necessary to define methods and URLs
447 for fetching (and, for dgit push, altering) a variety of information both
448 in the archive and in dgit-repos. How to do this is not yet
449 documented, and currently the arrangements are unpleasant. See
453 Specifies the .changes file which is to be uploaded. By default
454 dgit push looks for single .changes file in the parent directory whose
455 filename suggests it is for the right package and version - or,
456 if there is a _multi.changes file, dgit uses that.
460 pathname contains slashes, the directory part is also used as
462 .BR --build-products-dir ;
463 otherwise, the changes file is expected in that directory (by
467 .BI --build-products-dir= directory
468 Specifies where to find the built files to be uploaded.
469 By default, dgit looks in the parent directory
472 .BI --existing-package= package
473 dgit push needs to canonicalise the suite name. Sometimes, dgit
474 lacks a way to ask the archive to do this without knowing the
475 name of an existing package. Without --new we can just use the
476 package we are trying to push. But with --new that will not work, so
479 or use the value of this option. This option is not needed with the
480 default mechanisms for accessing the archive.
483 Print a usage summary.
485 .BI --initiator-tempdir= directory
486 dgit rpush uses a temporary directory on the invoking (signing) host.
487 This option causes dgit to use
489 instead. Furthermore, the specified directory will be emptied,
490 removed and recreated before dgit starts, rather than removed
491 after dgit finishes. The directory specified must be an absolute
495 Do not delete the destination directory if clone fails.
496 .SH WORKFLOW - SIMPLE
497 It is always possible with dgit to clone or fetch a package, make
498 changes in git (using git-commit) on the suite branch
499 .RB ( "git checkout dgit/" \fIsuite\fR)
500 and then dgit push. You can use whatever gitish techniques you like
501 to construct the commit to push; the only requirement is that it is a
502 descendant of the state of the archive, as provided by dgit in the
503 remote tracking branch
504 .BR remotes/dgit/dgit/ \fIsuite\fR.
506 If you are using dgit to do an NMU, and don't know about the
507 maintainers' preferred packaging workflows, you should make your
508 changes as a linear series of (logicially separated) commits on top of
509 what's already in the archive.
511 If you are lucky the other uploaders have also used dgit and
512 integrated the other relevant git history; if not you can fetch it
513 into your tree and cherry-pick etc. as you wish.
514 .SH WORKFLOW - INTEGRATING BETWEEN DGIT AND OTHER GIT HISTORY
515 If you are the maintainer of a package dealing with uploads made
516 without dgit, you will probably want to merge the synthetic commits
517 (made by dgit to represent the uploads) into your git history.
518 Normally you can just merge the dgit branch into your own master, or
519 indeed if you do your work on the dgit local suite branch
521 you can just use dgit pull.
523 However the first time dgit is used it will generate a new origin
524 commit from the archive which won't be linked into the rest of your
525 git history. You will need to merge this.
527 If last upload was in fact made with git, you should usually proceed
528 as follows: identify the commit which was actually used to build the
529 package. (Hopefully you have a tag for this.) Check out the dgit
531 .RB ( "git checkout dgit/" \fIsuite\fR)
532 and merge that other commit
533 .RB ( "git merge debian/" \fIversion\fR).
534 Hopefully this merge will be trivial because the two trees should
535 be the same. The resulting branch head can be merged into your
537 .RB ( "git checkout master && git merge dgit/" \fIsuite\fR).
539 If last upload was not made with git, a different approach is required
540 to start using dgit. First, do
542 (or clone) to obtain a git history representation of what's in the
543 archive and record it in the
544 .BI remotes/dgit/dgit/ suite
545 tracking branch. Then somehow, using your other git history
546 plus appropriate diffs and cherry picks from the dgit remote tracking
547 branch, construct a git commit whose tree corresponds to the tree to use for the
548 next upload. If that commit-to-be-uploaded is not a descendant of the
549 dig remote tracking branch, check it out and say
550 .BR "git merge -s ours remotes/dgit/dgit/" \fIsuite\fR;
551 that tells git that we are deliberately throwing away any differences
552 between what's in the archive and what you intend to upload.
555 to actually upload the result.
557 You may use any suitable git workflow with dgit, provided you
558 satisfy dgit's requirements:
560 dgit maintains a pseudo-remote called
562 with one branch per suite. This remote cannot be used with
567 repository for each package contains one ref per suite named
568 \fBrefs/dgit/\fR\fIsuite\fR. These should be pushed to only by
569 dgit. They are fast forwarding. Each push on this branch
570 corresponds to an upload (or attempted upload).
572 However, it is perfectly fine to have other branches in dgit-repos;
573 normally the dgit-repos repo for the package will be accessible via
574 the remote name `origin'.
576 dgit push will also (by default) make signed tags called
578 and push them to dgit-repos, but nothing depends on these tags
581 dgit push can operate on any commit which is a descendant of the
582 current dgit/suite tip in dgit-repos.
584 Uploads made by dgit contain an additional field
586 in the source package .dsc. (This is added by dgit push.)
587 This specifies a commit (an ancestor of the dgit/suite
588 branch) whose tree is identical to the unpacked source upload.
590 Uploads not made by dgit are represented in git by commits which are
591 synthesised by dgit. The tree of each such commit corresponds to the
592 unpacked source; there is an origin commit with the contents, and a
593 psuedo-merge from last known upload - that is, from the contents of
594 the dgit/suite branch.
596 dgit expects repos that it works with to have a
598 remote. This refers to the well-known dgit-repos location
599 (currently, the dgit-repos project on Alioth). dgit fetch updates
600 the remote tracking branch for dgit/suite.
602 dgit does not (currently) represent the orig tarball(s) in git. The
603 orig tarballs are downloaded (by dgit clone) into the parent
604 directory, as with a traditional (non-gitish) dpkg-source workflow.
605 You need to retain these tarballs in the parent directory for dgit
608 dgit repositories could be cloned with standard (git) methods. The
609 only exception is that for sourcefull builds / uploads the orig
610 tarball(s) need to be present in the parent directory.
612 To a user looking at the archive, changes pushed using dgit look like
613 changes made in an NMU: in a `3.0 (quilt)' package the delta from the
614 previous upload is recorded in a new patch constructed by dpkg-source.
615 .SH READ-ONLY DISTROS
616 Distros which do not maintain a set of dgit history git repositories
617 can still be used in a read-only mode with dgit. Currently Ubuntu
618 is configured this way.
619 .SH PACKAGE SOURCE FORMATS
620 If you are not the maintainer, you do not need to worry about the
621 source format of the package. You can just make changes as you like
622 in git. If the package is a `3.0 (quilt)' package, the patch stack
623 will usually not be represented in the git history.
624 .SH FORMAT 3.0 (QUILT)
625 For a format `3.0 (quilt)' source package, dgit may have to make a
626 commit on your current branch to contain metadata used by quilt and
629 This is because `3.0 (quilt)' source format represents the patch stack
630 as files in debian/patches/ actually inside the source tree. This
631 means that, taking the whole tree (as seen by git or ls) (i)
632 dpkg-source cannot represent certain trees, and (ii) packing up a tree
633 in `3.0 (quilt)' and then unpacking it does not always yield the same
636 dgit will automatically work around this for you when building and
637 pushing. The only thing you need to know is that dgit build, sbuild,
638 etc., may make new commits on your HEAD. If you're not a quilt user
639 this commit won't contain any changes to files you care about.
641 You can explicitly request that dgit do just this fixup, by running
644 If you are a quilt user you need to know that dgit's git trees are
645 `patches applied packaging branches' and do not contain the .pc
646 directory (which is used by quilt to record which patches are
647 applied). If you want to manipulate the patch stack you probably want
648 to be looking at tools like git-dpm.
649 .SH FILES IN THE SOURCE PACKAGE BUT NOT IN GIT
650 This section is mainly of interest to maintainers who want to use dgit
651 with their existing git history for the Debian package.
653 Some developers like to have an extra-clean git tree which lacks files
654 which are normally found in source tarballs and therefore in Debian
655 source packages. For example, it is conventional to ship ./configure
656 in the source tarball, but some people prefer not to have it present
657 in the git view of their project.
659 dgit requires that the source package unpacks to exactly the same
660 files as are in the git commit on which dgit push operates. So if you
661 just try to dgit push directly from one of these extra-clean git
662 branches, it will fail.
664 As the maintainer you therefore have the following options:
667 Persuade upstream that the source code in their git history and the
668 source they ship as tarballs should be identical. Of course simply
669 removing the files from the tarball may make the tarball hard for
672 One answer is to commit the (maybe autogenerated)
673 files, perhaps with some simple automation to deal with conflicts and
674 spurious changes. This has the advantage that someone who clones
675 the git repository finds the program just as easy to build as someone
676 who uses the tarball.
679 Have separate git branches which do contain the extra files, and after
680 regenerating the extra files (whenever you would have to anyway),
681 commit the result onto those branches.
684 Provide source packages which lack the files you don't want
685 in git, and arrange for your package build to create them as needed.
686 This may mean not using upstream source tarballs and makes the Debian
687 source package less useful for people without Debian build
690 Of course it may also be that the differences are due to build system
691 bugs, which cause unintended files to end up in the source package.
692 dgit will notice this and complain. You may have to fix these bugs
693 before you can unify your existing git history with dgit's.
695 dgit looks at the following git config keys to control its behaviour.
696 You may set them with git-config (either in system-global or per-tree
697 configuration), or provide
699 on the dgit command line.
701 .BI dgit-suite. suite .distro
703 .BI dgit.default.distro
705 .BI dgit-distro. distro .username
707 .BI dgit-distro. distro .git-url
709 .BI dgit-distro. distro .git-user
711 .BI dgit-distro. distro .git-host
713 .BI dgit-distro. distro .git-proto
715 .BI dgit-distro. distro .git-path
717 .BI dgit-distro. distro .git-check
719 .BI dgit-distro. distro .git-create
721 .BI dgit-distro. distro .upload-host
723 .BI dgit-distro. distro .mirror
725 .BI dgit-distro. distro .archive-query
727 .BI dgit-distro. distro .archive-query-default-component
729 .BI dgit-distro. distro .sshpsql-user
731 .BI dgit-distro. distro .sshpsql-host
733 .BI dgit-distro. distro .sshpsql-dbname
735 .BI dgit-distro. distro .ssh
737 .BI dgit-distro. distro .keyid
741 .BR dgit-distro. \fIdistro\fR . *
742 .SH ENVIRONMENT VARIABLES
744 .BR DGIT_SSH ", " GIT_SSH
745 specify an alternative default program (and perhaps arguments) to use
746 instead of ssh. DGIT_SSH is consulted first and may contain arguments;
747 if it contains any whitespace will be passed to the shell. GIT_SSH
748 specifies just the program; no arguments can be specified, so dgit
749 interprets it the same way as git does.
751 also the --ssh= and --ssh: options.
753 .BR gpg ", " dpkg- "..., " debsign ", " git ", " curl ", " dput ", " LWP::UserAgent
754 and other subprograms and modules used by dgit are affected by various
755 environment variables. Consult the documentaton for those programs
758 We should be using some kind of vhost/vpath setup for the git repos on
759 alioth, so that they can be moved later if and when this turns out to
762 dgit push should perhaps do `git push origin', or something similar,
765 Debian does not have a working rmadison server, so to find out what
766 version of a package is in the archive, or to canonicalise suite
767 names, we ssh directly into the ftpmaster server and run psql there to
770 The mechanism for checking for and creating per-package repos on
771 alioth is a hideous bodge. One consequence is that dgit currently
772 only works for people with push access.
774 Debian Maintainers are currently not able to push, as there is not
775 currently any mechanism for determining and honouring the archive's
776 ideas about access control. Currently only DDs can push.
778 dgit's git representation of format `3.0 (quilt)' source packages does
779 not represent the patch stack as git commits. Currently the patch
780 series representation cannot round trip between git and the archive.
781 Ideally dgit would represent a quilty package with an origin commit of
782 some kind followed by the patch stack as a series of commits followed
783 by a pseudo-merge (to make the branch fast-forwarding). This would
784 also mean a new `dgit rebase-prep' command or some such to turn such a
785 fast-forwarding branch back into a rebasing patch stack, and a `force'
786 option to dgit push (perhaps enabled automatically by a note left by
787 rebase-prep) which will make the required pseudo-merge.
789 If the dgit push fails halfway through, it should be restartable and
790 idempotent. However this is not true for the git tag operation.
791 Also, it would be good to check that the proposed signing key is
792 available before starting work.
794 dgit's handling of .orig.tar.gz is not very sophisticated. Ideally
795 the .orig.tar.gz could be transported via the git repo as git tags.
796 Doing this is made more complicated by the possibility of a `3.0
797 (quilt)' package with multiple .orig tarballs.
799 dgit's build functions, and dgit push, should not make any changes to
800 your current HEAD. Sadly this is necessary for packages in the `3.0
801 (quilt)' source format. This is ultimately due to what I consider
802 design problems in quilt and dpkg-source.
804 There should be an option which arranges for the `3.0 (quilt)'
805 autocommit(s) to not appear on your HEAD, but instead only in the
806 remote tracking suite branch.
808 The option parser requires values to be cuddled to the option name.
810 dgit assumes knowledge of the archive database. (The information dgit
811 needs is not currently available via any public online service with a
812 well-defined interface, let alone a secure one.)
814 --dry-run does not always work properly, as not doing some of the git
815 fetches may result in subsequent actions being different. Doing a
816 non-dry-run dgit fetch first will help.
822 \fBgit-buildpackage\fP(1),
823 \fBdpkg-buildpackage\fP(1),
825 https://wiki.debian.org/Alioth