Package: dgit
Version: 8.3
Severity: minor
Tags: patch
Dear Maintainer,
>From b706387a72d95ae30652901f126f92be90699b28 Mon Sep 17 00:00:00 2001
>Date: Mon, 4 Feb 2019 02:30:04 +0000
Use a single-font-style macro (".B", ".I") for a single argument.
Remove unneeded quotation marks (").
The output from "nroff" and "groff" is unchanged with this patch.
[ There are still some typographical mistakes left. ]
Signed-off-by: Bjarni Ingi Gislason <bjarn...@rhi.hi.is>
---
dgit.1 | 64 +++++++++++++++++++++++++++++-----------------------------
1 file changed, 32 insertions(+), 32 deletions(-)
diff --git a/dgit.1 b/dgit.1
index 6f89574..f0d2a8f 100644
--- a/dgit.1
+++ b/dgit.1
@@ -462,12 +462,12 @@ Prints version information and exits.
Tries to fetch a copy of the source code for the dgit-repos-server,
as actually being used on the dgit git server, as a git tree.
.TP
-.BI "dgit print-dgit-repos-server-source-url"
+.B dgit print-dgit-repos-server-source-url
Prints the url used by dgit clone-dgit-repos-server.
This is hopefully suitable for use as a git remote url.
It may not be useable in a browser.
.TP
-.BI "dgit print-dpkg-source-ignores"
+.B 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 directory
and nothing else.
@@ -515,7 +515,7 @@ distro's
config setting (see CONFIGURATION, below), or failing that, the
uploader trailer line in debian/changelog.
.TP
-.BR --no-sign
+.B --no-sign
does not sign tags or uploads (meaningful only with push).
.TP
.TP
@@ -527,7 +527,7 @@ Valid with dgit fetch and dgit pull, only.
.TP
.BR --clean=git " | " -wg
Use
-.BR "git clean -xdf"
+.B git clean -xdf
to clean the working tree,
rather than running the package's rules clean target.
@@ -548,7 +548,7 @@ See --clean=git[-ff],always, below.
.TP
.BR --clean=git-ff " | " -wgf
Use
-.BR "git clean -xdff"
+.B git clean -xdff
to clean the working tree.
Like
git clean -xdf
@@ -566,7 +566,7 @@ Avoids running rules clean,
and can avoid needing the build-dependencies.
With
-.BR ,ignores
+.B ,ignores
or
.BR -wci ,
untracked files covered by .gitignore are tolerated,
@@ -599,7 +599,7 @@ or
.BR -wdd ,
the build-dependencies are not checked
(due to passing
-.BR -d
+.B -d
to dpkg-buildpackage),
which violates policy, but may work in practice.
@@ -635,7 +635,7 @@ 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 --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,7 +643,7 @@ 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
+.B --ignore-dirty
Deprecated alias for --include-dirty.
.TP
.BR --overwrite [=\fIprevious-version\fR]
@@ -685,7 +685,7 @@ changes, even with
unless someone committed to git a finalised changelog
entry, and then made later changes to that version.)
If
-.IR previous-version
+.I previous-version
is specified, it ought to be the version currently in the archive.
dgit push --overwrite
@@ -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
-.BR --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.
@@ -780,7 +780,7 @@ The meanings of
.IR something s
understood in the context of Debian are discussed below:
.TP
-.BR --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
@@ -797,7 +797,7 @@ and
should be needed;
--overwrite is usually better.
.TP
-.BR --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
rejected-from-NEW (or
never-accepted) versions in the git history of your current push, were
rejected by ftpmaster for copyright or redistributability reasons.
.TP
-.BR --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
-.BR --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,7 +823,7 @@ HEAD should be a series of plain commits
and pseudomerges,
with as ancestor a patches-applied branch.
.TP
-.BR --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)
@@ -832,7 +832,7 @@ try to generate a single squashed patch for all the changes
made in git
(as with --quilt=smash).
This is not a good idea for an NMU in Debian.
.TP
-.BR --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,7 +843,7 @@ if you do not change the upstream version
nor make changes in debian/patches,
it will remain true.)
.TP
-.BR --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
@@ -971,33 +971,33 @@ 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
+.B dgit.default.build-products-dir
configuration setting
(see CONFIGURATION, below)
which this command line option overrides).
.TP
-.BI --no-rm-on-error
+.B --no-rm-on-error
Do not delete the destination directory if clone fails.
.TP
-.BI --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
-.BI --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
-.BI --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
-.BI -D
+.B -D
Prints debugging information to stderr. Repeating the option produces
more output (currently, up to -DDDD is meaningfully different).
.TP
@@ -1028,9 +1028,9 @@ Specifies a single additional option to pass, eventually,
to
dpkg-genchanges.
Options which are safe to pass include
-.BR -C
+.B -C
(and also
-.BR "-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.)
@@ -1153,9 +1153,9 @@ 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"
+.B sudo -E pbuilder
and
-.BR "sudo -E cowbuilder"
+.B sudo -E cowbuilder
respectively.
Like with gbp-build and gbp pq,
the specified value is split on whitespace.
@@ -1259,7 +1259,7 @@ on the dgit command line.
.LP
Settings likely to be useful for an end user include:
.TP
-.BI dgit.default.build-products-dir
+.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
the parent directory
@@ -1415,13 +1415,13 @@ or when pushing and
.TP
.BR dgit-distro. \fIdistro\fR .source-only-uploads " " ok | always | never |
not-wholly-new
.TP
-.BI dgit.default.old-dsc-distro
+.B dgit.default.old-dsc-distro
.TP
.BI dgit.dsc-url-proto-ok. protocol
.TP
-.BI dgit.dsc-url-proto-ok.bad-syntax
+.B dgit.dsc-url-proto-ok.bad-syntax
.TP
-.BI dgit.default.dsc-url-proto-ok
+.B dgit.default.dsc-url-proto-ok
.TP
.BR dgit.vcs-git.suites " \fIsuite\fR[" ; ...]
.SH ENVIRONMENT VARIABLES
--
2.20.1
-- 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~beta1
ii ca-certificates 20170717
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-3
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
