Package: apt-cacher
Version: 1.5.1
Severity: minor
Tags: patch

Found some typos in '/usr/share/man/man1/apt-cacher.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.15-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)

Versions of packages apt-cacher depends on:
ii  bzip2                         1.0.3-2    high-quality block-sorting file co
ii  libwww-perl                   5.803-4    WWW client/server library for Perl
ii  perl                          5.8.7-10   Larry Wall's Practical Extraction 

apt-cacher recommends no packages.

-- no debconf information
--- apt-cacher.1        2006-02-08 13:38:36.000000000 -0500
+++ /tmp/apt-cacher.1   2006-02-22 04:47:09.000000000 -0500
@@ -54,8 +54,8 @@
 with a HTTP proxy setting, see PROXY MODE USAGE below.
 .PP
 Apt\-cacher currently only handles forwarding to HTTP sources. Support for
-other access methods (ftp, rsync) is not planed because the maintainer
-believies that the outcome is not worth the efforts.
+other access methods (ftp, rsync) is not planned because the maintainer
+believes that the outcome is not worth the efforts.
 .SH INSTALLATION METHODS
 Apt\-cacher can be installed in various ways. The recommended is running the
 program as a stand-alone daemon. This should get the best performance and the
@@ -104,7 +104,7 @@
 MB, so make sure it is on a partition with plenty of room. NOTE: the cache
 directory needs to contain some subdirectories for correct storage management.
 If you try to create a custom directory, please use the script
-/usr/share/apt-cacher/install.pl or use the initialy created cache directory as
+/usr/share/apt-cacher/install.pl or use the initially created cache directory 
as
 example.
 .TP
 .B offline_mode [ 0 ]
@@ -218,7 +218,7 @@
 .SH PROXY MODE USAGE
 .PP
 As stated above apt-cacher can be reached with APT clients using two methods:
-modification of base URLs in sources.list so that the actuall apt-cacher server
+modification of base URLs in sources.list so that the actual apt-cacher server
 is connected instead of the original server (which still must be listed in the
 same URL unless an alias is used, see path_map option).
 Another method follows the HTTP proxy technology. The APT client can be
@@ -262,7 +262,7 @@
 .B Q: Does the daily generation of reports or cleaning the cache depend
 on whether apt-cacher is running continuously as a daemon?
 .PP
-A: No, the regular maintainence jobs are independent of a running server. They
+A: No, the regular maintenance jobs are independent of a running server. They
 are executed by cron and use only static data like logs and cached index files
 and package directory listing.
 However, apt-cacher should be configured correctly because cleanup runs it
@@ -280,7 +280,7 @@
 permitted; allowed_hosts=* and denied_hosts=<ip data>, then every host is
 accepted except of those matched by denied_hosts; allowed_hosts=<ip data> and
 denied_hosts=<ip data>, then only the clients from allowed_hosts are accepted
-except of those matched by denied_hosts. allowed_hosts=<empty> blocks 
everything. If allowed_hosts is omited, * is assumed.
+except of those matched by denied_hosts. allowed_hosts=<empty> blocks 
everything. If allowed_hosts is omitted, * is assumed.
 denied_hosts must not have an "*" value, use empty allowed_hosts setting if 
you want that.
 .PP
 .B Q: generate_reports: how does being able to view the reports depend on

Reply via email to