Package: debhelper
Version: 4.2.34
Severity: minor
Tags: patch
Found some typos in '/usr/share/man/man7/debhelper.7.gz', see attached '.diff'.
Hope this helps...
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Versions of packages debhelper depends on:
ii binutils 2.15-5 The GNU assembler, linker and bina
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii debconf-utils 1.4.48 debconf utilities
ii dpkg-dev 1.10.27 Package building tools for Debian
ii file 4.12-1 Determines file type using "magic"
ii fileutils 5.2.1-2 The GNU file management utilities
ii html2text 1.3.2a-1 An advanced HTML to text converter
ii perl 5.8.4-8 Larry Wall's Practical Extraction
ii po-debconf 0.8.23 manage translated Debconf template
-- no debconf information
--- - 2005-04-22 05:53:07.474338000 -0400
+++ /tmp/debhelper7.gz.27660 2005-04-22 05:53:07.468440458 -0400
@@ -238,7 +238,7 @@
.IP dh_scrollkeeper(1)
generate ScrollKeeper registration scripts
.IP dh_shlibdeps(1)
-calculate shared library dependancies
+calculate shared library dependencies
.IP dh_strip(1)
strip executables, shared libraries, and some static libraries
.IP dh_suidregister(1)
@@ -429,21 +429,21 @@
From time to time, major non-backwards-compatible changes need to be made
to debhelper, to keep it clean and well-designed as needs change and its
author gains more experience. To prevent such major changes from breaking
-existing packages, the concept of debhelper compatability levels was
-introduced. You tell debhelper which compatability level it should use, and
+existing packages, the concept of debhelper compatibility levels was
+introduced. You tell debhelper which compatibility level it should use, and
it modifies its behavior in various ways.
.PP
-You tell debhelper what compatability level to use by writing a number to
+You tell debhelper what compatibility level to use by writing a number to
debian/compat. For example, to turn on V4 mode:
.PP
.Vb 1
\& % echo 4 > debian/compat
.Ve
.PP
-These are the available compatablity levels:
+These are the available compatibility levels:
.IP "V1" 4
.IX Item "V1"
-This is the original debhelper compatability level, and so it is the default
+This is the original debhelper compatibility level, and so it is the default
one. In this mode, debhelper will use debian/tmp as the package tree
directory for the first binary package listed in the control file, while using
debian/<package> for all other packages listed in the control file.
@@ -468,12 +468,12 @@
.RE
.IP "V4" 4
.IX Item "V4"
-This is the reccommended mode of operation. It does everything V3 does,
+This is the recommended mode of operation. It does everything V3 does,
plus:
.RS 4
.IP "\-" 8
dh_makeshlibs \-V will not include the debian part of the version number in
-the generated dependancy line in the shlibs file.
+the generated dependency line in the shlibs file.
.IP "\-" 8
You are encouraged to put the new ${misc:Depends} into debian/control to
supplement the ${shlibs:Depends} field.
@@ -513,9 +513,9 @@
.PP
Once your package uses debhelper to build, be sure to add
debhelper to your Build-Depends line in debian/control. You should
-build-depend on a verson of debhelper equal to (or greater than) the
-debhelper compatability level your package uses. So if your package used
-compatability level 4:
+build-depend on a version of debhelper equal to (or greater than) the
+debhelper compatibility level your package uses. So if your package used
+compatibility level 4:
.PP
.Vb 1
\& Build\-Depends: debhelper (>= 4)
