[tahoe-lafs-trac-stream] [tahoe-lafs] #1385: stop respecting the pre-v1.3.0 configuration files

[tahoe-lafs]

#1385: stop respecting the pre-v1.3.0 configuration files
-------------------------+-------------------------------------------------
     Reporter:  zooko    |      Owner:
         Type:           |     Status:  new
  enhancement            |  Milestone:  1.9.0
     Priority:  minor    |    Version:  1.8.2
    Component:  code-    |   Keywords:  docs configuration defaults
  nodeadmin              |  usability
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by zooko):

 Okay I have this patch almost finished -- I'm just writing the source:NEWS
 and patch description, and I was writing "This will fail safe and fail
 loud if an old-style config is found", and then I started to wonder if we
 shouldn't ensure that it fails safe by stopping the node if it detects an
 old-style config file. If the node goes ahead and starts up and runs, then
 it will (after emitting a warning) be operating with different values than
 it was using in Tahoe-LAFS v1.8.2. I'm looking at the list of old-style
 config files wondering if it would be unsafe for the user if their node
 goes ahead and switches to the {{{tahoe.cfg}}} value from the old-style
 value for any of them. I don't like to wonder about things like that.
 (Even though there are few or no users who have any old-style config files
 left.)

 So I'm going to go back and change this patch to make the node emit a
 warning ''and then stop itself'', if it detects an old-style config file.

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