[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2235: Error from 'tahoe cp' on Windows, possibly due to a long path (IOError: Errno2 - no such file or dir.)

[Tahoe-LAFS]

#2235: Error from 'tahoe cp' on Windows, possibly due to a long path (IOError:
Errno2 - no such file or dir.)
--------------------------------+------------------------------------------
     Reporter:  CyberAxe        |      Owner:  daira
         Type:  defect          |     Status:  new
     Priority:  normal          |  Milestone:  undecided
    Component:  code-frontend-  |    Version:  1.10.0
  cli                           |   Keywords:  tahoe-cp error windows win32
   Resolution:                  |
Launchpad Bug:                  |
--------------------------------+------------------------------------------

Comment (by zooko):

 Replying to [comment:7 daira]:
 > Replying to [comment:5 daira]:
 > > * Paths prefixed with "`\\?\`" must be absolute, but CLI commands
 accept relative paths. Also, they don't canonicalize in the same way, e.g.
 "`..`" and "`.`" are not supported.
 >
 > Given this constraint, the best place to prepend "`\\?\`" would probably
 be in `fileutil.abspath_expanduser_unicode`.

 Okay, I don't see any reason ''not'' to prepend "`\\?\`" to all paths when
 reading files.

 We should probably think about it a bit more when ''creating'' files i.e.
 during a {{{tahoe get}}}, because if we do this then the resulting files
 wouldn't be accessible via tools that don't support long paths, such as
 the Explorer or cmd.exe, for example, if I understand correctly.

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