[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                                                   
   Resolution:                     |    Keywords:  tahoe-cp preservation availability rebalancing usability
Launchpad Bug:                     |  
-----------------------------------+----------------------------------------

Comment (by davidsarah):

 Hmm, the encoding parameters of the existing file can be obtained from its
 URI, but how does {{{tahoe cp}}} know the current encoding parameters? It
 can't get them from {{{tahoe.cfg}}}, because its code directory may just
 have a {{{node.url}}} and no {{{tahoe.cfg}}}. Uploading a small file (just
 larger than the LIT threshold) and looking at the resulting URI would do
 it, but that's inefficient.

 We may need a new web-API operation to get the encoding parameters.

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