Evan pointed out the clues to what people are seeing in the previous post, but unless LJ goes back to what it was doing before, the client is going to be broken until we get a new version out. This is kinda not fun, and without any warning.

However, a weekend is coming up and maybe I can whip out a new version. This means that Bob, Fraser, and everyone else better get their commits in. ;)

Comments

Unfortunately, I haven't been able to figure out how to get @#$% Project Builder to commit stuff for me! It keeps on telling that "commit" requires write access to the repository. Which I supposedly have.

This might be related to the fact that I originally checked it out anonymously, but PB offers no way to change who I'm talking to the server as, and trying to figure out command-line CVS from the man page just makes my head hurt. Being behind a firewall/router might be part of the problem, too...

I've spent the past couple hours beating against this, and am giving up: you can find the modified iTunes.m here.

Someday I'll have to try and get this working, but right now... I'm giving up and going shopping for shoes.

In the CVS directories (yes, each of them) you will find a file called "Root". This is what CVS uses so you dont have to define the -d again. So if you go through and change each of these files to contain:

Then you open the PB icon, and it should ask you things likefor your sf password when it checks the cvs status... then itshould save it in your keychain and leave you alone. There'salso some thing I was using a while back from virgintracker thatwould do the magic of this before PB ssh support was fully integrated.

I finally got it to check in, by using the command line to check it in myself. PB just doesn't want to do it for me; it keeps on timing out.

For future reference (mine, and anyone else who joins up and can't get CVS to work), this seems to be the sequence of commands. I haven't done anything to the Unix side of things; if you've switched to a different shell or something, things may be different.

Getting the source as a developer:

%setenv CVS_RSH ssh%cd ~/Documents (or wherever you want to keep the thing)%cvs -z3 -d:ext:username@cvs.sourceforge.net:/cvsroot/ijournal co iJournal(this snags a copy of it all; if you've already done so anonymously, editing the CVS/Root files as Gnarf suggests above does seem to work. There's more than one CVS directory created in the project, so check carefully.)

You will be asked for your SF password, then you'll grab everything.

Comitting changes:

%setenv CVS_RSH ssh%cd ~/Documents%cvs -z3 -d:ext:username@cvs.sourceforge.net:/cvsroot/ijournal commit iJournal/foobar.m(whatever file you've worked on; I think you can just commit iJournal, and cvs will see what's changed, but I have not tested this.)

You'll be asked for your SF password, then thrown into one of those scary textmode editors. Type a succinct description of your changes, then type esc, :x, return. The changes are then sent in.

I doubt this is the most efficient way to do this, but it is a way that worked for me when all else failed. Dealing with the Unix command line never fails to give me a headache...