Your message dated Sat, 13 Oct 2012 11:51:24 +0200
with message-id <[email protected]>
and subject line README added
has caused the Debian Bug report #675881,
regarding grok: Please add a README to '/usr/share/doc/grok/examples'
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.)
--
675881: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675881
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grok
Version: 1.20110708.1-1
Severity: wishlist
Dear Maintainer,
Please consider adding a README to '/usr/share/doc/grok/examples' that
explains what the nine '.grok' files in that directory do, how to run
them, and what sort of output might result.
HTH...
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-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 grok depends on:
ii libc6 2.13-32
ii libevent-2.0-5 2.0.18-stable-1
ii libpcre3 1:8.30-5
ii libtokyocabinet9 1.4.47-2
grok recommends no packages.
grok suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.20110708.1-3
There is now a README.examples in /usr/share/doc/grok in the version
uploaded yesterday.
--
Stig Sandbeck Mathisen
--- End Message ---
