Also note that svn update would merge your changes with the head revision potentially leading to merge conflicts which you would have to manually resolve.
Main Topics
Browse All TopicsHi experts,
Short version: Can I force a commit "no questions asked"? How? Would that still allow me to access / compare the previous versions?
More details!
I'm currently working on a project with lots of files and updates... so I must have some version control program. Some years ago I used CVS, but it seems that now Subversion is the route to go. Running on XP, I selected TortoiseSVN as a client since it also seems the route to go.
So I have installed TortoiseSVN on my local machine, the goal being to track changes of the local versions of some projects.
NOTE:
1 - I am the single user of the machine, and for all the files (I will also import some files and place them in the version control)
2 - it seems that SVN is not installed as an a program, just subversion. [Maybe THAT is the problem?]
I have painfully made my way thru the doc (it somehow assumes that you already know Subversion... which I didn't) and placed 3 different tress/ projects in the repository. What I did was to create the repository, export the directory tree, delete the files from the disk, checkout the project , which repopulated the directory tree with all the needed.svn dir.
Of course I am working on the project file. And in fact, since that was my goal, I transferred files by FTP from my remote server where the project is going to run.
After that, I wanted to commit the changes on my local machine.
This has worked fine on most files and directories, but there are some strange situation I do not understand how I could solve them.
The most frequent/ significant messages I get in my various attempts to circumvent the problem are:
Command : Commit
Modified : D:\XXXX\var
Error : Failure for propagation (commit), details :
Error : Directory '/un-carat/var' is obsolete
Error : You have to update your working copy first.
Finished! :
13/01/2009 - 13:45:50
Command : Commit
Error : The working copy of 'D:\XXXX\downloader\pearli
Error : Please execute the "Cleanup" command.
Finished! :
Can I force a commit "no questions asked"? How? Would that still allow me to access / compare the previous versions?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
1 - Update did the trick. It was safe because the only changes that remained where on the directory itself, not on the file it contains. THX A LOT
2 - The cleanup thing did NOT work though. No easy way to make a text capture of the error message, so I attach a screen capture. My version is in French.
"Dans le répertoire" means "in the directory"
"Erreur en exécutant la command" means "Error while processing the command"
"La copie de travail" -> the working copy
"est verrouillée" -> is locked
When I try to unlock the \data which is said to be locked, I get the error message "There's nothing to unlock. No file has a lock on this working copy"
B-((
No directory is locked.
However, the display evidences that SVN "ignores" some directories.
I believe most of this dirs were there earlier.
Then I asked that the directory "cache" should not be synced.
This apparently worked... but I probably did something else so thee are more directories ignored... And when I try to "add" the directories, I'm told there is nothing to add since all the files are all present in the repository...
OK, thx a lot. This placed me on the right path. Doing it tooks some time..
What I did in fact, since I did not have a clean copy of the files
- copy the files to some other place, then delete the old place
- in the copy: delete all existing .svn directories
and use this as the source for copying the last version.
Business Accounts
Answer for Membership
by: sunnycoderPosted on 2009-01-14 at 03:08:52ID: 23371516
First error message means that your current working copy is not up to date. e.g. If head revision of a file is 100, your working copy is <=99. If you do an svn update before checking in, error would go away.
Second error message can be removed by executing svn cleanup as indicated.
I am not aware of any way to force checkin