Your message dated Thu, 03 Jun 2010 08:23:30 -0400
with message-id <[email protected]>
and subject line Re: Bug#584418: rm: documentation not included
has caused the Debian Bug report #584418,
regarding rm: documentation not included
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.)


-- 
584418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584418
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: coreutils
Version: 6.10-6
Severity: normal


The rm man page says to look for full documentation in texinfo format
but the texinfo documentation gives the man page again.

mv has obviously options not documented on the man page.


-- System Information:
Debian Release: squeeze/sid
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages coreutils depends on:
ii  libacl1                       2.2.47-2   Access control list shared library
ii  libc6                         2.11.1-1   Embedded GNU C Library: Shared lib
ii  libselinux1                   2.0.65-5   SELinux shared libraries

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
On Thu, Jun 03, 2010 at 02:17:37PM +0200, Michal Suchanek wrote:
The rm man page says to look for full documentation in texinfo format
but the texinfo documentation gives the man page again.

run "info coreutils"

Mike Stone


--- End Message ---

Reply via email to