[tahoe-lafs-trac-stream] [tahoe-lafs] #1304: 'tahoe cp' copying to a mutable file should replace the contents

[tahoe-lafs]

#1304: 'tahoe cp' copying to a mutable file should replace the contents
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  davidsarah
  davidsarah             |     Status:  new
         Type:  defect   |  Milestone:  1.9.0
     Priority:  major    |    Version:  1.8.1
    Component:  code-    |   Keywords:  tahoe-cp usability design-review-
  frontend-cli           |  needed
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Changes (by davidsarah):

 * owner:  kevan => davidsarah
 * status:  assigned => new


Comment:

 Replying to [comment:5 kevan]:
 > How do we want to behave when {{{tahoe cp}}}'s authority is inadequate
 to replace the contents of the target? I like failure in that case; I
 don't like the idea of falling back to directory modification from content
 replacement for mutable files, since they're pretty different behaviors.

 +1, that case should be an error.

 > I've attached a patch. I'll set 'review-needed' once we've decided what
 to do when the target mutable file isn't writable and I've written a test
 for that.

 I'll review what you have so far.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1304#comment:7>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage