[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN commands fail on Mac OS X 10.5 (Leopard) when the --non-interactive option is used

From: Greg Troxel <gdt_at_ir.bbn.com>
Date: Tue, 10 Feb 2009 10:07:48 -0500

Brandon Humphrey <bhumphrey_at_divxcorp.com> writes:

> svn ls https://svn/svn/SomeRepository/ <-- Completes successfully
> without interaction because credentials are already cached
> svn ls -non-interactive https://svn/svn/SomeRepository/ <-- Error,
> svn: PROPFIND of '/svn/SomeRepository': authorization failed
> (https://svn)
>
> I've located previous discussions around this issue, including a
> documented Subversion bug.
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=3059+
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageI
> d=4237
> http://www.nabble.com/Possible-Bug-with-%22--non-interactive%22-mode-on-
> OS-X-Leopard-to14338652.html

> The SVN Issue (#3059) still has a status of NEW, but it has not been
> updated since 2007. Does anyone know of a work-around or patch
> available for this problem?

I am having the same problem, with svn 1.5.4 and 1.5.5 on OS X 10.5.x
(for all versions I've tried). I am using svn built from pkgsrc. OS X
does prompt me to allow keychain access every time I update svn.

As a workaround it would be nice for svn to separate "don't ask keychain
to be non-interactive" and "don't prompt for merge behavior". I use
this switch in merge scripts to do all the merging to be cleaned up
later, and have credentials, so it's really the merge prompting that I
am trying to avoid.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1134491

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].

  • application/pgp-signature attachment: stored
Received on 2009-02-10 16:11:13 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.