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

Re: Commit failed (I'm a beginner to Subversion and TortoiseSVN)

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: 2007-05-08 23:59:06 CEST

On 08/05/07, Shah, Ravi P. CIV NAWCAD, 4.1.4 <ravi.shah@navy.mil> wrote:
> Ryan,
> First and foremost, Thanks for your response!!! I've re-created the
> scenario here using the Subversion manual.
> A. Created new repository
> 1. In C:\, created empty folder named SVN2
> 2. In the SVN2 folder, created MyNewRepository
> 3. On the command prompt, went to path C:\SVN2. In this path,
> entered the command:
> svnadmin create --fs-type fsfs MyNewRepository
> B. I created a MS VC++ project under the path: My Documents\SVN
> projects\helloSVN. In other words, it's helloSVN. I attempted to change
> the repository for the file, helloSVN.cpp.

Save yourself a lot of repetitive typing and make this into a batch file.
1. Delete existing test repository and WC.
2. Create a new test repo and WC.
3. Add some content and commit

The whole point in doing this is so that others can reproduce the
problem. Creating a batch file makes it easy to see what you are doing
and reproduce it painlessly, and it makes it easier for you to start
over and tweak your script until you can reproduce the fault you saw

> 1. On the command prompt, went to the path, MyDocuments\SVN
> projects.
> 2. svn import helloSVN file:///C:/SVN2/MyNewRepository
> 3. Got the following message:
> svn: Could not use external editor to fetch log message;
> consider setting the $S VN_EDITOR environment variable or using the
> --message (-m) or --file (-F) options
> svn: None of the environment variables SVN_EDITOR, VISUAL or
> EDITOR is set, and
> no 'editor-cmd' run-time configuration option was found

You must supply a commit message. If there is none on the command line
svn will try to get one interactively, but you hadn't set this up. Use
command line messages for this sort of recipe.

> 3. Next attempt:
> svn import helloSVN file:///C:/SVN2/MyNewRepository \ -m
> "Initial Import"

The backslash in the manual just means "this won't all fit on one line
in the manual, but you should still type it on one line". I think it
says that somewhere.

> 4. Got the following message:
> svn: Too many arguments to import command
> 5. Next attempt:
> svn import helloSVN file:///C:/SVN2/MyNewRepository -m
> "Initial Import"
> 6. Listed all files and directories added under helloSVN and
> showed message
> "Committed revision 1".
> 7. Did a checkout: svn checkout file:///C:SVN2/MyNewRepository
> 8. Listed all the paths that were checkout
> 9. changed paths to the C:\ directory
> 10. entered the following command: svn list
> file:///C:/SVN2/MyNewRepository
> 11. Listed the files and directories
> 12. I looked in Windows Explorer and realized that a folder
> named MyNewRepository was added in My Documents\SVN projects\helloSVN.
> 13. So far, I've been unable to revert what I checked out. I've
> tried the following command lines: (... indicates intermediate directory
> names/paths)
> svn revert file:///C:.../My
> Documents/SVNprojects/helloSVN/MyNewRepository
> svn revert file:///C:/SVN2/MyNewRepository
> svn revert file:///C:.../My Documents/SVN projects/helloSVN
> svn revert file:///C:/SVN2
> svn revert file:///C:.../My Documents/SVN
> projects/helloSVN/.

You misunderstand what revert does. Revert discards *uncommitted*
changes in your working copy. You may have been misled by this use of
the term in TortoiseSVN, although the text is subtly different "revert
all changes made in this revision".

If you have a directory there which shouldn't be, the easiest way is
to svn delete it.

> 14. All these attempts gave me the following error messages:
> svn: 'file:\\\C:\Documents' is not a working copy
> svn: Can't open file 'file:\\\C:\Documents\.svn\entries':
> The filename, directory
> name, or volume label syntax is incorrect.

All these are due to the space in your filename. You're not used to
working on the command line, right? Q: How does the program
distinguish between spaces between command line arguments and spaces
in a filename? A: It can't; you have to use quotes around any paths
which contain spaces to make it unambiguous.

You really need to have another look at the manual for subversion. It
is all very well explained, and set out as a tutorial. From your
description so far you are not doing anything very unusual or
advanced, so you shouldn't have to read too far to cover the basics
that you need.


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 10 02:43:45 2007

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.