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

RE: Removed directory and working copy issues

From: Robert Swarbrick <robert.swarbrick_at_asg.com>
Date: 2005-08-11 08:37:13 CEST

Did you try "svn delete" to tell subversion you really wanted the
directory removed, as opposed to some accidental deletion on a working
copy getting committed back to the repository?

The "basic work cycle" in Ch3 of the manual discusses this.


-----Original Message-----
From: Martin Novak [mailto:mn@puakma.net]
Sent: 11 August 2005 03:58
To: users@subversion.tigris.org
Subject: Removed directory and working copy issues

Hello, I have bug for subversion, I tried to look at the current bugs,
and nothing found, so sorry if it's duplicate. To OS: I'm using 1.2.1 on

MacOSX 10.4.

The problem occurs when I manually remove some directory (using outside
tools - eg command line 'rm'), and then I try to commit the whole
project to the server (using command: 'svn ci' or even in subclipse).
svn doesn't recognize directory remove, and it's writing me that:

mn@jablicko-3 puakma.ide $ svn ci
subversion/libsvn_client/commit.c:832: (apr_err=155005)
svn: Commit failed (details follow):
subversion/libsvn_wc/lock.c:677: (apr_err=155005)
svn: Working copy '/Users/mn/Puakma/puakma.ide/final' is missing or not

the deal is that information about directory 'final' is stored in
'/Users/mn/Puakma/puakma.ide/.svn/entries' file, and when commiting svn
is not able to recognize that dir was removed, and remove it from
repository automatically which should be imho doing...


P.S. I'm not subscribed to the list or what are you using, so please
forward me any answers or subscribe me

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 11 08:37:25 2005

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.