On Jul 23, 2012, at 14:22, John Maher wrote:
> @Thorsten: Thanks for taking the time to respond, I do appreciate it, I
> should provide more background. I did use tortoise. Then I lost a
> bunch of source code trying to do a merge probably because I didn't know
> what I was doing. I started with version 1. Branched for version 2.
> Enhanced version 1 then merged to version 2 and somehow killed the
> enhanced version 1. All I could get was old version 1 or new version 2
> in effect prohibiting any more enhancements to version 1 (I didn't want
> to dig through version 2 to find the changes and put them back in
> version 1 with the release of version 2 so close). I have now completed
> version 2 and would like to get it under source code control without any
> code loss. That is why I wished to learn the command line version, it
> seems knowing how the CLI works will tell me how svn works better than a
> third party product. Am I right or wrong? Besides the book that I am
> reading only mentions command line options so it is incompatible with
> anything else. To top it off, I can get clarifications for the CLI here
> but the support for the other products stinks.
Yes learning the command line is probably helpful both for your understanding of Subversion and in performing certain operations.
> Thanks for the link
> http://en.wikipedia.org/wiki/Uniform_resource_locator, however it
> indicates the problem I was trying to resolve earlier. Wikipedia claims
> a URL points to a resource on the internet. We don't store our
> repository on the internet. We store it on our intranet. So either we
> can't use the command line to import files, which seems unlikely. Or
> svn uses the term URL differently than Wikipedia, very likely. I have
> seen numerous instances where different sources use terms differently.
> What does the svn book (http://svnbook.red-bean.com/en/1.7/svn-book.pdf)
> mean when it uses the term?
A URL identifies a resource on the Internet, or any other network (such as your intranet), or on your local computer. It always begins with a protocol (http, https, svn, svn+ssh, file), and continues with various optional parts, including hostname, port number, and path.
> Actually I don't need to create a directory, I need to create a
> repository. Looking at the server now it looks like we have a separate
> repository for each project with folders such as branches, tags and
> files stored in the root so we can't use a repository for more than 1
> project. Is this incorrect?
A repository is a versioned filesystem. You can store whatever you want in it, whether that's a single project or all your projects or photos or mp3s or recipes.
> So it looks like I need to create a
> repository before the import. I issued "svnadmin create" to make a new
> repository, and it succeeded but only when issued when the current
> directory was the repository directory.
That is correct.
> Actually it appears to succede
> anywhere, but I doubt the folders it creates are useable if they are not
> on the server.
Repositories are usable anywhere, but your server is probably only configured to use them from a particular location.
> Realizing I needed a new repository, I issued:
> svnadmin create iERP85_v2 WORKED!!
>
> svn import "g:/code/intuitive projects/projects"
> file://Vm006/Repositories/iERP85_v2
> svn import "g:/code/intuitive projects/projects"
> svn://Vm006/Repositories/iERP85_v2
> svn import "g:/code/intuitive projects/projects"
> http://Vm006/Repositories/iERP85_v2
You need to know which server process, if any, you are running on your server. Are you running apache? If so, then an http or https URL is correct. Are you running svnserve? Then an svn URL is correct. Are you allowing svnserve to start automatically as a result of an ssh connection? If so then an svn+ssh URL is correct. If you do not know what the URL of your repository(ies) is you need to talk to whoever set up the server.
> All fail with "Could not use external editor to fetch log message;
> consider setting the $SVN_EDITOR environment variable or using the
> --message (-m) or --file (-F) options"
>
> It appears that the import command has an undocumented required
> parameter, or something else is wrong, because when I provide the
> parameter I get different errors.
All commands that add a revision to the repository (such as import or commit) require you to enter a commit message. If you do not provide one on the command line, Subversion tries to open your preferred editor for you. If you have not configured your command line environment to indicate what your preferred editor is, then Subversion prints the message you encountered.
> import "g:/code/intuitive projects/projects" file://Vm006/Repositories/i
> erp_v2 -m "JPM"
> svn: E180001: Unable to connect to a repository at URL
> 'file://vm006/Repositories/ierp_v2'
> svn: E180001: Unable to open an ra_local session to URL
> svn: E180001: Unable to open repository
> 'file://vm006/Repositories/ierp_v2'
>
> import "g:/code/intuitive projects/projects" svn://Vm006/Repositories/iE
> RP85_v2 -m "JPM"
> svn: E730060: Unable to connect to a repository at URL
> 'svn://vm006/Repositories/iERP85_v2'
> svn: E730060: Can't connect to host 'vm006': A connection attempt failed
> because the connected party did not properly respond after a period of
> time, or established connection failed because connected host has failed
> to respond.
>
> import "g:/code/intuitive projects/projects" http://Vm006/Repositories/i
> ERP85_v2 -m "JPM"
> svn: E175002: Unable to connect to a repository at URL
> 'http://vm006/Repositories/iERP85_v2'
> svn: E175002: OPTIONS of 'http://vm006/Repositories/iERP85_v2': could
> not connect to server (http://vm006)
Received on 2012-07-23 21:41:31 CEST