Your message dated Mon, 21 Apr 2008 15:09:41 -0300
with message-id <[EMAIL PROTECTED]>
and subject line manual closing bug
has caused the Debian Bug report #422939,
regarding 'man sleepenh' typos: "Supose", "acurate" x 4, "successfull", &
"suplied"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
422939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422939
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: sleepenh
Version: 1.2-2.1
Severity: minor
Tags: patch
Found some typos in '/usr/share/man/man1/sleepenh.1.gz', see attached '.diff'.
Hope this helps...
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
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 sleepenh depends on:
ii libc6 2.5-7 GNU C Library: Shared libraries
sleepenh recommends no packages.
-- no debconf information
--- sleepenh.1 2006-07-17 18:58:36.000000000 -0400
+++ /tmp/sleepenh.1 2007-05-08 02:09:37.000000000 -0400
@@ -21,10 +21,10 @@
.SH DESCRIPTION
\fBsleepenh\fP is a program that can be used when there is a need
to execute some functions periodically in a shell script. It was
-not designed to be acurate for a single sleep, but to be
-acurate in a sequence of consecutive sleeps.
+not designed to be accurate for a single sleep, but to be
+accurate in a sequence of consecutive sleeps.
.br
-After a successfull execution, it returns to stdout the timestamp
+After a successful execution, it returns to stdout the timestamp
it finished running, that can be used as \fBinitial-time\fP to a
successive execution of \fBsleepenh\fP.
.SH OPTIONS
@@ -38,7 +38,7 @@
\fBinitial-time\fP is a real number in seconds, with microseconds
resolution. This number is system dependent. In GNU/Linux systems,
it is the number of seconds since midnight 1970-01-01 GMT. Do not
-try to get a good value of \fBinitial-time\fP. Use the value suplied
+try to get a good value of \fBinitial-time\fP. Use the value supplied
by a previous execution of \fBsleepenh\fP.
.br
If you don't specify \fBinitial-time\fP, it is assumed the current-time.
@@ -65,7 +65,7 @@
.B 13
Failure. System error, could not get current time.
.SH USAGE EXAMPLE
-Supose you need to send the char 'A' to the serial port ttyS0
+Suppose you need to send the char 'A' to the serial port ttyS0
every 4 seconds. This will do that:
.Sx
@@ -89,8 +89,8 @@
.TP
sleepenh 0
.SH BUGS
-It is not acurate for a single sleep. Short sleep-times will also not
-be acurate.
+It is not accurate for a single sleep. Short sleep-times will also not
+be accurate.
.SH SEE ALSO
.BR date (1),
.BR sleep (1).
--- End Message ---
--- Begin Message ---
Package: sleepenh
Version: 1.3-1
this bug was fixed in version 1.2-3, however I did not upload this
version. I uploaded 1.3-1 to sid, which also contains the fix. Please
see changelog.debian.gz for more info.
--- End Message ---
