"svn revert" corrupts working copy

2014-02-19 Thread Florin Avram
Hi, I found a situation when using "svn revert" seems to corrupt the working copy. In a working copy like this: - wc_root_dir -- directory --- file erase the directory from disk (not using SVN) and create a file with the same name instead. "svn status" will report: ~ directory ! directory/f

Re: "svn revert" corrupts working copy

2014-02-19 Thread Stefan Sperling
On Wed, Feb 19, 2014 at 12:50:02PM +0200, Florin Avram wrote: > Hi, > > I found a situation when using "svn revert" seems to corrupt the working > copy. In a working copy like this: > - wc_root_dir > -- directory > --- file > > erase the directory from disk (not using SVN) and create a file with

Re: "svn revert" corrupts working copy

2014-02-19 Thread Florin Avram
Well, this design corrupts the working copy and I cannot use it after. I doubt this is what you want... I ran into this issue by testing how "svn revert" behaves on different strange situations, but, at least theoretically, anybody can run into it. On 19.02.2014 13:02, Stefan Sperling wrote:

Re: "svn revert" corrupts working copy

2014-02-19 Thread Stefan Sperling
On Wed, Feb 19, 2014 at 01:07:49PM +0200, Florin Avram wrote: > Well, this design corrupts the working copy and I cannot use it after. I > doubt this is what you want... > I ran into this issue by testing how "svn revert" behaves on different > strange situations, but, at least theoretically, anybo

Re: "svn revert" corrupts working copy

2014-02-19 Thread Philip Martin
Stefan Sperling writes: > So, just move your file to a safe place, and run 'svn revert' again. In this case it's 'svn cleanup' after removing the obstruction. I suppose Subversion could check for such obstructions before creating the workqueue item and fail with some sort of "cannot revert" err

Re: "svn revert" corrupts working copy

2014-02-19 Thread Stefan Sperling
On Wed, Feb 19, 2014 at 12:17:06PM +, Philip Martin wrote: > Stefan Sperling writes: > > > So, just move your file to a safe place, and run 'svn revert' again. > > In this case it's 'svn cleanup' after removing the obstruction. Then I misunderstood the original problem report. Can you give

Re: "svn revert" corrupts working copy

2014-02-19 Thread Florin Avram
I think I know enough about Subversion and work with it for more than 5 years, so I know very well what obstructed and missing means, and that Subversion tries to not erase non-versioned data.I know only less about new SVN 1.8.x behavior, which I'm testing currently, and which in some situation

SVN import

2014-02-19 Thread Somashekarappa, Anup (CWM-NR)
Hi, We are trying to build the job in jenkins where it is trying to commit to SVN repository. The artifacts are getting committed successfully but we are seeing the below error in th output. svncommit: [echo] Commiting build v031_b84_r45185_DBOS-DTR-DB to http://SVNURL/svndata/path/bui

Re: "svn revert" corrupts working copy

2014-02-19 Thread Stefan Sperling
On Wed, Feb 19, 2014 at 02:52:48PM +0200, Florin Avram wrote: > I understand your point, but I have the feeling somewhere there is not a > correct decision and things can be improved. > > What I'm trying to say is that what Subversion does in this case is not too > obvious. Think to the following

Re: "svn revert" corrupts working copy

2014-02-19 Thread Florin Avram
I'm glad we found out a common point of view. A better error message, that indicates the cause (at least, in the provided example, it should be very clear what is triggering the error), would definitely help save some time, since no other command works to obtain other information about this wor

Re: "svn revert" corrupts working copy

2014-02-19 Thread Stefan Sperling
On Wed, Feb 19, 2014 at 05:09:11PM +0200, Florin Avram wrote: > Should I create a new issue regarding the error messages for this situation, > or someone else does this?! If you have time to do so that would be great. Thanks!

Re: SVN import

2014-02-19 Thread Philip Martin
"Somashekarappa, Anup (CWM-NR)" writes: > We are trying to build the job in jenkins where it is trying to commit > to SVN repository. > > The artifacts are getting committed successfully but we are seeing the > below error in th output. > > svncommit: > [echo] Commiting build v031_b84_r45185

RE: SVN import

2014-02-19 Thread Somashekarappa, Anup (CWM-NR)
Hi, I have given the full access but getting the same error. -rwxrwxrwx1 apache apache 2069504 Feb 16 19:24 rep-cache.db Thanks & Regards, Anup T S -Original Message- From: Philip Martin [mailto:philip.mar...@wandisco.com] Sent: 2014, February, 19 11:16 AM To: Somashekarappa, An

issue validation: bug, Memcached+FullText cache is totally broken in svnserve 1.8.5

2014-02-19 Thread Anatoly Orlov
Hi. Preface: We are trying to migrate to svn 1.8.5, with very large repository(~700G), with heavy load(1000+ developers, 200+ test servers) since we use svn+ssh memcached is reasonable cache system for us. Problem: Enabling memcached with full text caches in version 1.8.5. causes svnserve -t s

Re: issue validation: bug, Memcached+FullText cache is totally broken in svnserve 1.8.5

2014-02-19 Thread Stefan Sperling
On Wed, Feb 19, 2014 at 10:03:47PM +0400, Anatoly Orlov wrote: > Hi. > > Preface: > We are trying to migrate to svn 1.8.5, with very large repository(~700G), > with heavy load(1000+ developers, 200+ test servers) since we use svn+ssh > memcached is reasonable cache system for us. > > Problem: >