[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2329: cp -r stops with an exception

[Tahoe-LAFS]

#2329: cp -r stops with an exception
-------------------------+-------------------------------------------------
     Reporter:  zooko    |      Owner:  warner
         Type:  defect   |     Status:  assigned
     Priority:  major    |  Milestone:  1.10.1
    Component:  code-    |    Version:  1.10.0
  frontend-cli           |   Keywords:  regression tahoe-cp review-needed
   Resolution:           |  release-blocker
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by warner):

 I've updated comment:35 to reflect that (the rule is that you must give -r
 to copy a directory, so a directory-like source without -r gives an
 error). I think our table is now up to date.

 Looking at the table, with an eye towards writing docs that explain what
 has changed, the new "cp -r PARENTCAP/dir local/missing" case (F2, bottom
 row) stands out. It's consistent with current trunk, but not with 1.10, or
 the proposed behavior for other directory-like sources, or with bin/cp.
 It'd be easier to explain if it were `local/missing/file` instead. I'm
 sure we've discussed this to death.. I've been too busy figuring out how
 to format that table. I'll reread the ticket and re-understand the
 rationale for that one.

 Next steps:

 * try to make the code implement the table
 * put an edited form of the table into NEWS, to explain the user-visible
 change
 * put a smaller form (just bin/cp and current behavior) into cli.rst
 * put an even smaller form (just current behavior, maybe as prose) into
 the tahoe-cp `--help` docstring

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2329#comment:38>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage