New answers tagged svn
Instead of creating an empty file (which I did not dare to do), I did a temporary fresh checkout of just the affected directory (specifying the same revision) and copied the missing file from the new .svn subfolder into the broken working directory's one. In order to further illustrate this, in my case, the file svn complained about was ...
Just change the permissions of .nano_history file as follows: sudo chown youruser:yourgroup /home/<username>/.nano_history DONE! The message is gone! =) Really is that simple.
Did you make sure that you are all using the same version of tortoisesvn? I'm doing something similar with different vms running on the same physical host and i've only had a problem if the working copy was checked out using an old version of svn. That could explain why the others only see an upgrade option ...
Top 50 recent answers are included