[ https://issues.apache.org/jira/browse/SVN-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264233#comment-17264233 ]
Johan Corveleyn commented on SVN-4868: -------------------------------------- Thank you for filing this issue [~dcamarena]. I agree this would be a nice improvement if SVN could auto-fix this kind of working copy corruption. To be clear: I don't currently have the time to work on this myself, sorry. Just confirming the validity of the request ... For some more background: this was discussed / asked earlier on the tortoisesvn users list: https://groups.google.com/g/tortoisesvn/c/4r_zm4-DBdU?pli=1. I had participated in that discussion, saying that I would bring the issue to one of the SVN mailing lists, which I sadly forgot to do. So thanks, Daniel, for picking this up via StackOverflow, and filing it here. > Error "Unable to create pristine install stream" when .svn\tmp folder is > missing > -------------------------------------------------------------------------------- > > Key: SVN-4868 > URL: https://issues.apache.org/jira/browse/SVN-4868 > Project: Subversion > Issue Type: New Feature > Reporter: Daniel Camarena > Priority: Minor > Attachments: r4NcG[1].png > > > When the .svn\tmp folder is missing in the working copy any action (update, > commit, etc.) fails with the message "Unable to create pristine install > stream". > Obviously it's the users fault when corrupting the hidden, internal directory > of SVN. In my case the folders of thousands of working copies were missing > after disaster recovery. I discovered that my backup software didn't backup > "tmp" folders. > I created a work around to create the tmp folder and posted it here: > [https://stackoverflow.com/questions/35962861/how-to-fix-unable-to-create-pristine-install-stream/65704644#65704644] > > Anyway it would be nice if SVN would catch that exception and try to create > the .svn\tmp folder. -- This message was sent by Atlassian Jira (v8.3.4#803005)