tags:

views:

593

answers:

1

hellow all , i am using svn for my xcode project. now i added two files into current project and added to repository and commit changes for classes folder. But,when i am trying to commit entire project i am getting error like "Error: 155005 (Working copy not locked; this is probably a bug, please report) Description: Commit failed (details follow): Error: 155005 (Working copy not locked; this is probably a bug, please report) Description: Directory '/Users/gopalmadhu/Desktop/All My data/Schduler current code/build/Debug-iphonesimulator/scheduler.app.dSYM/.svn' containing working copy admin area is missing "

due to this the classes that are already checked -in also not getting visible when i check out my code . the files are in the project but not visible.so i need to add them again from the project floder to classes folder. this is not correct way of managing the svn.. so wht can i do to solve my problem .coud anyone help me solve this. Thanks ..

+5  A: 

Your problem is in committing build results to Subversion.

Subversion works by putting a hidden folder called .svn in every folder that is under version control. This does not work well with folders that might get deleted and recreated by a tool because the tool will probably not respect the existence of the .svn folder. That includes the whole build directory, the contents of which get wiped every time you clean your project targets.

You should remove your build directory from version control. It shouldn't be in there anyway since everything in it can be regenerated by doing an Xcode build. To get out of your existing dilemma try the following:

  1. Back up your project somewhere
  2. In a terminal go to your project directory and rm -rf build
  3. do an svn update. At this point Subversion will hopefully restore the build directory.
  4. svn rm build
  5. svn commit -m "Removed build from version control"
  6. (optional) svn propedit svn:ignore . This will bring up an editor for the svn:ignore property. Add build on a separate line. After that subversion won't show you the build directory in svn status commands.
JeremyP
Thanks alot for Your Response . It works for me in this case . great relief... thanks once again
ratnasomu
If it fixed the problem for you, please can you accept the answer :)
JeremyP
i accepted the answer Jeremy P . but i have 1 problem here can u solve that after commit the project now if at all i changed anything its not showing me the M symbol and commitchanes etc.. it simply coming like a local file.. i have edited the project settings dnt knw wht happening here thank you
ratnasomu
That's because build *is* now a local file. You should never have your build directory under version control.
JeremyP
ok so there is no problem if I work like this i.e; with out M symbols and disabled commit project etc .. but any how if we want to check with previous versions this way is not good now Jeremy
ratnasomu
in this case i have added 2 files for checking to know whether they are committing or not.sad,they are not committing, those are not adding to project als ,help me out how can we get that add to repository ,M symbols etc .so, when ever we want to commit the project at that time can delete the build .. Help me
ratnasomu
These two files. Are they in the build directory? You should not put your own stuff in the build directory. If they are in the main project directory, you need to `svn add` them so that Subversion knows that you want to keep them under version control. You can also do that from Xcode, but I find the command line interface to be more reliable.
JeremyP
i have added them in the classes folder. jst svn add is enough when it can give after svn commit or before svn commit . and did you understand my problem here i want scm to be worked for checked out files that is when ever i added the files it should come with ? marks and add to repository option should be there ,...
ratnasomu
svn add is not working its giving not enough arguments ...
ratnasomu