On Tue, 07 Jan 2025 22:08:33 +0100, Bo Berglund <bo.bergl...@gmail.com> wrote:
>In the batch file the command is created at the start and then used for all >repos going down the file. Here is how it is defined (again wrapped lines): > >rem If a repository is not synced due to a lock problem, then use --steal-lock >in a manual command > >rem SET SYNCCMD="C:\Program Files\VisualSVN Server\bin\svnsync.exe" synchronize >--steal-lock --sync-username syncuser > >SET SYNCCMD="C:\Program Files\VisualSVN Server\bin\svnsync.exe" synchronize >--sync-username syncuser > >What looks like a commented out suggestion about --steal-locks may or may not >apply here, what does it mean an how to use it? I tried it and got another set of error messages: H:\>"C:\Program Files\VisualSVN Server\bin\svnsync.exe" synchronize --steal-lock --sync-username syncuser https://svn.mydomain.com/svn/pc https://agiengineering/svn/pc Stole lock previously held by 'AGIENGINEERING:4b3622e3-1724-2d47-9cdd-82690ad1fe60' svnsync: E000022: Revision being currently copied (4499), last merged revision (4498), and destination HEAD (4518) are inconsistent; have you committed to the destination without using svnsync? What to do now? Am I hosed or is there some repair possibility? Should I dump the full pc repo in its present state and recreate it from scratch on the mirror after deleting it? What are the steps to do that? -- Bo Berglund Developer in Sweden
