On Fri, Dec 14, 2018 at 5:26 AM Stefan Sperling <s...@elego.de> wrote: > On Thu, Dec 13, 2018 at 07:18:23AM -0600, Tom Browder wrote: ... > > description. Basically the subversion repos on my remote server were > > current as of about six months ago when they were established there > > and a hotcopy was made. > > You should reconsider your backup strategy. ... > a different physical machine. Use the post-commit hook to trigger a backup > (and the post-revprop-change hook, too, if your repository is configured > to allow revprop changes). ...
I was in the process of setting that up and got distracted (old age :-). > Only you can decide whether the history of your data is valuable to you. True. > > I started to update on one and am getting these messages (which you > > Clean Up: Failed to run the WC DB work queue associated with > > 'C:\Users\Tom\Documents\0-mydocs-svn', work item 636 (file-install ... > This error means the working copy is corrupt. This error has nothing to do > with the repository. The working copy's work queue contains instructions to > copy a temporary file into the area where you see the files you work with. ,,, > Generally, SVN's design considers working copies as disposable > because they can always be checked out again, Your resistence to > transferring your data again is working against that design assumption. I'm guilty as charged! > > Is there anything I can do to fix something like that? Or do I have ... > heard about last Sunday. Would it take you more than a week to transfer > the data? Maybe you should just do something that allows you to move on, > instead of waiting until you find a potentially perfect solution? Yes, I made some bad decisions. Many thanks, Stefan! -Tom