Question

I have a number of files checked out with changes ready to submit.

I realised that my client spec was hardcoding my alternate root, so I removed the alternate root from all lines in the client spec, and specified it in the alternate root box instead.

I also had some files not checked out that I wasn’t ready to add to changelists so I renamed the directory structure underneath and then synced all branches I needed and then renamed the directory to AltBranch and renamed the old one back.

Now however all the checked out files are listed as “not mapped to workspace view” – they are still there however.

I wanted to force perforce to agree with my version, so I tried p4 sync -k, however I get the error

//.../X.cpp#10 - is opened for edit and can't be deleted

I then tried p4 sync -k -f, but I get the error

//.../X.cpp#10 - refreshing C:\Work\...\X.cpp
//.../X.cpp#10 - is opened for edit and can't be deleted

On the whole I really like Perforce, however its insistence in always knowing best is frustrating

Answer 1

I have managed to produce a batch file that contains a sequence of Perforce commands to achieve what I want.

This solution is Windows/DOS specific – although I would imagine other command shells could do the parsing needed for this fix:

 @ echo off
 echo Please Exit Perforce
 pause
 setlocal
 rem Retrieve depot spec format of file
 for /f "delims=# " %%d in ('p4 files %1') do set p4name=%%d
 rem Retrieve current pending changelist
 for /f "tokens=5 delims= " %%d in ('p4 opened %p4name%') do set change=%%d
 p4 revert -k %p4name%
 p4 sync -k %p4name%
 p4 edit -c %change% %1

This version is specific to files, although a directory version would be possible substituting files for dirs

Also stupidly the Command Prompt does not set ERRORLEVEL if the command in the ticks fails.