[p4] p4v sync -f failing with unable to create a file that has been removed from repository

Patrick B perforce-user-forum at forums.perforce.com
Tue Apr 21 08:05:01 PDT 2015


Posted on behalf of forum user 'Patrick B'.

Limitations is right... it requires a server side setting (no big deal) AND an
option specified by every single client/api everywhere for every
command.  It's basically a non-starter.  Clearly if sync
can't 'create' a file that is too long given the constraints, fine,
but to treat as an error the 'attempt' to delete a file that isn't
even there is pretty broken.  Windows long filename support has been
there for a very long time (at the api/file system level). It really
shouldn't have to be specified explicitly in my mind.  It should
just work.  Perforce should handle it.  If other programs
don't like the long filenames, that's not a problem Perforce should
worry about.



--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/4036-p4v-sync-f-failing-with-unable-to-create-a-file-that-has-been-removed-from-repository



More information about the perforce-user mailing list