[tahoe-lafs-trac-stream] [tahoe-lafs] #1373: 'tahoe cp' should not make links to existing immutable files when the encoding parameters have changed

[tahoe-lafs]

#1373: 'tahoe cp' should not make links to existing immutable files when the
encoding parameters have changed
----------------------------------------------------------------------+-----
 Reporter:  davidsarah                                                |           Owner:           
     Type:  defect                                                    |          Status:  new      
 Priority:  major                                                     |       Milestone:  undecided
Component:  code-frontend-cli                                         |         Version:  1.8.2    
 Keywords:  tahoe-cp preservation availability rebalancing usability  |   Launchpad Bug:           
----------------------------------------------------------------------+-----
 Whenever {{{tahoe cp}}} copies an existing Tahoe immutable file, it will
 link to the file rather than re-uploading it (see
 [source:src/allmydata/scripts/tahoe_cp.py at 4768#L170 the need_to_copy_bytes
 method of TahoeFileSource]). This is arguably the wrong behaviour when the
 current encoding parameters are not the same as those of the existing
 file.

 This makes it more difficult to rebalance a file by copying it (see [http
 ://tahoe-lafs.org/pipermail/tahoe-dev/2011-February/006192.html this
 tahoe-dev thread]).

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