On SVN, sf.net and MacOSX

Just a short note to everybody who is struggling with either (or both) problems:
* since only recenly was unable to use your sourceforge.net hosted subversion account with strange response 403
* was trying to use SCPlugin for MacOSX with https:// repositories without success

The solution to the first problem is pretty simple - you are probably using http://...sf.net/... address for your repositories - this is no longer supported.
To solve your problems - do

svn switch --relocate http://...... https://.......

The second problem might (as in my case) arise from the SSL certificate problems with the subversion server. If you enter your repository URL to the web browser and it asks you to confirm the certificate than this is exactly the problem I was facing, and ... good news - here is the solution for you. Apparently SCPlugin still cannot ask you to confirm the certificate through GUI, so you have to do it yourself manually.

The easiest way is to call

svn ls https://.....

and answer (p)ermanently to the given question.

However, since neither MacOSX (Leopard 10.5.4) nor Fink provides subversion in the new (backward incompatible!), endorsed by sf.net version 1.5 you might consider using the one (1.5.1) provided by SCPlugin at the following location:

/Library/Contextual\ Menu\ Items/SCFinderPlugin.plugin/Contents/Resources/SCPluginUIDaemon.app/Contents/bin/svn

The new SmartSVN 4 is also compatible with SVN 1.5 so your command line SVN might soon be incompatible with your repositories (if you use SmartSVN 4 at least once with this repository!)

Drag and Drop in MacOS X

One think I simply love about Mac is the consistency of UI interaction design.

For example, you can drag and drop files - right simple. But you can also use the same paradigm to copy color code from one editor to another. It is much easier than retyping it, or twisting arm to get it to the text editor.

Here is a short example:

Running fresh Leopard **might** solve your AirPort problems

I could not stand it any longer - certain issues which worked on Ewelina’s Mac somehow did not work on mine, e.g., no auto-connect to known WiFi networks.

I thought to myself - this have to be because I did Tiger-to-Leopard upgrade. Time to reinstall my precious Leo and see what will happen.

The whole procedure started on Friday night, and I got it operational few hours later with my stuff seamlessly migrated thanks to the wonders of TimeMachine/TimeCapsule (sweet - trust me).

I have saved a lot of space as a side effect - this time I knew what NOT to install ☺

And the Wifi apparently worked just fine.

At least until .... I came downstairs where a separate WiFi network is setup (our walls as so tick the signal can hardly go from one floor to other). To my surprise - autoconnect to the network downstairs did no work. I was trying everything - from changing network settings to fiddling with KeyChain access.

Nothing helped.

Than, following an old and very good advice of my old friend and Unix guru in one person, i.e., Dorota, I have checked LOGs using Mac’s Console.
And I have found this:

7/27/08 15:16:44 SystemUIServer[122] Error: _ACNetworkCopyKeychainItem() expected password for "WiSkrukDownstairs" not found: -25300 (The specified item could not be found in the keychain.)

After some googling I have came across a post suggesting that moving “System Preferences” from /Applications to /Applications/Utilities/ can be the cause.

Really ?! I mean - this application should be in utilities in the first place.

Well, anyway - I gave it a shout.

Result?

Now it works