X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit.1;h=a21f212dc94382ae528a028254122585a7b15937;hp=67aa2fab65c2785091ae5847dfb110225f03d2b0;hb=770df553c36474e58926dfe833d97b375cd9c272;hpb=07497abfd7bc78144279fbb87a6435aad18b9c0a diff --git a/dgit.1 b/dgit.1 index 67aa2fab..a21f212d 100644 --- a/dgit.1 +++ b/dgit.1 @@ -17,6 +17,10 @@ dgit \- git integration with the Debian archive [\fIbuild\-opts\fP] .br .B dgit +[\fIdgit\-opts\fP] \fBpbuilder\fP|\fBcowbuilder\fP +[\fIdebbuildopts\fP] +.br +.B dgit [\fIdgit\-opts\fP] \fBpush\fP|\fBpush-source\fP [\fIdgit\-opts\fP] [\fIsuite\fP] .br @@ -46,6 +50,7 @@ dgit-maint-debrebase(7) for maintainers: a pure-git rebasish workflow dgit-maint-merge(7) for maintainers: a pure-git merging workflow dgit-maint-gbp(7) for maintainers already using git-buildpackage dgit-sponsorship(7) for sponsors and sponsored contributors +dgit-downstream-dsc(7) setting up dgit push for a new distro .TE .LP See \fBdgit(7)\fP for detailed information about the data @@ -193,6 +198,35 @@ You probably want to pass -A, to request those. .IP Tagging, signing and actually uploading should be left to dgit push. .TP +\fBdgit pbuilder\fR [\fIdebbuildopts\fP] +Constructs the source package, uses +.B pbuilder +to do a binary build, and uses mergechanges to merge the source and +binary changes files. +The output is left in +.IR package \fB_\fR version \fB_multi.changes\fR. + +You should ensure that your dgit --build-products-dir setting matches +your pbuilder --buildresult. + +The \fIdebbuildopts\fP are passed to pbuilder using its --debbuildopts +option. If you want to pass other options to pbuilder, use the +\fB--pbuilder:\fR dgit option as described below +(remember that dgit options should appear between \fBdgit\fR and +\fBpbuilder\fR). + +You should ensure that in your pbuilderrc you do +.B not +have the setting +.B SOURCE_ONLY_CHANGES=yes +as this may cause trouble. +.TP +\fBdgit cowbuilder\fR [\fIdebbuildopts\fP] +Like \fBdgit pbuilder\fR, but uses +.B cowbuilder +instead of +.B pbuilder. +.TP \fBdgit gbp-build\fR ... Runs .B git-buildpackage @@ -437,6 +471,26 @@ to cause it to exclude exactly the .git diredcory and nothing else. The separate arguments are unquoted, separated by spaces, and do not contain spaces. +.TP +.B dgit print-unapplied-treeish +Constructs a tree-ish approximating the patches-unapplied state +of your 3.0 (quilt) package, +and prints the git object name to stdout. +This requires appropriate .orig tarballs. +This tree object is identical to your .origs +as regards upstream files. +The contents of the debian subdirectory is not interesting +and should not be inspected; +except that debian/patches will be identical to your HEAD. + +To make this operate off-line, +the access configuration key +which is used to determine the build-products-dir +is the uncanonicalised version of the suite name from the changelog, +or (of course) dgit.default.build-products-dir. +See ACCESS CONFIGURATION, below. + +This function is primarily provided for the benefit of git-debrebase. .SH OPTIONS .TP .BR --dry-run " | " -n @@ -528,12 +582,17 @@ refuse to push. It may (for Debian, will) be unable to access the git history for any packages which have been newly pushed and have not yet been published. .TP -.BR --ignore-dirty -Do not complain if the working tree does not match your git HEAD. +.BR --include-dirty +Do not complain if the working tree does not match your git HEAD, +and when building, +include the changes from your working tree. This can be useful with build, if you plan to commit later. (dgit push will still ensure that the .dsc you upload and the git tree you push are identical, so this option won't make broken pushes.) .TP +.BR --ignore-dirty +Deprecated alias for --include-dirty. +.TP .BR --overwrite [=\fIprevious-version\fR] Declare that your HEAD really does contain all the (wanted) changes @@ -622,7 +681,7 @@ Also, it can mean that dgit fails to find necessary git commits. .TP -.BR --dgit-view-save= \fIbranch\fR|\fIref\fR +.BR --save-dgit-view= \fIbranch\fR|\fIref\fR Specifies that when a split view quilt mode is in operation, and dgit calculates (or looks up in its cache) @@ -642,6 +701,10 @@ And it is only effective with If ref does not start with refs/ it is taken to to be a branch - i.e. refs/heads/ is prepended. + +.B --dgit-view-save +is a deprecated alias for +--save-dgit-view. .TP .BI --deliberately- something Declare that you are deliberately doing @@ -838,9 +901,20 @@ Note that \fBdgit push-source\fR will always find the right .changes, regardless of this option. .TP .BI --build-products-dir= directory -Specifies where to find the built files to be uploaded. -By default, dgit looks in the parent directory +Specifies where to find and create tarballs, binry packages, +source packages, .changes files, and so on. + +By default, dgit uses the parent directory .RB ( .. ). + +Changing this setting may necessitate +moving .orig tarballs to the new directory, +so it is probably best to +use the +.BI dgit.default.build-products-dir +configuration setting +(see CONFIGURATION, below) +which this command line option overrides). .TP .BI --no-rm-on-error Do not delete the destination directory if clone fails. @@ -911,6 +985,8 @@ Specifies a single additional option to pass to .BR dpkg-buildpackage , .BR dpkg-genchanges , .BR sbuild , +.BR pbuilder , +.BR cowbuilder , .BR ssh , .BR dgit , .BR git-debrebase , @@ -958,6 +1034,8 @@ Specifies alternative programs to use instead of .BR dpkg-buildpackage , .BR dpkg-genchanges , .BR sbuild , +.BR pbuilder , +.BR cowbuilder , .BR gpg , .BR ssh , .BR dgit , @@ -996,6 +1074,14 @@ In both cases, unusually, the specified value is split on whitespace to produce a command and possibly some options and/or arguments. +For pbuilder and cowbuilder, the defaults are +.BR "sudo -E pbuilder" +and +.BR "sudo -E cowbuilder" +respectively. +Like with gbp-build and gbp pq, +the specified value is split on whitespace. + For .BR ssh , the default value is taken from the @@ -1095,6 +1181,12 @@ on the dgit command line. .LP Settings likely to be useful for an end user include: .TP +.BI dgit.default.build-products-dir +Specifies where to find the built files to be uploaded, +when --build-products-dir is not specified. The default is +the parent directory +.RB ( .. ). +.TP .BR dgit-suite. \fIsuite\fR .distro " \fIdistro\fR" Specifies the distro for a suite. dgit keys off the suite name (which appears in changelogs etc.), and uses that to determine the distro