0

We have a network folder on the Windows domain in which we would like to keep the release source codes. We would like to be able to build the code on the machine of a random developer of our team.

So I created a network folder and checked out the source code into it. Whenever I do an Update, there aren't any problems. But it looks like no one else but me is able to do an update into that folder. They get the following error in tortoisesvn:

Working copy "blabla" locked
sqlite: attempt to write a readonly database

How can I fix this issue?

Liezzzje
  • 430
  • 2
  • 6
  • 17

1 Answers1

3

Working Copy on network drive (and repository also) was and is always Bad Idea (tm)

Quote from Simon Large

Placing repositories on a network share has always been discouraged very strongly. Sharing working copies has always been strongly discouraged too, because it negates the whole point if having revision control.

Additional reading:

Lazy Badger
  • 94,711
  • 9
  • 78
  • 110
  • Ok, but we are all developing in our source code. Where should we keep the release version of the code? For example: I urgently need to fix a bug, but I'm working on something else. In that case, I would fix the bug, check in the code and recompile the release version. I don't want to compile my code, as it contains other modifications that I don't want to compile. – Liezzzje Nov 20 '12 at 08:49
  • @Liezzzje - please, read SVN Book, fist chapter, in order to be able to speak on common language. Anyway "release version" you'll store on *some URL* **in Repository**, you asked about dealing **with Working Copy**. Read about branches in Subversion and in SCM in common – Lazy Badger Nov 20 '12 at 14:08