trash-cli::trash-put man page claims to be `trash`

[Myk Melez]

In Ubuntu 12.04.1 LTS (Precise), the man page for the trash-put command from the trash-cli package (version 0.11.3~git20120324.fb57a8e-1) claims to be called trash:

--------------------------------------------------------------------------------
TRASH(1) TRASH(1)

NAME
       trash - Command line trash utility.

SYNOPSIS
       trash [arguments] ...

DESCRIPTION
       Trash-cli package provides a command line interface trashcan utility compliant with the FreeDesktop.org Trash Specification. It remembers
       the name, original path, deletion date, and permissions of each trashed file.

ARGUMENTS
       Names of files or directory to move in the trashcan.

EXAMPLES
       $ cd /home/andrea/
       $ touch foo bar
       $ trash foo bar
--------------------------------------------------------------------------------

Given that the name of the command is trash-put, and the name of the man page is trash-put, I would have expected the man page to describe the trash-put command. (Although I actually expected the package to provide a `trash` command, which I recall existing in previous versions of Ubuntu, and which is simpler to type.)

I know this is a relatively minor issue, and perhaps it is already fixed in Quantal, but keep in mind that Precise is an LTS release, so there are folks who will be running it for years. Thus it seems worth fixing this problem.

(See bug 1043854 for another trash-cli command name issue.)

[Stefano Karapetsas (stefano-karapetsas)]

I agree with you, but I maintain the package in Debian, so I have no power to fix the issue in Precise.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Andreas Moog (ampelbein)]

While I agree that this is a bug in precise, I do not think it warrants a stable release upgrade. It is a very minor annoyance and users who do use command line tools can be expected to not be bothered too much by it. Setting as "Fix released" due to the bug being fixed in later versions.