On 16.10.2006, at 17:22, Christopher Elkins wrote:
> On Oct 16, 2006, at 2:55 PM, Christian Schaffner wrote:
>>> On 25.09.2006, at 11:31, Felix Ritter wrote:
>>>> Hi Mac users,
>>>> the new keychain support in subversion 1.4 is giving me a hard
>>>> time. I've some automated builds using svn that are started via
>>>> cron deamon (Mac OS 10.4.7). Since the cron jobs runs as a user
>>>> who never actually unlocked the keychain tool (e.g. by login
>>>> into a MacOS desktop session), the svn checkout or update stops
>>>> with prompting the user for a keyword to unlock the keychain
>>>> (the repository is accessed via https). Thus the whole build
>>>> process hangs. Any advice on how to use svn on MacOS in
>>>> automated processes like this would be greatly appreciated.
>> I am the author of the Fink svn packages, which I updated to svn
>> 1.4.0 recently. I am having exactly the same problem, since we run
>> an automated script that updates our internal test web site every
>> time we check something into svn. The user of the script is 'www'
>> which doesn't have a keychain. Did you find a solution to that
>> problem? Anybody else?
> One workaround, although somewhat inconvenient, is to use a 1.3
> client to authenticate for the first time (thereby caching the
> credentials in plain-text) and then use a 1.4 client for further
> access (which will use the cached credentials as-is).
Reading through the commit logs and mailing lists (there doesn't seem
to be too much documentation about this feature) it looks like adding
'--non-interactive' to svn commands should disable user interaction
with keychain too.
Read about the keychain API at:
Did you try that? (I can't try right now...)
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Oct 17 02:07:26 2006