#2082 new defect

it says "option --node-dir not a unique prefix", but it is!

Reported by: zooko Owned by:
Priority: normal Milestone: soon
Component: code-frontend-cli Version: 1.10.0
Keywords: usability error cli twisted Cc:
Launchpad Bug:

Description

zooko@spark ~/tmp/tahoe-lafs.org/z/backup_of_klog $ tahoe cp --node-dir=~/.tahoe-basedirs/leastauthority-zookog_at_gmail.com/gateway/ blog.html $RWDIRCAP
Usage: tahoe cp [options] FROM.. TO
Options:
  -q, --quiet             Operate silently.
  -V, --version           Display version numbers.
      --version-and-path  Display version numbers and paths to their locations.
  -r, --recursive         Copy source directory recursively.
  -v, --verbose           Be noisy about what is happening.
      --caps-only         When copying to local files, write out filecaps
                          instead of actual data (only useful for debugging and
                          tree-comparison purposes).
  -d, --node-directory=   Specify which Tahoe node directory should be used. The
                          directory should either contain a full Tahoe node, or
                          a file named node.url that points to some other Tahoe
                          node. It should also contain a file named
                          'private/aliases' which contains the mapping from
                          alias name to root dirnode URI. [default:
                          '/home/zooko/.tahoe']
  -u, --node-url=         Specify the URL of the Tahoe gateway node, such as
                          'http://127.0.0.1:3456'. This overrides the URL found
                          in the --node-directory .
      --dir-cap=          Specify which dirnode URI should be used as the
                          'tahoe' alias.
      --help              Display this help and exit.

Use 'tahoe cp' to copy files between a local filesystem and a Tahoe grid. Any
FROM/TO arguments that begin with an alias indicate Tahoe-side files or non-file
arguments. Directories will be copied recursively. New Tahoe-side directories
will be created when necessary. Assuming that you have previously set up an
alias 'home' with 'tahoe create-alias home', here are some examples:

tahoe cp ~/foo.txt home: # creates tahoe-side home:foo.txt

tahoe cp ~/foo.txt /tmp/bar.txt home: # copies two files to home:

tahoe cp ~/Pictures home:stuff/my-pictures # copies directory recursively

You can also use a dircap as either FROM or TO target:

tahoe cp
URI:DIR2-RO:ixqhc4kdbjxc7o65xjnveoewym:5x6lwoxghrd5rxhwunzavft2qygfkt27oj3fbxlq4c6p45z5uneq/blog.html
./ # copy Zooko's wiki page to a local file

This command still has some limitations: symlinks and special files (device
nodes, named pipes) are not handled very well. Arguments should probably not
have trailing slashes. 'tahoe cp' does not behave as much like /bin/cp as you
would wish, especially with respect to trailing slashes.

/usr/bin/tahoe:  option --node-dir not a unique prefix

Change History (6)

comment:1 Changed at 2014-01-09T18:37:36Z by daira

  • Keywords twisted added

comment:2 Changed at 2015-05-11T14:14:31Z by daira

  • Milestone changed from undecided to 1.11.0

comment:3 Changed at 2016-03-22T05:02:52Z by warner

  • Milestone changed from 1.11.0 to 1.12.0

Milestone renamed

comment:4 Changed at 2016-06-28T18:20:37Z by warner

  • Milestone changed from 1.12.0 to 1.13.0

moving most tickets from 1.12 to 1.13 so we can release 1.12 with magic-folders

comment:5 Changed at 2020-06-30T14:45:13Z by exarkun

  • Milestone changed from 1.13.0 to 1.15.0

Moving open issues out of closed milestones.

comment:6 Changed at 2021-03-30T18:40:19Z by meejah

  • Milestone changed from 1.15.0 to soon

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.