Re: BUG? ... 'svn update' does not save authentication information

Jeff Putsch <putsch@mxim.com> writes:

> On Wed, Oct 09, 2002 at 06:31:43PM +0100, Philip Martin wrote:
> > Don't you get an error at this stage? Something like
> >
> > svn: Working copy not locked
> > svn: directory not locked (foo)
>
> Yes I get that error. Wish it would go away.

A novel approach to fixing bugs :)

Seriously, this is the cause of the problem, since it is an error that
occurs while storing auth info in the working copy. It's a little
tricky to solve it "properly" since storing auth info involves writing
to the working copy, and it can happen during an otherwise read-only
operation such as 'svn status', and one doesn't know in advance
whether it will be done.

> The data seems to have been
> pulled from the repository correctly.

In most cases I think it has. Storing auth info is usually done as a
last pass over the working copy tree, and it is that pass that is
generating the error.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org