[tahoe-lafs-trac-stream] [tahoe-lafs] #2027: Inconsistent 'tahoe cp' Behavior

tahoe-lafs trac at tahoe-lafs.org
Wed Jul 17 16:15:16 UTC 2013


#2027: Inconsistent 'tahoe cp' Behavior
---------------------------+-----------------------------------------------
     Reporter:             |      Owner:  daira
  markberger               |     Status:  assigned
         Type:  defect     |  Milestone:  1.11.0
     Priority:  normal     |    Version:  1.10.0
    Component:  code-      |   Keywords:  usability error cli tahoe-cp easy
  frontend-cli             |
   Resolution:             |
Launchpad Bug:             |
---------------------------+-----------------------------------------------
Changes (by daira):

 * keywords:   => usability error cli tahoe-cp easy
 * owner:   => daira
 * status:  new => assigned


Old description:

> When copying a file from the top level of a directory node using the CLI,
> tahoe requires a file name to be specified.
>
> Ex: {{{tahoe cp tahoe:test.jpg ~}}} fails while {{{tahoe cp
> tahoe:test.jgp ~/test.jpg }}} succeeds.
>
> However, when a file is copied from a subdirectory to the local disk
> without a specified file name, the download will succeed.
>
> Ex: {{{tahoe cp tahoe:test/test.jgp ~}}} succeeds along with {{{tahoe cp
> tahoe:test/test.jgp ~/test.jpg}}}.
>
> The CLI's behavior should be consistent. Either require users to specify
> a file name for all cp actions or allow users to copy files from the top
> level of a directory  to a local directory without specifying a file
> name.

New description:

 When copying a file from the top level of a directory node using the CLI,
 tahoe requires a file name to be specified.

 Ex: {{{tahoe cp tahoe:test.jpg ~}}} fails while {{{tahoe cp tahoe:test.jpp
 ~/test.jpg }}} succeeds.

 However, when a file is copied from a subdirectory to the local disk
 without a specified file name, the download will succeed.

 Ex: {{{tahoe cp tahoe:test/test.jpg ~}}} succeeds along with {{{tahoe cp
 tahoe:test/test.jpg ~/test.jpg}}}.

 The CLI's behavior should be consistent. Either require users to specify a
 file name for all cp actions or allow users to copy files from the top
 level of a directory  to a local directory without specifying a file name.

--

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2027#comment:1>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage


More information about the tahoe-lafs-trac-stream mailing list