Bug#712701: devscript: manpage roff errors
Julian Gilbey
jdg at debian.org
Tue Jun 18 17:01:50 UTC 2013
Package: devscripts
Version: 2.13.2
Severity: minor
Tags: patch
Two messages from esr, with patches.
----- Forwarded message from esr at thyrsus.com -----
Date: Tue, 18 Jun 2013 01:14:00 -0400 (EDT)
From: esr at thyrsus.com
Subject: Problems in uscan.1
To: Julian Gilbey <jdg at debian.org>
This is automatically generated email about markup problems in a man
page for which you appear to be responsible. If you are not the right
person or list, please tell me so I can correct my database.
See http://catb.org/~esr/doclifter/bugs.html for details on how and
why these patches were generated. Feel free to email me with any
questions. Note: These patches do not change the modification date of
any manual page. You may wish to do that by hand.
I apologize if this message seems spammy or impersonal. The volume of
markup bugs I am tracking is over five hundred - there is no real
alternative to generating bugmail from a database and template.
--
Eric S. Raymond
Problems with uscan.1:
Ambiguous or invalid backslash. This doesn't cause groff a problem.
but it confuses doclifter and may confuse older troff implementations.
--- uscan.1-unpatched 2013-05-26 05:52:13.143350607 -0400
+++ uscan.1 2013-05-26 05:52:31.611350261 -0400
@@ -31,19 +31,19 @@
# format version number, currently 3; this line is compulsory!
version=3
-# Line continuations are performed with \fB\\\fR
+# Line continuations are performed with \fB\e\fR
# This is the format for an FTP site:
# Full-site-with-pattern [Version [Action]]
-ftp://ftp.tex.ac.uk/tex-archive/web/c_cpp/cweb/cweb-(.+)\\.tar\\.gz \\
+ftp://ftp.tex.ac.uk/tex-archive/web/c_cpp/cweb/cweb-(.+)\e.tar\e.gz \e
debian uupdate
# This is the format for an FTP site with regex special characters in
# the filename part
-ftp://ftp.worldforge.org/pub/worldforge/libs/Atlas-C++/transitional/Atlas-C\\+\\+-(.+)\\.tar\\.gz
+ftp://ftp.worldforge.org/pub/worldforge/libs/Atlas-C++/transitional/Atlas-C\e+\e+-(.+)\e.tar\e.gz
# This is the format for an FTP site with directory pattern matching
-ftp://ftp.nessus.org/pub/nessus/nessus-([\\d\\.]+)/src/nessus-core-([\\d\\.]+)\\.tar\\.gz
+ftp://ftp.nessus.org/pub/nessus/nessus-([\ed\e.]+)/src/nessus-core-([\ed\e.]+)\e.tar\e.gz
# This can be used if you want to override the PASV setting
# for a specific site
@@ -53,73 +53,73 @@
# as the FTP format. \fBuscan\fR starts by downloading the homepage,
# obtained by removing the last component of the URL; in this case,
# \fIhttp://www.cpan.org/modules/by-module/Text/\fR
-http://www.cpan.org/modules/by-module/Text/Text-CSV_XS-(.+)\\.tar\\.gz
+http://www.cpan.org/modules/by-module/Text/Text-CSV_XS-(.+)\e.tar\e.gz
# This is a variant HTTP format which allows direct specification of
# the homepage:
# Homepage Pattern [Version [Action]]
-http://www.dataway.ch/~lukasl/amph/amph.html \\
- files/amphetamine-([\\d\\.]*).tar.bz2
+http://www.dataway.ch/~lukasl/amph/amph.html \e
+ files/amphetamine-([\ed\e.]*).tar.bz2
# This one shows that recursive directory scanning works, in either of
# two forms, as long as the website can handle requests of the form
# \fIhttp://site/inter/mediate/dir/\fR
-http://tmrc.mit.edu/mirror/twisted/Twisted/(\\d\\.\\d)/ \\
- Twisted-([\\d\\.]*)\\.tar\\.bz2
-http://tmrc.mit.edu/mirror/twisted/Twisted/(\\d\\.\\d)/Twisted-([\\d\\.]*)\\.tar\\.bz2
+http://tmrc.mit.edu/mirror/twisted/Twisted/(\ed\e.\ed)/ \e
+ Twisted-([\ed\e.]*)\e.tar\e.bz2
+http://tmrc.mit.edu/mirror/twisted/Twisted/(\ed\e.\ed)/Twisted-([\ed\e.]*)\e.tar\e.bz2
# For maximum flexibility with upstream tarball formats, use this:
-http://example.com/example-(\d[\d\.]*)\\.(?:zip|tgz|tbz2|txz|tar\\.(?:gz|bz2|xz))
+http://example.com/example-(\ed[\ed\.]*)\e.(?:zip|tgz|tbz2|txz|tar\e.(?:gz|bz2|xz))
# qa.debian.org runs a redirector which allows a simpler form of URL
# for SourceForge based projects. The format below will automatically
# be rewritten to use the redirector.
-http://sf.net/audacity/audacity-src-(.+)\\.tar\\.gz
+http://sf.net/audacity/audacity-src-(.+)\e.tar\e.gz
# For GitHub projects you can use the tags page:
-https://github.com/<user>/<project>/tags .*/(\\d[\\d\\.]*)\\.tar\\.gz
+https://github.com/<user>/<project>/tags .*/(\ed[\ed\e.]*)\e.tar\e.gz
# For Google Code projects you should use the downloads page like this:
-http://code.google.com/p/<project>/downloads/list?can=1 \\
- .*/<project>-(\\d[\\d.]*)\\.tar\\.gz
+http://code.google.com/p/<project>/downloads/list?can=1 \e
+ .*/<project>-(\ed[\ed.]*)\e.tar\e.gz
# This is the format for a site which has funny version numbers;
# the parenthesised groups will be joined with dots to make a
# sanitised version number
-http://www.site.com/pub/foobar/foobar_v(\\d+)_(\\d+)\\.tar\\.gz
+http://www.site.com/pub/foobar/foobar_v(\ed+)_(\ed+)\e.tar\e.gz
# This is another way of handling site with funny version numbers,
# this time using mangling. (Note that multiple groups will be
# concatenated before mangling is performed, and that mangling will
# only be performed on the basename version number, not any path
# version numbers.)
-opts="uversionmangle=s/^/0.0./" \\
- ftp://ftp.ibiblio.org/pub/Linux/ALPHA/wine/development/Wine-(.+)\\.tar\\.gz
+opts="uversionmangle=s/^/0.0./" \e
+ ftp://ftp.ibiblio.org/pub/Linux/ALPHA/wine/development/Wine-(.+)\e.tar\e.gz
# Similarly, the upstream part of the Debian version number can be
# mangled:
-opts=dversionmangle=s/\\.dfsg\\.\\d+$// \\
- http://some.site.org/some/path/foobar-(.+)\\.tar\\.gz
+opts=dversionmangle=s/\e.dfsg\e.\ed+$// \e
+ http://some.site.org/some/path/foobar-(.+)\e.tar\e.gz
# The filename is found by taking the last component of the URL and
# removing everything after any '\fB?\fR'. If this would not make a usable
# filename, use filenamemangle. For example,
# <A href="http://foo.bar.org/download/?path=&download=foo-0.1.1.tar.gz">
# could be handled as:
-# opts=filenamemangle=s/.*=(.*)/$1/ \\
-# http://foo.bar.org/download/\\?path=&download=foo-(.+)\\.tar\\.gz
+# opts=filenamemangle=s/.*=(.*)/$1/ \e
+# http://foo.bar.org/download/\e?path=&download=foo-(.+)\e.tar\e.gz
#
# <A href="http://foo.bar.org/download/?path=&download_version=0.1.1">
# could be handled as:
-# opts=filenamemangle=s/.*=(.*)/foo-$1\\.tar\\.gz/ \\
-# http://foo.bar.org/download/\\?path=&download_version=(.+)
+# opts=filenamemangle=s/.*=(.*)/foo-$1\e.tar\e.gz/ \e
+# http://foo.bar.org/download/\e?path=&download_version=(.+)
# The option downloadurlmangle can be used to mangle the URL of the file
# to download. This can only be used with http:// URLs. This may be
# necessary if the link given on the web page needs to be transformed in
# some way into one which will work automatically, for example:
-# opts=downloadurlmangle=s/prdownload/download/ \\
-# http://developer.berlios.de/project/showfiles.php?group_id=2051 \\
+# opts=downloadurlmangle=s/prdownload/download/ \e
+# http://developer.berlios.de/project/showfiles.php?group_id=2051 \e
# http://prdownload.berlios.de/softdevice/vdr-softdevice-(.+).tgz
.fi
@@ -211,8 +211,8 @@
field. (Again, this pattern will be anchored at the beginning and the
end, so it must match the whole href. If you want to match just the
basename of the href, you can use a pattern like
-".*/name-(.+)\\.tar\\.gz" if you know that there is a full URL, or
-better still: "(?:.*/)?name-(.+)\\.tar\\.gz" if there may or may not
+".*/name-(.+)\e.tar\e.gz" if you know that there is a full URL, or
+better still: "(?:.*/)?name-(.+)\e.tar\e.gz" if there may or may not
be. Note the use of (?:...) to avoid making a backreference.) If any
of the hrefs in the homepage which match the (anchored) pattern are
relative URLs, they will be taken as being relative to the base URL of
@@ -253,13 +253,13 @@
If the '\fBs\fR' operation is used, the replacement can contain
backreferences to expressions within parenthesis in the matching regexp,
-like `\fBs/-alpha(\\d*)/.a$1/\fR'. These backreferences must use the
-`\fB$1\fR' syntax, as the `\fB\\1\fR' syntax is not supported.
+like `\fBs/-alpha(\ed*)/.a$1/\fR'. These backreferences must use the
+`\fB$1\fR' syntax, as the `\fB\e1\fR' syntax is not supported.
.TP
\fBdversionmangle=\fIrules\fR
This is used to mangle the Debian version number of the currently
installed package in the same way as the \fBuversionmangle\fR option.
-Thus, a suitable rule might be `\fBs/\\.dfsg\\.\\d+$//\fR' to remove a
+Thus, a suitable rule might be `\fBs/\e.dfsg\e.\ed+$//\fR' to remove a
`\fB.dfsg.1\fR' suffix from the Debian version number, or to handle `\fB.pre6\fR'
type version numbers. Again, the \fIrules\fR string may not contain
commas; this should not be a problem.
----- End forwarded message -----
----- Forwarded message from esr at thyrsus.com -----
Date: Tue, 18 Jun 2013 01:14:00 -0400 (EDT)
From: esr at thyrsus.com
Subject: Problems in rc-alert.1
To: Julian Gilbey <jdg at debian.org>
[...]
Problems with rc-alert.1:
Use local definitions of .EX/.EE or .DS/.DE to avoid low-level troff
requests in the page body. There are plans to add these to groff man;
in the interim, this patch adds a compatible definition to your page.
--- rc-alert.1-unpatched 2012-06-28 12:22:39.537252118 -0400
+++ rc-alert.1 2012-06-28 12:23:18.341251389 -0400
@@ -2,7 +2,7 @@
.SH NAME
rc-alert \- check for installed packages with release-critical bugs
.SH SYNOPSIS
-\fBrc\-alert\fR [\fIinclusion options\fR] [\fB\-\-debtags\fR [\fItag\fR[\fB,\fItag\fR ...]] [\fB\-\-popcon\fR] [\fIpackage\fR ...]
+\fBrc\-alert\fR [\fIinclusion options\fR] [\fB\-\-debtags\fR [\fItag\fR[\fB,\fItag\fR ...]]] [\fB\-\-popcon\fR] [\fIpackage\fR ...]
.br
\fBrc\-alert \-\-help\fR|\fB\-\-version\fR
.SH DESCRIPTION
----- End forwarded message -----
Julian
More information about the devscripts-devel
mailing list