Package: dgit Version: 8.3 Severity: minor Tags: patch Dear Maintainer,
write the leading dash(es) of an option as '\-', not just '-', see man-pages(7). The patch does not change the output from nroff. diff -dpru dgit/dgit.1 new-dgit/dgit.1 --- dgit/dgit.1 2019-02-04 02:30:03.000000000 +0000 +++ new-dgit/dgit.1 2019-02-10 16:00:16.000000000 +0000 @@ -147,8 +147,8 @@ commit. Tagging, signing and actually uploading should be left to dgit push. dgit's build operations access the network, -to get the -v option right. -See -v, below. +to get the \-v option right. +See \-v, below. .TP \fBdgit build-source\fR ... Builds the source package, and a changes file for a prospective @@ -163,12 +163,12 @@ Tagging, signing and actually uploading push-source, or dgit push. .TP .B dgit clean -Cleans the current working tree (according to the --clean= option in +Cleans the current working tree (according to the \-\-clean= option in force). .TP -\fBdgit update-vcs-git\fR [\fIsuite\fP|\fB.\fR] [\fB--\fR] [\fIgit fetch options\fR] +\fBdgit update-vcs-git\fR [\fIsuite\fP|\fB.\fR] [\fB\-\-\fR] [\fIgit fetch options\fR] .TQ -\fBdgit update-vcs-git\fR [\fIsuite|\fP\fB.\fR] \fB-\fR +\fBdgit update-vcs-git\fR [\fIsuite|\fP\fB.\fR] \fB\-\fR Sets up, or updates the url of, the vcs-git remote, and (unless \fB-\fR was specified) runs git fetch on it. @@ -194,7 +194,7 @@ The output is left in .IP Note that by default sbuild does not build arch-independent packages. -You probably want to pass -A, to request those. +You probably want to pass \-A, to request those. .IP Tagging, signing and actually uploading should be left to dgit push. .TP @@ -206,12 +206,12 @@ 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. +You should ensure that your dgit \-\-build-products-dir setting matches +your pbuilder \-\-buildresult. -The \fIdebbuildopts\fP are passed to pbuilder using its --debbuildopts +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 +\fB\-\-pbuilder:\fR dgit option as described below (remember that dgit options should appear between \fBdgit\fR and \fBpbuilder\fR). @@ -251,7 +251,7 @@ In more detail: dgit push checks that th the .dsc. It then pushes the HEAD to the suite's dgit-repos branch, adjusts the .changes to include any .origs which the archive lacks and exclude .origs which the archive has -(so -sa and -sd are not needed when building for dgit push), +(so \-sa and \-sd are not needed when building for dgit push), makes a signed git tag, edits the .dsc to contain the dgit metadata field, runs debsign to sign the upload (.dsc and .changes), pushes the signed tag, and finally uses dput to upload the .changes to the @@ -267,11 +267,11 @@ to prepare the branch for source package upload and push. .TP \fBdgit push-source\fR [\fIsuite\fP] -Without \fB-C\fR, builds a source package and dgit pushes it. Saying +Without \fB\-C\fR, builds a source package and dgit pushes it. Saying \fBdgit push-source\fR is like saying "update the source code in the archive to match my git HEAD, and let the autobuilders do the rest." -With \fB-C\fR, performs a dgit push, additionally ensuring that no +With \fB\-C\fR, performs a dgit push, additionally ensuring that no binary packages are uploaded. .TP \fBdgit rpush\fR \fIbuild-host\fR\fB:\fR\fIbuild-dir\fR [\fIpush args...\fR] @@ -286,7 +286,7 @@ l l. 1. Clone on build host (dgit clone) 2. Edit code on build host (edit, git commit) 3. Build package on build host (dgit build) -4. Test package on build host or elsewhere (dpkg -i, test) +4. Test package on build host or elsewhere (dpkg \-i, test) 5. Upload by invoking dgit rpush on host with your GPG key. .TE @@ -390,7 +390,7 @@ dgit can make patches in some situations so dgit quilt-fixup can be useful in its own right. To always use dgit's own patch generator instead of git-debrebase make-patches, -pass --git-debrebase=true to dgit. +pass \-\-git-debrebase=true to dgit. See .B FORMAT 3.0 (QUILT) @@ -421,14 +421,14 @@ and specifying where to find that commit import-dsc might need online access. If this is a problem (or dgit's efforts to find the commit fail), -consider --no-chase-dsc-distro -or --force-import-dsc-with-dgit-field. +consider \-\-no-chase-dsc-distro +or \-\-force-import-dsc-with-dgit-field. There is only one sub-option: -.B --require-valid-signature +.B \-\-require-valid-signature causes dgit to insist that the signature on the .dsc is valid -(using the same criteria as dpkg-source -x). +(using the same criteria as dpkg-source \-x). Otherwise, dgit tries to verify the signature but the outcome is reported only as messages to stderr. @@ -468,7 +468,7 @@ This is hopefully suitable for use as a It may not be useable in a browser. .TP .B dgit print-dpkg-source-ignores -Prints the -i and -I arguments which must be passed to dpkg-souce +Prints the \-i and \-I arguments which must be passed to dpkg-souce to cause it to exclude exactly the .git directory and nothing else. The separate arguments are unquoted, separated by spaces, @@ -495,18 +495,18 @@ See ACCESS CONFIGURATION, below. This function is primarily provided for the benefit of git-debrebase. .SH OPTIONS .TP -.BR --dry-run " | " -n +.BR \-\-dry-run " | " \-n Go through the motions, fetching all information needed, but do not actually update the output(s). For push, dgit does the required checks and leaves the new .dsc in a temporary file, but does not sign, tag, push or upload. .TP -.BR --damp-run " | " -L +.BR \-\-damp-run " | " \-L Go through many more of the motions: do everything that doesn't involve either signing things, or making changes on the public servers. .TP -.BI -k keyid +.BI \-k keyid Use .I keyid for signing the tag and the upload. The default comes from the @@ -515,26 +515,26 @@ distro's config setting (see CONFIGURATION, below), or failing that, the uploader trailer line in debian/changelog. .TP -.B --no-sign +.B \-\-no-sign does not sign tags or uploads (meaningful only with push). .TP .TP -.BI -p package +.BI \-p package Specifies that we should process source package .I package rather than looking in debian/control or debian/changelog. Valid with dgit fetch and dgit pull, only. .TP -.BR --clean=git " | " -wg +.BR \-\-clean=git " | " \-wg Use -.B git clean -xdf +.B git clean \-xdf to clean the working tree, rather than running the package's rules clean target. This will delete all files which are not tracked by git. (Including any files you forgot to git add.) -.BI --clean= ... +.BI \-\-clean= ... options other than dpkg-source are useful when the package's clean target is troublesome, or to avoid needing the build-dependencies. @@ -544,22 +544,22 @@ dgit will only actually clean the tree i or binaries from your working tree). Otherwise it will just check that there are no untracked unignored files. -See --clean=git[-ff],always, below. +See \-\-clean=git[-ff],always, below. .TP -.BR --clean=git-ff " | " -wgf +.BR \-\-clean=git-ff " | " \-wgf Use -.B git clean -xdff +.B git clean \-xdff to clean the working tree. Like -git clean -xdf +git clean \-xdf but it also removes any subdirectories containing different git trees (which only unusual packages are likely to create). .TP -.BR --clean=git "[" -ff "]" ,always " | " -wga " | " -wgfa -Like --clean=git, but always does the clean and not just a check, +.BR \-\-clean=git "[" -ff "]" ,always " | " \-wga " | " \-wgfa +Like \-\-clean=git, but always does the clean and not just a check, deleting any untracked un-ignored files. .TP -.BR --clean=check " | " --clean=check,ignores " | " -wc " | " -wci +.BR \-\-clean=check " | " \-\-clean=check,ignores " | " \-wc " | " \-wci Merely check that the tree is clean (does not contain uncommitted files). Avoids running rules clean, @@ -568,7 +568,7 @@ and can avoid needing the build-dependen With .B ,ignores or -.BR -wci , +.BR \-wci , untracked files covered by .gitignore are tolerated, so only files which show up as .B ? @@ -576,7 +576,7 @@ in git status (ie, ones you maybe forgot to git add) are treated as a problem. .TP -.BR --clean=none " | " -wn +.BR \-\-clean=none " | " \-wn Do not clean the tree, nor check that it is clean. Avoids running rules clean, and can avoid needing the build-dependencies. @@ -584,22 +584,22 @@ If there are files which are not in git, or if the build creates such files, a subsequent dgit push will fail. .TP -.BR --clean=dpkg-source "[" -d "] | " -wd " | " -wdd +.BR \-\-clean=dpkg-source "[" \-d "] | " \-wd " | " \-wdd Use dpkg-buildpackage to do the clean, so that the source package is cleaned by dpkg-source running the package's clean target. ---clean=dpkg-source is the default. +\-\-clean=dpkg-source is the default. Without the extra .BR d , requires the package's build dependencies. With -.BR ... -d +.BR ... \-d or -.BR -wdd , +.BR \-wdd , the build-dependencies are not checked (due to passing -.B -d +.B \-d to dpkg-buildpackage), which violates policy, but may work in practice. @@ -607,7 +607,7 @@ The rules clean target will only be run when dgit is going to build source or binary packages from your working tree, rather than from your git branch -(for example because of --include-dirty +(for example because of \-\-include-dirty or because the binary package build uses your working tree). In all cases, @@ -618,24 +618,24 @@ in case these are files you forgot to gi for a `3.0 (quilt)' package when dgit has to apply patches, dirtily, to the working tree.) If your package does not have a good .gitignore -you will probably need --clean=dpkg-source,no-check aka -wdn. +you will probably need \-\-clean=dpkg-source,no-check aka \-wdn. .TP -.BR --clean=dpkg-source "[" -d "]" ,no-check " | " -wdn " | " -wddn -Like --clean=dpkg-source, but +.BR \-\-clean=dpkg-source "[" -d "]" ,no-check " | " \-wdn " | " \-wddn +Like \-\-clean=dpkg-source, but does not care about untracked un-ignored files. .TP -.BR --clean=dpkg-source "[" -d "]" ,all-check " | " -wda " | " -wdda -Like --clean=dpkg-source, but +.BR \-\-clean=dpkg-source "[" -d "]" ,all-check " | " \-wda " | " \-wdda +Like \-\-clean=dpkg-source, but fails even on ignored untracked files. This could perhaps be used to detect bugs in your rules clean target. .TP -.BR -N " | " --new +.BR \-N " | " \-\-new The package is or may be new in this suite. Without this, dgit will 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 -.B --include-dirty +.B \-\-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. @@ -643,10 +643,10 @@ This can be useful with build, if you pl 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 -.B --ignore-dirty -Deprecated alias for --include-dirty. +.B \-\-ignore-dirty +Deprecated alias for \-\-include-dirty. .TP -.BR --overwrite [=\fIprevious-version\fR] +.BR \-\-overwrite [=\fIprevious-version\fR] Declare that your HEAD really does contain all the (wanted) changes from all versions listed in its changelog; @@ -661,7 +661,7 @@ It is safer not to specify .IR previous-version , and usually it's not needed. Just say -.BR --overwrite , +.BR \-\-overwrite , unless you know what you are doing. This option is useful if you are the maintainer, and you have @@ -681,17 +681,17 @@ specified, dgit will check that the vers mentioned in your debian/changelog. (This will avoid losing changes, even with -.BR --overwrite , +.BR \-\-overwrite , unless someone committed to git a finalised changelog entry, and then made later changes to that version.) If .I previous-version is specified, it ought to be the version currently in the archive. -dgit push --overwrite +dgit push \-\-overwrite will, if necessary, make a pseudo-merge (that is, something that looks like the result -of git merge -s ours) to stitch the archive's version into your own +of git merge \-s ours) to stitch the archive's version into your own git history, so that your push is a fast forward from the archive. (In quilt mode @@ -699,7 +699,7 @@ git history, so that your push is a fast implying a split between the dgit view and the maintainer view, the pseudo-merge will appear only in the dgit view.) .TP -.BR --delayed =\fIdays\fR +.BR \-\-delayed =\fIdays\fR Upload to a DELAYED queue. .B WARNING: @@ -717,7 +717,7 @@ someone should make a suitable dgit push to update the contents of dgit-repos to a version without the controversial changes. .TP -.B --no-chase-dsc-distro +.B \-\-no-chase-dsc-distro Tells dgit not to look online for additional git repositories containing information about a particular .dsc being imported. @@ -741,7 +741,7 @@ Also, it can mean that dgit fails to find necessary git commits. .TP -.BR --save-dgit-view= \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) @@ -754,24 +754,24 @@ so don't specify a branch you want to ke This option is effective only with the following operations: quilt-fixup; push; all builds. And it is only effective with ---[quilt=]gbp, ---[quilt=]dpm, ---quilt=unpatched. +\-\-[quilt=]gbp, +\-\-[quilt=]dpm, +\-\-quilt=unpatched. If ref does not start with refs/ it is taken to be a branch - i.e. refs/heads/ is prepended. -.B --dgit-view-save +.B \-\-dgit-view-save is a deprecated alias for ---save-dgit-view. +\-\-save-dgit-view. .TP -.BI --deliberately- something +.BI \-\-deliberately- something Declare that you are deliberately doing .IR something . This can be used to override safety catches, including safety catches which relate to distro-specific policies. -The use of --deliberately is declared and published in the signed tags +The use of \-\-deliberately is declared and published in the signed tags generated for you by dgit, so that the archive software can give effect to your intent, and @@ -780,7 +780,7 @@ The meanings of .IR something s understood in the context of Debian are discussed below: .TP -.B --deliberately-not-fast-forward +.B \-\-deliberately-not-fast-forward Declare that you are deliberately rewinding history. When pushing to Debian, use this when you are making a renewed upload of an entirely new source package whose previous version was not accepted for release @@ -790,14 +790,14 @@ In split view quilt modes, this also prevents the construction by dgit of a pseudomerge to make the dgit view fast forwarding. Normally only one of ---overwrite (which creates a suitable pseudomerge) +\-\-overwrite (which creates a suitable pseudomerge) and ---deliberately-not-fast-forward +\-\-deliberately-not-fast-forward (which suppresses the pseudomerge and the fast forward checks) should be needed; ---overwrite is usually better. +\-\-overwrite is usually better. .TP -.B --deliberately-include-questionable-history +.B \-\-deliberately-include-questionable-history Declare that you are deliberately including, in the git history of your current push, history which contains a previously-submitted version of this package which was not approved (or has not yet been @@ -806,12 +806,12 @@ option after verifying that: none of the never-accepted) versions in the git history of your current push, were rejected by ftpmaster for copyright or redistributability reasons. .TP -.B --deliberately-fresh-repo +.B \-\-deliberately-fresh-repo Declare that you are deliberately rewinding history and want to throw away the existing repo. Not relevant when pushing to Debian, as the Debian server will do this automatically when necessary. .TP -.B --quilt=linear +.B \-\-quilt=linear When fixing up source format `3.0 (quilt)' metadata, insist on generating a linear patch stack: one new patch for each relevant commit. @@ -823,16 +823,16 @@ HEAD should be a series of plain commits and pseudomerges, with as ancestor a patches-applied branch. .TP -.B --quilt=auto +.B \-\-quilt=auto When fixing up source format `3.0 (quilt)' metadata, prefer to generate a linear patch stack -(as with --quilt=auto) +(as with \-\-quilt=auto) but if that doesn't seem possible, try to generate a single squashed patch for all the changes made in git -(as with --quilt=smash). +(as with \-\-quilt=smash). This is not a good idea for an NMU in Debian. .TP -.B --quilt=smash +.B \-\-quilt=smash When fixing up source format `3.0 (quilt)' metadata, generate a single additional patch for all the changes made in git. This is not a good idea for an NMU in Debian. @@ -843,48 +843,48 @@ if you do not change the upstream versio nor make changes in debian/patches, it will remain true.) .TP -.B --quilt=nofix +.B \-\-quilt=nofix Check whether source format `3.0 (quilt)' metadata would need fixing up, but, if it does, fail. You must then fix the metadata yourself -somehow before pushing. (NB that dpkg-source --commit will not work +somehow before pushing. (NB that dpkg-source \-\-commit will not work because the dgit git tree does not have a .B .pc directory.) .TP -.BR --quilt=nocheck " | " --no-quilt-fixup +.BR \-\-quilt=nocheck " | " \-\-no-quilt-fixup Do not check whether up source format `3.0 (quilt)' metadata needs fixing up. If you use this option and the metadata did in fact need fixing up, dgit push will fail. .TP -.BR -- [ quilt= ] gbp " | " -- [ quilt= ] dpm " | " --quilt=unapplied +.BR \-\- [ quilt= ] gbp " | " \-\- [ quilt= ] dpm " | " \-\-quilt=unapplied Tell dgit that you are using a nearly-dgit-compatible git branch, aka a .BR "maintainer view" , and do not want your branch changed by dgit. -.B --gbp +.B \-\-gbp (short for -.BR --quilt=gbp ) +.BR \-\-quilt=gbp ) is for use with git-buildpackage. Your HEAD is expected to be a patches-unapplied git branch, except that it might contain changes to upstream .gitignore files. This is the default for dgit gbp-build. -.B --dpm +.B \-\-dpm (short for -.BR --quilt=dpm ) +.BR \-\-quilt=dpm ) is for use with git-dpm. Your HEAD is expected to be a patches-applied git branch, except that it might contain changes to upstream .gitignore files. -.B --quilt=unapplied +.B \-\-quilt=unapplied specifies that your HEAD is a patches-unapplied git branch (and that any changes to upstream .gitignore files are represented as patches in debian/patches). -With --quilt=gbp|dpm|unapplied, +With \-\-quilt=gbp|dpm|unapplied, dgit push (or precursors like quilt-fixup and build) will automatically generate a conversion of your git branch into the right form. dgit push will push the @@ -902,16 +902,16 @@ for the dgit view. dgit quilt-fixup will merely do some checks, and cache the maintainer view. -.B If you have a branch like this it is essential to specify the appropriate --quilt= option! +.B If you have a branch like this it is essential to specify the appropriate \-\-quilt= option! This is because it is not always possible to tell: a patches-unapplied git branch of a package with one patch, for example, looks very like a patches-applied branch where the user has used git revert to undo the patch, expecting to actually revert it. However, if you fail to specify the right \-\-quilt option, and you aren't too lucky, dgit will notice the problem and stop, -with a useful hint. +with a useful hint. .TP -.BR -d "\fIdistro\fR | " --distro= \fIdistro\fR +.BR \-d "\fIdistro\fR | " \-\-distro= \fIdistro\fR Specifies that the suite to be operated on is part of distro .IR distro . This overrides the default value found from the git config option @@ -923,7 +923,7 @@ for accessing the archive and dgit-repos If your suite is part of a distro that dgit already knows about, you can use this option to make dgit work even if your dgit doesn't know about the suite. For example, specifying -.B -ddebian +.B \-ddebian will work when the suite is an unknown suite in the Debian archive. To define a new distro it is necessary to define methods and URLs @@ -931,7 +931,7 @@ for fetching (and, for dgit push, alteri in the archive and in dgit-repos. How to set this up is not yet documented. .TP -.BI -C changesfile +.BI \-C changesfile Specifies the .changes file which is to be uploaded. By default dgit push looks for single .changes file in the parent directory whose filename suggests it is for the right package and version. @@ -940,12 +940,12 @@ If the specified .I changesfile pathname contains slashes, the directory part is also used as the value for -.BR --build-products-dir ; +.BR \-\-build-products-dir ; otherwise, the changes file is expected in that directory (by default, in .BR .. ). .TP -.B --rm-old-changes +.B \-\-rm-old-changes When doing a build, delete any changes files matching .IB package _ version _*.changes before starting. This ensures that @@ -960,7 +960,7 @@ or the .rm-old-changes configuration set Note that \fBdgit push-source\fR will always find the right .changes, regardless of this option. .TP -.BI --build-products-dir= directory +.BI \-\-build-products-dir= directory Specifies where to find and create tarballs, binary packages, source packages, .changes files, and so on. @@ -976,38 +976,38 @@ configuration setting (see CONFIGURATION, below) which this command line option overrides). .TP -.B --no-rm-on-error +.B \-\-no-rm-on-error Do not delete the destination directory if clone fails. .TP -.B --dep14tag +.B \-\-dep14tag Generates a DEP-14 tag (eg .BR debian/ \fIversion\fR) as well as a dgit tag (eg .BR archive/debian/ \fIversion\fR) where possible. This is the default. .TP -.B --no-dep14tag +.B \-\-no-dep14tag Do not generate a DEP-14 tag, except in split quilt view mode. (On servers where only the old tag format is supported, the dgit tag will have the DEP-14 name. This option does not prevent that.) .TP -.B --dep14tag-always +.B \-\-dep14tag-always Insist on generating a DEP-14 tag as well as a dgit tag. If the server does not support that, dgit push will fail. .TP -.B -D +.B \-D Prints debugging information to stderr. Repeating the option produces -more output (currently, up to -DDDD is meaningfully different). +more output (currently, up to \-DDDD is meaningfully different). .TP -.BI -c name = value +.BI \-c name = value Specifies a git configuration option, to be used for this run. dgit itself is also controlled by git configuration options. .TP -.RI \fB-v\fR version "|\fB_\fR | " \fB--since-version=\fR version |\fB_\fR +.RI \fB\-v\fR version "|\fB_\fR | " \fB\-\-since-version=\fR version |\fB_\fR Specifies the -.BI -v version +.BI \-v version option to pass to dpkg-genchanges, during builds. Changes (from debian/changelog) since this version will be included in the built changes file, and hence in the upload. If this option is not @@ -1016,27 +1016,27 @@ uploaded to the intended suite. Specifying .B _ -inhibits this, so that no -v option will be passed to dpkg-genchanges +inhibits this, so that no \-v option will be passed to dpkg-genchanges (and as a result, only the last stanza from debian/changelog will be used for the build and upload). .TP -.RI \fB-m\fR maintaineraddress +.RI \fB\-m\fR maintaineraddress Passed to dpkg-genchanges (eventually). .TP -.RI \fB--ch:\fR option +.RI \fB\-\-ch:\fR option Specifies a single additional option to pass, eventually, to dpkg-genchanges. Options which are safe to pass include -.B -C +.B \-C (and also -.B -si -sa -sd +.B \-si \-sa \-sd although these should never be necessary with Debian since dgit automatically calculates whether .origs need to be uploaded.) For other options the caveat below applies. .TP -.RI \fB--curl:\fR option " | \fB--dput:\fR" option " |..." +.RI \fB\-\-curl:\fR option " | \fB\-\-dput:\fR" option " |..." Specifies a single additional option to pass to .BR curl , .BR dput , @@ -1069,26 +1069,26 @@ and cause lossage. For dpkg-buildpackage, dpkg-genchanges, mergechanges and sbuild, the option applies only when the program is invoked directly by dgit. Usually, for passing options to dpkg-genchanges, you should use -.BR --ch: \fIoption\fR. +.BR \-\-ch: \fIoption\fR. -Specifying --git is not effective for some lower-level read-only git +Specifying \-\-git is not effective for some lower-level read-only git operations performed by dgit, and also not when git is invoked by another program run by dgit. See notes below regarding ssh and dgit. -NB that --gpg:option is not supported (because debsign does not +NB that \-\-gpg:option is not supported (because debsign does not have that facility). But see -.B -k +.B \-k and the .B keyid distro config setting. .TP -.RI \fB--curl!:\fR option " | \fB--dput!:\fR" option " |..." +.RI \fB\-\-curl!:\fR option " | \fB\-\-dput!:\fR" option " |..." Specifies an option to remove from the command line for a program called by dgit, as for -\fB--\fR\fIprogram\fI\fB:\fR\fIoption\fR +\fB\-\-\fR\fIprogram\fI\fB:\fR\fIoption\fR (and the same caveats apply). Any options or arguments exactly identical to @@ -1099,11 +1099,11 @@ are removed. This can only be used to delete options which are always passed by default by dgit, or to undo a previous -\fB--\fR\fIprogram\fI\fB:\fR\fIoption\fR. +\fB\-\-\fR\fIprogram\fI\fB:\fR\fIoption\fR. It cannot be used to override option(s) dynamically decided on by dgit. .TP -.RI \fB--curl=\fR program " | \fB--dput=\fR" program " |..." +.RI \fB\-\-curl=\fR program " | \fB\-\-dput=\fR" program " |..." Specifies alternative programs to use instead of .BR curl , .BR dput , @@ -1138,8 +1138,8 @@ For .BR dgit , specifies the command to run on the remote host when dgit rpush needs to invoke a remote copy of itself. (dgit also reinvokes -itself as the EDITOR for dpkg-source --commit; this is done using -argv[0], and is not affected by --dgit=). +itself as the EDITOR for dpkg-source \-\-commit; this is done using +argv[0], and is not affected by \-\-dgit=). .BR gbp-build 's value @@ -1153,9 +1153,9 @@ unusually, the specified value is split to produce a command and possibly some options and/or arguments. For pbuilder and cowbuilder, the defaults are -.B sudo -E pbuilder +.B sudo \-E pbuilder and -.B sudo -E cowbuilder +.B sudo \-E cowbuilder respectively. Like with gbp-build and gbp pq, the specified value is split on whitespace. @@ -1172,25 +1172,25 @@ git config variables .BI dgit-distro. distro .ssh and .B .dgit.default.ssh -(which can in turn be overridden with -c). Also, when dgit is using +(which can in turn be overridden with \-c). Also, when dgit is using git to access dgit-repos, only git's idea of what ssh to use (eg, .BR GIT_SSH ) is relevant. .TP -.BI --existing-package= package +.BI \-\-existing-package= package dgit push needs to canonicalise the suite name. Sometimes, dgit lacks a way to ask the archive to do this without knowing the -name of an existing package. Without --new we can just use the -package we are trying to push. But with --new that will not work, so +name of an existing package. Without \-\-new we can just use the +package we are trying to push. But with \-\-new that will not work, so we guess .B dpkg or use the value of this option. This option is not needed with the default mechanisms for accessing the archive. .TP -.BR -h | --help +.BR \-h | \-\-help Print a usage summary. .TP -.BI --initiator-tempdir= directory +.BI \-\-initiator-tempdir= directory dgit rpush uses a temporary directory on the invoking (signing) host. This option causes dgit to use .I directory @@ -1199,7 +1199,7 @@ removed and recreated before dgit starts after dgit finishes. The directory specified must be an absolute pathname. .TP -.BI --force- something +.BI \-\-force- something Instructs dgit to try to proceed despite detecting what it thinks is going to be a fatal problem. .B This is probably not going to work. @@ -1207,45 +1207,45 @@ These options are provided as an escape in case dgit is confused. (They might also be useful for testing error cases.) .TP -.B --force-import-dsc-with-dgit-field +.B \-\-force-import-dsc-with-dgit-field Tell dgit import-dsc to treat a .dsc with a Dgit field like one without it. The result is a fresh import, discarding the git history that the person who pushed that .dsc was working with. .TP -.B --force-uploading-binaries +.B \-\-force-uploading-binaries Carry on and upload binaries even though dgit thinks your distro does not permit that. .TP -.B --force-uploading-source-only +.B \-\-force-uploading-source-only Carry on and do a source-only upload, without any binaries, even though dgit thinks your distro does not permit that, or does not permit that in this situation. .TP -.B --force-unrepresentable +.B \-\-force-unrepresentable Carry on even if dgit thinks that your git tree contains changes (relative to your .orig tarballs) which dpkg-source is not able to represent. Your build or push will probably fail later. .TP -.B --force-changes-origs-exactly +.B \-\-force-changes-origs-exactly Use the set of .origs specified in your .changes, exactly, without regard to what is in the archive already. The archive may well reject your upload. .TP -.B --force-unsupported-source-format +.B \-\-force-unsupported-source-format Carry on despite dgit not understanding your source package format. dgit will probably mishandle it. .TP -.B --force-dsc-changes-mismatch +.B \-\-force-dsc-changes-mismatch Do not check whether .dsc and .changes match. The archive will probably reject your upload. .TP -.BR --force-import-gitapply-absurd " | " --force-import-gitapply-no-absurd +.BR \-\-force-import-gitapply-absurd " | " \-\-force-import-gitapply-no-absurd Force on or off the use of the absurd git-apply emulation when running gbp pq import when importing a package from a .dsc. @@ -1254,14 +1254,14 @@ See Debian bug #841867. dgit can be configured via the git config system. You may set keys with git-config (either in system-global or per-tree configuration), or provide -.BI -c key = value +.BI \-c key = value on the dgit command line. .LP Settings likely to be useful for an end user include: .TP .B 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 +when \-\-build-products-dir is not specified. The default is the parent directory .RB ( .. ). .TP @@ -1285,8 +1285,8 @@ for each the default value used if there is no distro-specific setting. .TP .BR dgit-distro. \fIdistro\fR .clean-mode -One of the values for the command line --clean= option; used if ---clean is not specified. +One of the values for the command line \-\-clean= option; used if +\-\-clean is not specified. .TP .BR dgit-distro. \fIdistro\fR .clean-mode-newer Like .clean-mode, @@ -1295,8 +1295,8 @@ Setting both .clean-mode and .clean-mode to provide a single git config compatible with different dgit versions. .TP .BR dgit-distro. \fIdistro\fR .quilt-mode -One of the values for the command line --quilt= option; used if ---quilt is not specified. +One of the values for the command line \-\-quilt= option; used if +\-\-quilt is not specified. .TP .BR dgit-distro. \fIdistro\fR .rm-old-changes Boolean, used if neither \-\-rm-old-changes nor \-\-no-rm-old-changes @@ -1311,7 +1311,7 @@ git repository server. .TP .BI dgit-distro. distro .keyid See also -.BR -k . +.BR \-k . .TP .BI dgit-distro. distro .mirror " url" .TP @@ -1345,15 +1345,15 @@ True by default. Ignored for dgit setup Program to use instead of .IR cmd . Works like -.BR -- \fIcmd\fR = "... ." +.BR \-\- \fIcmd\fR = "... ." .TP .BI dgit-distro. distro .opts- cmd Extra options to pass to .IR cmd . Works like -.BR -- \fIcmd\fR : "... ." +.BR \-\- \fIcmd\fR : "... ." To pass several options, configure multiple values in git config -(with git config --add). The options for +(with git config \-\-add). The options for .BI dgit.default.opts- cmd .BI dgit-distro. distro /push.opts- cmd and are all used, followed by options from dgit's command line. @@ -1433,7 +1433,7 @@ if it contains any whitespace will be pa specifies just the program; no arguments can be specified, so dgit interprets it the same way as git does. See -also the --ssh= and --ssh: options. +also the \-\-ssh= and \-\-ssh: options. .TP .BR DEBEMAIL ", " DEBFULLNAME Default git user.email and user.name for new trees. See @@ -1462,10 +1462,10 @@ your current HEAD. Sadly this is necess (quilt)' source format. This is ultimately due to what I consider design problems in quilt and dpkg-source. ---dry-run does not always work properly, as not doing some of the git +\-\-dry-run does not always work properly, as not doing some of the git fetches may result in subsequent actions being different. Doing a non-dry-run dgit fetch first will help. ---damp-run is likely to work much better. +\-\-damp-run is likely to work much better. .SH SEE ALSO \fBdgit\fP(7), \fBdgit-*\fP(7), -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.144-1 (SMP w/2 CPU cores) Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages dgit depends on: ii apt 1.8.0~rc2 ii ca-certificates 20190110 ii coreutils 8.30-1 ii curl 7.63.0-1 ii devscripts 2.19.2 ii dpkg-dev 1.19.2 ii dput 1.0.3 ii git [git-core] 1:2.20.1-2 ii git-buildpackage 0.9.13 pn libdigest-sha-perl <none> ii libdpkg-perl 1.19.2 ii libjson-perl 4.01000-1 ii liblist-moreutils-perl 0.416-1+b4 ii liblocale-gettext-perl 1.07-3+b4 ii libtext-glob-perl 0.10-1 ii libtext-iconv-perl 1.7-5+b7 ii libwww-perl 6.36-1 ii perl 5.28.1-4 Versions of packages dgit recommends: ii openssh-client [ssh-client] 1:7.9p1-5 Versions of packages dgit suggests: pn sbuild | pbuilder | cowbuilder <none> -- no debconf information -- Bjarni I. Gislason
