On Wed, 25 Mar 2026 13:22:49 +0100, Daniel Sahlberg <[email protected]> wrote:
>I suppose you could just `svnadmin dump` the failing revision and then >`svnadmin load` it to the target repository and carefully `svn propset` >svn:sync-last-merged-rev to an appropriate value. Make sure you read >through and understand everything in the SVN book related to svnsync before >attempting this, test it on a testrepository and make a proper backup >before you try it for real. > >Hope it works out for you! Yes, it was a sync timeout when trying to synchronize across the Internet when there was this massive commit. I managed to create the dump file for the commit and move it to the mirror server and load it there. So the mirror now also contains the commit of that revision. But before I had finished the load into the mirror the developer actually removed the bad project so increasing the revision number again but this time without any associated committed files! The previously committed project is now invisible. I tried to sync again after I saw this and this time the sync process succeeds in the normal time but the revision on the mirror does not include the removal revision so it sits at an earlier rev still now. Do I have to dump the entire repo and load it on the mirror server in a different dir (rename the old repo, create a new by the same name and then load the full dump)? The end result should be that the mirror is exactly the same as the main repository. It is a backup and is never used actively itself with the exception of the nightly syncs. -- Bo Berglund Developer in Sweden
