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

Re: access lock bug with 'svn up FILENAME'

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-10-23 16:00:41 CEST

Greg Stein <gstein@lyra.org> writes:

> This is probably simple, so I'm just sending here rather than an issue:
>
> [gstein@roshi cvs2svn]$ svn up
> U cvs2svn.py
> Updated to revision 3446.
> [gstein@roshi cvs2svn]$ svn up -r 3440 cvs2svn.py
> U cvs2svn.py
> subversion/libsvn_wc/lock.c:407: (apr_err=155005, src_err=0)
> svn: Working copy not locked
> svn: directory not locked (.)

That's not a canonical path. Ah, yes, svn_wc__do_update_cleanup is at
fault, it should not convert an empty path to "."

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 23 16:01:24 2002

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

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