[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 07:25:01 PDT 2015


Posted on behalf of forum user 'Patrick B'.

If -f is specified then Perforce will forcefully try to remove deleted files as
well (to ensure they're really not there - which makes sense).
The problem is the max path error is broken in this case.  For *that*
given path, it wouldn't have been able to create the file in the workspace
in the first place so to error out saying it can't remove a file that it
couldn't have put there is bogus.
This has caused us a lot of heartache lately with build servers that use -f for
syncing.



--
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