path: root/dgit.1
diff options
authorSean Whitton <>2018-10-20 10:21:58 -0700
committerSean Whitton <>2018-10-20 10:21:58 -0700
commit4ea49240ddaa77bb4e290f9018727805ef87efc6 (patch)
treeecc5ef8ce55fa7cce83ebc9554edeb29920ea2cf /dgit.1
parentc1594eccda40a6a40bb2eb330a13578f330b3cc9 (diff)
parent16d99b2680f6c4e41c7740f542ca064455b4f5a4 (diff)
Merge tag 'debian/8.0' into stretch-bpo
dgit release 8.0 for unstable (sid) [dgit] [dgit distro=debian] # gpg: Signature made Sat 13 Oct 2018 04:01:49 PM MST # gpg: using RSA key 559AE46C2D6B6D3265E7CBA1E3E3392348B50D39 # gpg: Can't check signature: No public key
Diffstat (limited to 'dgit.1')
1 files changed, 75 insertions, 24 deletions
diff --git a/dgit.1 b/dgit.1
index 16c0a01..c3dd420 100644
--- a/dgit.1
+++ b/dgit.1
@@ -130,7 +130,7 @@ If you already have the suite branch,
and want to merge your branch with updates from the archive,
use dgit pull.
-dgit checkout will normally need to aceess the archive server,
+dgit checkout will normally need to access the archive server,
to canonicalise the provided suite name.
The exception is if you specify the canonical name,
and the branch (or tracking branch) already exists.
@@ -146,7 +146,7 @@ commit.
Tagging, signing and actually uploading should be left to dgit push.
-dgit's build operations access the the network,
+dgit's build operations access the network,
to get the -v option right.
See -v, below.
@@ -424,7 +424,7 @@ If this is a problem
consider --no-chase-dsc-distro
or --force-import-dsc-with-dgit-field.
-There is only only sub-option:
+There is only one sub-option:
.B --require-valid-signature
causes dgit to insist that the signature on the .dsc is valid
@@ -436,7 +436,7 @@ If
.I branch
is prefixed with
.B +
-then if it already exists, it will be simply ovewritten,
+then if it already exists, it will be simply overwritten,
no matter its existing contents.
.I branch
@@ -469,7 +469,7 @@ It may not be useable in a browser.
.BI "dgit print-dpkg-source-ignores"
Prints the -i and -I arguments which must be passed to dpkg-souce
-to cause it to exclude exactly the .git diredcory
+to cause it to exclude exactly the .git directory
and nothing else.
The separate arguments are unquoted, separated by spaces,
and do not contain spaces.
@@ -538,7 +538,12 @@ This will delete all files which are not tracked by git.
options other than dpkg-source
are useful when the package's clean target is troublesome, or
to avoid needing the build-dependencies.
+dgit will only actually clean the tree if it needs to
+(because it needs to build the source package
+or binaries from your working tree).
+Otherwise any untracked files will be simply ignored.
.BR --clean=git-ff " | " -wgf
.BR "git clean -xdff"
@@ -548,11 +553,22 @@ git clean -xdf
but it also removes any subdirectories containing different git
trees (which only unusual packages are likely to create).
-.BR --clean=check " | " -wc
+.BR --clean=check " | " --clean=check,ignores " | " -wc " | " -wci
Merely check that the tree is clean (does not contain uncommitted
Avoids running rules clean,
and can avoid needing the build-dependencies.
+.BR ,ignores
+.BR -wci ,
+untracked files covered by .gitignore are tolerated,
+so only files which show up as
+.B ?
+in git status
+(ie, ones you maybe forgot to git add)
+are treated as a problem.
.BR --clean=none " | " -wn
Do not clean the tree, nor check that it is clean.
@@ -562,21 +578,50 @@ If there are
files which are not in git, or if the build creates such files, a
subsequent dgit push will fail.
-.BR --clean=dpkg-source " | " -wd
+.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.
-This is the default.
-Requires the package's build dependencies.
-.BR --clean=dpkg-source-d " | " -wdd
-.B dpkg-buildpackage -d
-to do the clean,
-so that the source package
-is cleaned by dpkg-source running the package's clean target.
-The build-dependencies are not checked (due to
-.BR -d ),
+--clean=dpkg-source is the default.
+Without the extra
+.BR d ,
+requires the package's build dependencies.
+.BR ... -d
+.BR -wdd ,
+the build-dependencies are not checked
+(due to passing
+.BR -d
+to dpkg-buildpackage),
which violates policy, but may work in practice.
+The rules clean target will only be run if it is needed:
+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
+or because the binary package build uses your working tree).
+In all cases,
+dgit will check that there are (after rules clean, if applicable) no
+untracked un-ignored files,
+in case these are files you forgot to git add.
+(Except that this check is not done
+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.
+.BR --clean=dpkg-source "[" -d "]" ,no-check " | " -wdn " | " -wddn
+Like --clean=dpkg-source, but
+does not care about untracked un-ignored files.
+.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.
.BR -N " | " --new
The package is or may be new in this suite. Without this, dgit will
@@ -708,7 +753,7 @@ And it is only effective with
If ref does not start with refs/
-it is taken to to be a branch -
+it is taken to be a branch -
i.e. refs/heads/ is prepended.
.B --dgit-view-save
@@ -898,7 +943,7 @@ default, in
When doing a build, delete any changes files matching
.IB package _ version _*.changes
before starting. This ensures that
-dgit push (and dgit sbuild) will be able to unambigously
+dgit push (and dgit sbuild) will be able to unambiguously
identify the relevant changes files from the most recent build, even
if there have been previous builds with different tools or options.
The default is not to remove, but
@@ -910,7 +955,7 @@ Note that \fBdgit push-source\fR will always find the right .changes,
regardless of this option.
.BI --build-products-dir= directory
-Specifies where to find and create tarballs, binry packages,
+Specifies where to find and create tarballs, binary packages,
source packages, .changes files, and so on.
By default, dgit uses the parent directory
@@ -1219,7 +1264,13 @@ the default value used if there is no distro-specific setting.
One of the values for the command line --clean= option; used if
--clean is not specified.
-.BR dgit-distro. \fIdistro\fR .quilt-mode
+.BR dgit-distro. \fIdistro\fR .clean-mode-newer
+Like .clean-mode,
+but ignored if the value does not make sense to this version of dgit.
+Setting both .clean-mode and .clean-mode-newer is useful
+to provide a single git config compatible with different dgit versions.
+.BR dgit-distro. \fIdistro\fR .quilt-
One of the values for the command line --quilt= option; used if
--quilt is not specified.
@@ -1366,7 +1417,7 @@ Default git and for new trees. See
.BR gpg ", " dpkg- "..., " debsign ", " git ", " curl ", " dput ", " LWP::UserAgent
and other subprograms and modules used by dgit are affected by various
-environment variables. Consult the documentaton for those programs
+environment variables. Consult the documentation for those programs
for details.
There should be