Hmmm, [still] the only way I can get it to work is using sudo to
create the repo in /usr/local then going back and changing the chmod
to 777 and importing, everything else I’ve tried has been an utter
failure. I need to find step-by-step instructions written for a 6
year old.
Todd
On Aug 29, 2008, at 9:28 AM, waltd wrote:
It looks like I messed up with my instructions. If you followed the
first part – svadmin create ./repoman/test – then you will need
to add /test/ into all of the paths after that. Alternatively, you
could delete the test subdirectory and run the svadmin command again.
cd /path/to/repoman
rm -Rf test
svadmin create .
And from that point on, any path beneath repoman would be a virtual
directory, managed by the svn system. Where I messed up was I had a
directory called test on my machine, but then I started writing
repoman for test in my examples and left the test in there by mistake.
I don’t have svn 1.5 here, maybe there’s a difference there, but I suspect the following will work for you. It did for me, and I’ll run through it one more time, using real paths as best I can (!).
cd ~/Documents
mkdir repoman
svnadmin create repoman
svn import /Library/WebServer/Documents/activeform file:///Users/waltd/Documents/repoman/activeform/trunk -m "Initial Import"
svn co file:///Users/waltd/Documents/repoman/activeform/trunk /Users/waltd/Documents/activeform
So we have:
Moved into the documents folder
Created a folder to become the repository
Blessed the repository with svnadmin – not running as root when we do so
Imported an existing project into the repository
Checked out a working copy of that project into a different location
Now, if you open that working copy using Coda, you will find that the svn stuff will fill itself in for you, and if you check the Version Control checkbox in the Site preferences, you will see the svn flags next to each file in the project whenever they need to appear. There’s also a Version Control HUD palette that you can invoke using the View menu.
If you save changes to the working copy, there will be a flag that allows you to commit that change to the repository. Or you can carry on with your working copy, and commit your changes later after you have completed some unit of work.
But it’s a very good idea to make lots of little commits, rather than one massive one, because it makes it easier to back out of changes in an incremental manner.
Which shell and what version of the OS are you using? To find the shell name, just type any random garbage in Terminal and hit return. The error message should start with the shell name.
Which shell and what version of the OS are you using? To find the
shell name, just type any random garbage in Terminal and hit
return. The error message should start with the shell name.
Type’ which svn’ in Terminal to see which svn you will get if you just type ‘svn’. Then type ‘svn --version’ to see the version string. Your path could certainly be part of the problem, maybe you are getting mixed versions of svnadmin and svn.
Here’s the rest of the results here, for comparison:
al:Documents waltd$ which svn
/usr/bin/svn
al:Documents waltd$ svn --version
svn, version 1.4.4 (r25188)
compiled Nov 25 2007, 08:20:33
Copyright (C) 2000-2006 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http://www.Collab.Net/).
The following repository access (RA) modules are available:
* ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.
- handles 'http' scheme
- handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
- handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
- handles 'file' scheme
al:Documents waltd$ which svnadmin
/usr/bin/svnadmin
al:Documents waltd$ svnadmin --version
svnadmin, version 1.4.4 (r25188)
compiled Nov 25 2007, 08:20:33
Copyright (C) 2000-2006 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http://www.Collab.Net/).
The following repository back-end (FS) modules are available:
* fs_fs : Module for working with a plain file (FSFS) repository.
~ Home$ svn --version
svn, version 1.5.1 (r32289)
compiled Aug 3 2008, 16:38:18
Copyright (C) 2000-2008 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http:// www.Collab.Net/).
The following repository access (RA) modules are available:
ra_neon : Module for accessing a repository via WebDAV protocol
using Neon.
handles ‘http’ scheme
handles ‘https’ scheme
ra_svn : Module for accessing a repository using the svn network
protocol.
handles ‘svn’ scheme
ra_local : Module for accessing a repository on local disk.
handles ‘file’ scheme
T.
On Aug 29, 2008, at 11:49 AM, waltd wrote:
Type’ which svn’ in Terminal to see which svn you will get if you
just type ‘svn’. Then type ‘svn --version’ to see the version
string. Your path could certainly be part of the problem, maybe you
are getting mixed versions of svnadmin and svn.
Here’s the rest of the results here, for comparison:
al:Documents waltd$ which svn
/usr/bin/svn
al:Documents waltd$ svn --version
svn, version 1.4.4 (r25188)
compiled Nov 25 2007, 08:20:33
Copyright (C) 2000-2006 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http:// www.Collab.Net/).
The following repository access (RA) modules are available:
ra_dav : Module for accessing a repository via WebDAV (DeltaV)
protocol.
handles ‘http’ scheme
handles ‘https’ scheme
ra_svn : Module for accessing a repository using the svn network
protocol.
handles ‘svn’ scheme
ra_local : Module for accessing a repository on local disk.
handles ‘file’ scheme
al:Documents waltd$ which svnadmin
/usr/bin/svnadmin
al:Documents waltd$ svnadmin --version
svnadmin, version 1.4.4 (r25188)
compiled Nov 25 2007, 08:20:33
Copyright (C) 2000-2006 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http:// www.Collab.Net/).
The following repository back-end (FS) modules are available:
fs_fs : Module for working with a plain file (FSFS) repository.
~ Home$ svnadmin --version
svnadmin, version 1.5.1 (r32289)
compiled Aug 3 2008, 16:38:18
Copyright (C) 2000-2008 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http:// www.Collab.Net/).
The following repository back-end (FS) modules are available:
fs_fs : Module for working with a plain file (FSFS) repository.
On Aug 29, 2008, at 12:05 PM, waltd wrote:
Okay, now repeat with svnadmin: which svnadmin; svadmin --version.
This is probably irrelevant at this point, but I’ve found that if you make the owner of the repository the webserver, then Coda has no issue applying the changes, and you can leave the chmod settings at a 751 as opposed to global write. So owner webserver (on mac os x leopard _www) and group admin.
Just what works for me, I also wanted to throw out there a thanks for this discussion even existing because it kick started my memory as to how I got my previous repositories working with Coda (which, by the way is a killer app!).
You’re welcome. I’m glad my bumbling about could be of use to someone.
Todd
On Apr 12, 2009, at 4:09 AM, pocketWashburn wrote:
I also wanted to throw out there a thanks for this discussion even
existing because it kick started my memory as to how I got my
previous repositories working with Coda (which, by the way is a
killer app!).