[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1333: 'private/' subdir of BASEDIR should be created during 'tahoe create-alias' and friends

[Tahoe-LAFS]

#1333: 'private/' subdir of BASEDIR should be created during 'tahoe create-alias'
and friends
--------------------------------+-----------------------
     Reporter:  warner          |      Owner:
         Type:  defect          |     Status:  new
     Priority:  minor           |  Milestone:  undecided
    Component:  code-nodeadmin  |    Version:  1.8.1
   Resolution:                  |   Keywords:  easy
Launchpad Bug:                  |
--------------------------------+-----------------------

Old description:

> user 'munderwo' on the IRC channel noticed an exception when they
> manually deleted their {{{~/.tahoe}}} directory, then re-created it, then
> ran {{{tahoe create-alias}}}. It complained that the
> {{{~/.tahoe/private}}} directory did not exist, which trying to write
> {{{aliases.tmp}}}.
>
> I suspect that we create this directory during {{{tahoe create-client}}},
> but then assume that it exists later. Instead, if {{{tahoe create-
> alias}}} notices that it is missing, it should just re-mkdir it.

New description:

 user 'munderwo' on the IRC channel noticed an exception when they manually
 deleted their {{{~/.tahoe}}} directory, then re-created it, then ran
 {{{tahoe create-alias}}}. It complained that the {{{~/.tahoe/private}}}
 directory did not exist, which trying to write {{{aliases.tmp}}}.

 I suspect that we create this directory during {{{tahoe create-client}}},
 but then assume that it exists later. Instead, if {{{tahoe create-alias}}}
 notices that it is missing, it should just re-mkdir it.

--

Comment (by Lcstyle):

 If the issue is still present, I think I can tackle this one, please
 assign.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1333#comment:3>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage