[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Renaming Files and Committing

From: Stawiszynski, Piotr <Piotr.Stawiszynski_at_sabre.com>
Date: Fri, 22 Feb 2008 13:36:03 -0000

Did you use svn move command to rename your file?

--
Piotr Stawiszyński
 
________________________________
From: Hatem Jaber [mailto:393_at_7079.net] 
Sent: Friday, February 22, 2008 1:52 PM
To: users_at_subversion.tigris.org
Subject: Renaming Files and Committing
Hi, I am testing the various commands and features that subversion offers before we actually setup our remote server with a repository. One thing I encountered this morning was the error messages that I receive when I rename a file and committ to the repository.
 
Step by step playback:
 
1) Created projecta
2) Created trunk tags branches
3) Checked out trunk to workspace
4) Added 2 files index.cfm, product.cfm, and service.cfm
5) Added news.cfm, newsdetail.cfm, and I renamed service.cfm to services.cfm
 
I received an error when attempting to do that through subclipse, here is the exact error:
 
svn: Commit failed (details follow):
svn: Commit failed (details follow):
svn: COPY of /svn/projecta/!svn/bc/7/trunk/service.cfm: 400 Bad Request (http://svn.url.com <http://svn.url.com> )
Now I will try it using TortoiseSVN and see if that has any better luck.
 
Error from TortoiseSVN as follows:
 
Error Commit failed (details follow):
Error COPY of services.cfm: 400 Bad Request (http://svn.url.com <http://svn.url.com> ) 
 
Shouldn't I be able to rename a file and subversion handle the delete and add without a problem?
 
The strange thing is that I renamed a file yesterday as I was playing with it and it seemed to work fine. But now for some strange reason it's not working and causing the errors I mentioned above. Any recommendations would be greatly appreciated!
 
Thanks,
HJaber
Received on 2008-02-22 14:36:32 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.