Package: devscripts
Version: 2.9.10
Severity: minor
Tags: patch

Found a few typos in '/usr/share/man/man1/uupdate.1.gz', see attached '.diff'.

Hope this helps...

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)

Versions of packages devscripts depends on:
ii  debianutils                   2.15.1     Miscellaneous utilities specific t
ii  dpkg-dev                      1.13.11    package building tools for Debian
ii  libc6                         2.3.5-8.1  GNU C Library: Shared libraries an
ii  perl                          5.8.7-8    Larry Wall's Practical Extraction 
ii  sed                           4.1.4-4    The GNU sed stream editor

Versions of packages devscripts recommends:
ii  fakeroot                      1.5.5      Gives a fake root environment

-- no debconf information
--- -   2005-12-06 02:51:14.281255000 -0500
+++ /tmp/uupdate1.gz.27934      2005-12-06 02:51:14.000000000 -0500
@@ -8,7 +8,7 @@
 .SH DESCRIPTION
 \fBuupdate\fR modifies an existing Debian source code archive to
 reflect an upstream update supplied as a patch or from a wholly new
-sourcecode archive.  The utility needs to be invoked from the top
+source code archive.  The utility needs to be invoked from the top
 directory of the old source code directory, and if a relative name is
 given for the new archive or patch file, it will be looked for first
 relative to the execution directory and then relative to the parent of
@@ -36,7 +36,7 @@
 \fBuscan\fR.)
 .PP
 Since \fBuupdate\fR uses \fBdebuild\fR to clean the current archive
-before trying to apply a patchfile, it accepts a \fB\-\-rootcmd\fR or
+before trying to apply a patch file, it accepts a \fB\-\-rootcmd\fR or
 \fB\-r\fR option allowing the user to specify a gain-root command to be
 used.  The default is to use \fBfakeroot\fR.
 .PP

Reply via email to