I’ve received several queries about the SMB patch that I mentioned in my svn-on-osx post. Unfortunately, when I went hunting for the patch the second time around, I wasn’t able to find it. But I was finally able to solve my OSX/Subversion/scplugin problems by using the svn+ssh transport, thus:
svn+ssh://username@some.server/path/to/repository
Once I gave up on SMB file sharing, I’ve had no trouble with scplugin or Subversion on Mac OS X.
On some earlier posts (tagged scplugin) I was trying to get scplugin working on my Mac (OS X 10.4.6). It seems like the problem may be due to subversion (svn) failing to communicate with my SMB-based repository. To test that, I made a local repository and created a test project within it.
First, let’s make sure DarwinPorts is up-to-date:
$ port sync Error: /opt/local/bin/port: port sync failed: sync failed doing rsync
Doh! I always forget to sudo that command…
$ sudo port sync Password: $ sudo port selfupdate DarwinPorts base version 1.200 installed Downloaded DarwinPorts base version 1.211 Configuring, Building and Installing new DarwinPorts base selfupdate done! $ port version Version: 1.211
(Just because I’m paranoid…)
Okay, now let’s see what version of svn I have installed, and compare that to what’s available from DarwinPorts:
$ svn −−version svn, version 1.3.0 (r17949) compiled Apr 4 2006, 11:47:42 $ port info subversion subversion 1.3.1, devel/subversion (Variants: mod_dav_svn, no_neon, no_bdb, mac-os-x-server-mod_dav_svn, tools)
Yep, the 1.3.1 version has made it into DarwinPorts so let’s upgrade that:
$ sudo port upgrade subversion −−−> Fetching subversion yadda yadda yadda −−−> Installing subversion 1.3.1_0 −−−> Activating subversion 1.3.1_0 −−−> Cleaning subversion $ svn −−version svn, version 1.3.1 (r19032) compiled Apr 20 2006, 15:31:38
(Paranoia again…)
Cool, the tools are up-to-date, so now it’s time to make a new local repository.
$ svnadmin create /path/to/local/repository $ svn import -m “Creating testproj” testproj/ file:///path/to/local/repository Adding testproj/some_file Committed revision 1.
Now let’s checkout a copy of the project and see how it looks in Finder.
$ svn checkout file:///path/to/local/repository/testproj svn: URL ‘file:///path/to/local/repository/testproj’ doesn’t exist
Oops, looks like I screwed up the repository import. I’ll just check out the whole repository for now, and rtfm for help with project importing later.
$ svn checkout file:///path/to/local/repository/ A svn_repository/some_file Checked out revision 1.
A quick perusal with Finder doesn’t show any visual svn status indicators, but after I made a change to the file I got to see scplugin’s “red bang” over the file icon, indicating that the file was out of sync with the repository. Woo hoo! Right-clicking or control-clicking on the changed file presents me with a Subversion context menu, from which I selected commit:
Sending some_file Transmitting file data . Committed revision 2. Process finished with exit status 0.
That looks pretty good. Unfortunately, scplugin hasn’t changed the status indicator in Finder–it’s still showing the red bang, even though the working copy and the repository are now in sync. Relaunching Finder doesn’t change this. 
Hmm…
Well, that’s some progress–at least subversion is working! I’ll play with scplugin some more and see what I can find out.
Thanks to Stu (no URL) and Ant, I think I’ve made some progress on scplugin! For some background, see my post on Subversion on Mac OSX and my subsequent attempts to get SCPlugin to work with Finder.
After trying Stu’s and Ant’s suggestions, I now get a Subversion menu when I control-click or right-click on a file/directory in the Finder. Woo hoo! Everything looks good, too. If I open the Subversion menu on a file which isn’t part of a svn working copy, only the Checkout and About menu items are available (as expected). Subversion working copies show the full menu (or whatever is appropriate). However, there are two things that still seem to be broken: the svn status indicators (icon overlays?) aren’t showing up in Finder, and I seem to have hosed the connection to my repository. Doh!
We’re using smb file shares to host our repository. When I first set this up, I connected to the file share (⌘K in Finder) and checked out a working copy of the repository. I could only work via the command line, but everything worked. Fastforward to a few days ago (when Stu and Ant dropped comments). I’m now trying to use scplugin again (not the command line), and all of the sudden nothing is working. It finally dawned on me that perhaps I should try the command line again. It turns out that when I first created my working copy, I must have somehow given a connection-specific smb string instead of the server name followed by the share. Here are the errors I’m getting:
svn commit -m 'Changed script to be user-independent' my_script
subversion/libsvn_client/commit.c:873: (apr_err=180001)
svn: Commit failed (details follow):
subversion/libsvn_ra_local/ra_plugin.c:285: (apr_err=180001)
svn: Unable to open an ra_local session to URL
subversion/libsvn_ra_local/split_url.c:125: (apr_err=180001)
svn: Unable to open repository 'file:///Volumes/server-3/my_proj/trunk/my_script’
The /Volumes/server-3 bit is where the problem lies–It should be /Volumes/sharename, instead of the third connection to this server. I did some hunting around on the net and found out how to fix broken svn repository references: use svn switch --relocate, such as:
svn switch --relocate file:///Volumes/server-3 file:///Volumes/sharename workingcopyroot
or so I thought. Now I’m getting the following error:
svn commit -m 'Changed script to be user-independent' my_script
subversion/libsvn_client/commit.c:873: (apr_err=5)
svn: Commit failed (details follow):
subversion/libsvn_subr/io.c:2199: (apr_err=5)
svn: Can't write to file '/Volumes/sharename/my_proj/db/transactions/3-1.txn/rev': Input/output error
Bummer. It may be time for a bug report…
I found a lead on why Subversion may not be working with Finder in Mac OSX (Tiger, version 10.4.4) on the System Preferences... tool. There is now an “SCPlugin” item on System Preferences. Open this up and you’ll find a checkbox labeled Enable Finder Integration (which was unchecked on my system). I checked this button, but there was no visible change on any of my Subversion-controlled files. I relaunched Finder, but still no indication of Subversion status on my files. It may be that I need to specify the Subversion Executable on the SCPlugin preferences, but there is no way for me to type in the path–there is only an Open button which launches a Finder-style widget, and I can’t figure out how to navigate to /usr/local with it.
Wait, maybe it is working, sort of… I just right-clicked on a Subversion-controlled file and found the “Subversion” context menu, but none of the operations seem to be doing anything. I’ll have to see if I can figure out how to type in an absolute path in Finder for the svn executable.
I was finally going through Chris J. Davis’ article, SVN on MacOS X. I downloaded the Subversion package to my Mac and it works fine via the command line, but I ran into trouble with scplugin, (the tool which bolts SVN on to the Finder.)
The first (easy) problem was that the download link for the scplugin binary is out-of-date. It’s now available here, on the Documents & files page.
The second problem: SCPlugin doesn’t seem to work. I’ve restarted the Finder a few times, but I can’t find a Subversion context menu anywhere. This is a bummer, but I can work from the terminal app for a while I guess. I may even have a chance to fiddle with this some more over the weekend.
In case anybody wants to know, I’m running MacOS X 10.4.3 on a 17″ PowerBook G4, svn version 1.3.0 and SCPlugin revision 269.
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Dec | ||||||
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 | 30 | 31 | ||||
