Re: RFS: qstardict
> 9:41 toots@leonard /tmp/qstardict-0.12.9%
> lintian -viI ../qstardict_0.12.9-1_amd64.changes
> N: Setting up lab in /tmp/VPmlOOVWRA ...
> N: Processing changes file qstardict_0.12.9-1_amd64.changes ...
> N: Processing 2 packages...
> N: ----
> N: Processing source package qstardict (version 0.12.9-1) ...
> I: qstardict source: debian-watch-file-is-missing
> N:
> N: This source package is not Debian-native but it does not have a
> N: debian/watch file. This file is used for automatic detection of new
> N: upstream versions by the Debian External Health Status project and
> N: other project infrastructure. If this package is maintained upstream,
> N: please consider adding a debian/watch file to detect new releases. If
> N: the package is not maintained upstream, consider adding a debian/watch
> N: file containing only comments to document this.
> N:
> N: Refer to Policy Manual, section 4.11 and the uscan(1) manual page for
> N: details.
> N:
> N: ----
> N: Processing binary package qstardict (version 0.12.9-1) ...
> W: qstardict: manpage-has-errors-from-man usr/share/man/man1/qstardict.1.gz
> 18: warning: `..' not defined
> N:
> N: This man page provokes warnings or errors from man.
> N:
> N: "cannot adjust" or "can't break" are trouble with paragraph filling,
> N: usually related to long lines. Adjustment can be helped by left
> N: justifying, breaks can be helped with hyphenation, see "Manipulating
> N: Filling and Adjusting" and "Manipulating Hyphenation" in the manual.
> N:
> N: "can't find numbered character" usually means latin1 etc in the input,
> N: and this warning indicates characters will be missing from the output.
> N: You can change to escapes like \[:a] described on the groff_char man
> N: page.
> N:
> N: Other warnings are often formatting typos, like missing quotes around
> N: a string argument to .IP. These are likely to result in lost or
> N: malformed output. See the groff_man (or groff_mdoc if using mdoc) man
> N: page for information on macros.
> N:
> N: This test uses man's --warnings option to enable groff warnings that
> N: catch common mistakes, such as putting . or ' characters at the start
> N: of a line when they are intended as literal text rather than groff
> N: commands. This can be fixed either by reformatting the paragraph so
> N: that these characters are not at the start of a line, or by adding a
> N: zero-width space (\&) immediately before them.
> N:
> N: At worst, warning messages can be disabled with the .warn directive,
> N: see "Debugging" in the groff manual.
> N:
> N: Removing /tmp/VPmlOOVWRA ...
This errors are fixed.
King regards
Alexander Rodin
Reply to: