On Jan 7, 2025, at 03:48, Bo Berglund wrote: > > It seems like the sync was not really done for this repo for a long time even > though the nightly sync operation actually was working for all the other repos > where the mirror contains commits done up to the server crash...
Indeed! > And it is a single operation on the main server that runs these sync > operations. > > HOW to fix this? > Couild I proceed like this: > > 1- Make a repo dump on the main server and load that into the mirror. > That should bring the mirror to rev 4518 (same as main) You could, but I'd try to figure out what problem the sync process is encountering, and fix it so that you can then sync the remaining revisions. And also fix the problem that the error was not communicated to you when it first happened. Is the sync process sending you an email with errors and it's not arriving? Being classified as spam? Or is no email being sent? Does it log errors and are you checking that error log? Etc. > 2- Check out the involved 3 projects fresh from the main repo > > 3- Using the emailings as base commit the same files as are listed there > Thus recreating the 10 revisions that are missing. > > 4- Perform a manual sync to the mirror repo to bring that to rev 4528 > > Is there some caveat (apart from, getting the wrong dates into the revisions)? That sounds good. You can manually set the svn:date revision property to the proper historical date if you like, possibly after first writing a pre-revprop-change hook to allow it if you don't already have one that does that. Your recreated revisions will probably not be an exact match for the original revisions, and if they aren't, everyone who had working copies of this repo will have to trash them and check out new ones. > And *how* could this have happened and for such a long time? We would have to see whatever error messages your sync process is generating to be able to say how to fix it.
