Unfortunately, the push to the destination depot isn't working - it complains about locked files in DVCS workspaces:
% p4 login -r hostedclone Enter password: User Jamie.Penman logged in. % p4 -I push -n -r hostedclone push load revisions 331759 finishing check files 100% finishing 18213 change(s) containing a total of 331759 file revision(s) were successfully pushed. This was preview mode; no modifications were made. % p4 -I push -r hostedclone push load revisions 331759 finishing check files 100% finishing //depot/systems/EITP/1B/SOL_X86/APAS/run/client-cfgs/DERIVS_USER/cfg/Desktop/20120521_INT_TRADER_Phase1a.FWS - locked by Another.User@Another.User-dvcs-1452014579 Cannot import revisions. Not all files could be locked. %
Looking directly at the depot, this file isn't opened anywhere:
% p4 opened -a //depot/systems/EITP/1B/SOL_X86/APAS/run/client-cfgs/DERIVS_USER/cfg/Desktop/20120521_INT_TRADER_Phase1a.FWS //depot/systems/EITP/1B/SOL_X86/APAS/run/client-cfgs/DERIVS_USER/cfg/Desktop/20120521_INT_TRADER_Phase1a.FWS - file(s) not opened anywhere.
Looking at the p4 push documentation I noticed this:
the remote server, it will leave those files locked on the remote
server. 'p4 opened' will display '*locked*', and the files cannot
be submitted by any other user. If the push command cannot be
quickly retried, you can use the 'p4 unlock -r' commmand to unlock
the files on the remote server.
So I tried p4 unlock -r, which gives 'no permission to lock'
% p4 -c Another.User-dvcs-1452014579 unlock -r -f ... //depot/fidessaNet/systems/GTP/STATIC/TOP/run/site-specific/RISK-DLS/2013-09-26/FF_FR_OPFI-RISK_DLS.txt - no permission to lock file //depot/fidessaNet/systems/GTP/STATIC/TOP/run/site-specific/RISK-DLS/2013-10-21/FF_GB_FOG-RISK_DLS.txt - no permission to lock file //depot/fidessaNet/systems/GTP/STATIC/TOP/run/site-specific/RISK-DLS/2013-10-23/FF_GB_FOG-RISK_DLS.txt - no permission to lock file //depot/fidessaNet/systems/TOOLS/MAIN/.site_cshrc - no permission to lock file //depot/fidessaNet/systems/TOOLS/MAIN/p5 - no permission to lock file //depot/fidessaNet/systems/TOOLS/MAIN/version.txt - no permission to lock file ...
...even though I've used -f and so have super permissions.
Any ideas on how to unlock any files locked in the other DVCS workspace so the push can progress?