[tahoe-dev] [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:  davidsarah          |           Owner:       
     Type:  defect              |          Status:  new  
 Priority:  major               |       Milestone:  1.9.0
Component:  code-frontend-cli   |         Version:  1.8.1
 Keywords:  tahoe-cp usability  |   Launchpad Bug:       
--------------------------------+-------------------------------------------
 When {{{tahoe cp}}} copies onto an existing mutable file (in a writable
 directory), it replaces the directory entry. This is not consistent with
 SFTP, which would replace the contents of the file. Replacing the contents
 is more similar to a conventional filesystem, and I think more likely to
 be expected by users who are using mutable files.

 Notice that !TahoeFileTarget in
 [source:src/allmydata/scripts/tahoe_cp.py at 4768#L184] never uses the
 {{{mutable}}} variable passed into its constructor.

 Although the comment there mentions #835, this is not the same bug. #835
 is about adding options to allow specifying whether ''directories'' are
 copied as mutable or immuutable.

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