Re: Xcode 2.1 CVS access non-functional.
Re: Xcode 2.1 CVS access non-functional.
- Subject: Re: Xcode 2.1 CVS access non-functional.
- From: Brad BARCLAY <email@hidden>
- Date: Fri, 10 Jun 2005 02:09:17 -0400
On Jun 9, 2005, at 19:17, Rob Lockstone wrote:
Hi Rob:
Well, that sucks. I don't have any helpful suggestions. But,
obviously, you should file a bug if you haven't already. And if/
when you do, please mention that CVS access is not totally broken.
I am currently using it successfully with a non-SourceForge
repository using public-private keypairs (with null passphrases),
using usr/bin/cvs, with the "use ssh instead of rsh" checkbox
UNchecked, and I'm not using SSHKeychain since I don't have a
passphrase to worry about. (Perhaps the problem lies within the
passphrase support in Xcode 2.1.)
Well, it's good to know it works for someone out there :).
I'm probably going to have to open a bug report on this one. I
went through all of the .xcodeproj files manually to ensure none of
the settings were munged, and also tried to create a new project to
see if that would work, but no go.
On a whim I decided to wrap the call to cvs into a shell script
to force the environment variables on it, and it still doesn't work
right. However, it did allow me to dump out the environment Xcode is
using, and I seem to have found the problem.
It appears that Xcode is setting the SSH_AUTH_SOCK environment
variable. It is setting this variable to something other than what
SSHKeychain uses. If I change this to the proper value in my cvs
wrapper script, the CVS command authenticates (although things still
aren't working properly, as Xcode isn't showing any status changes
for my files -- I think this is because I'm not returning the return
code for the real cvs command from within my script. Shell scripting
isn't my forte, so I'm going to have to look it up (I thought "return
$?" would be correct, but the shell didn't like that).
If I can get the script working, I have my own work-around. I
may also try disabling SSHKeychain -- it could be that Xcode is now
trying to use ssh-agent, and that this is conflicting with SSHKeychain.
...and there we have the problem. Xcode 2.1 now starts ssh-
agent for you, and then tries to use it for SSH authentication. I
guess that means that I'm going to need to configure ssh-agent, and
use it for Xcode instead of SSHKeychain.
I think I solved my own problem. I may still file a bug report
-- I'd prefer it if Xcode allowed me to manage this myself, and not
force ssh-agent onto me (SSHKeychain is nice because it lives in the
menu and makes it easy to add/remove keys, authorize keys, and set-up
SSH tunnels). Thanks for the input!
Brad BARCLAY,
Lead Developer & Project Administrator,
The jSyncManager Project.
=-=-=-=-=-=-=-=-=-=
From the Mac OS X Desktop of Brad BARCLAY
E-Mail: email@hidden Web: http://www.jsyncmanager.org
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden