Package: daptup
Version: 0.12.5.1
Severity: minor
Tags: patch
Dear Maintainer,
Found a typo in '/usr/share/man/man8/daptup.8.gz', see attached '.diff'.
Hope this helps...
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Versions of packages daptup depends on:
ii apt 0.9.7.7
ii cupt2.5.9
ii liblocale-gettext-perl 1.05-7+b1
ii perl5.14.2-16
daptup recommends no packages.
Versions of packages daptup suggests:
pn aptitude none
-- no debconf information
--- daptup.8 2012-08-25 06:26:08.0 -0400
+++ /tmp/daptup.8 2013-01-18 23:15:19.824141614 -0500
@@ -44,7 +44,7 @@
Starting with 0.8.0 version, \fBdaptup\fP uses apt hooks and you don't need to explicitly call it if you use 'apt-get update'.
.SH TROUBLESHOOTING
.PP
-If \fBdaptup\fP was interrupted while building the lists, the cached lists can stay in inconsistent state, which is inappropriate if you want to use \fB--last\fP option before the new update. There is nothing to do if interrupt was occured at the moment when old lists were building (besides running the new update). However, if interrupt was occured when the new lists were building, you can easily redo this stage by calling 'daptup \-\-post'.
+If \fBdaptup\fP was interrupted while building the lists, the cached lists can stay in inconsistent state, which is inappropriate if you want to use \fB--last\fP option before the new update. There is nothing to do if interrupt occurred at the moment when old lists were building (besides running the new update). However, if interrupt occurred when the new lists were building, you can easily redo this stage by calling 'daptup \-\-post'.
.SH FILES
.TP
.B /etc/daptup.conf
