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

Re: Inconsistent svn cp error messages and behaviour, recovering to earlier revision doesn't work

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2006-09-06 23:12:29 CEST

On 9/5/06, Harri Järvi <harri.jarvi@tut.fi> wrote:
> Hello,
>
> I'm using svn version 1.2.3 (r15833).
>
> Reverting to an earlier revision of a file doesn't work. And there are
> inconsistent error messages when trying to do so.
>
> The following is an excerpt of what goes on:
>
> 1$ svn rm file.txt
> D file.txt
>
> 2$ svn cp -r 349 svn+ssh://host/repository/trunk/file.txt file.txt
> svn: Entry for 'build.xml' exists (though the working file is missing)
>
> 3$ svn cp file2.txt file.txt
> svn: 'build.xml' is scheduled for deletion; it must be committed before
> being overwritten
>
> 4$ svn add file.txt
> svn: 'file.txt' not found
>
> 5$ touch file.txt
>
> 6$ svn add file.txt
> A file.txt
>
>
> The error messages in 2$ and 3$ are different. The error messages are
> inconsistent.
>
> Adding a new file in 6$ works and there is no error message, but copying
> from an earlier revision or another file (2$ and 3$) leads to error
> messages. This is incosistent behaviour.
>
> Why isn't recovering to (copying from) an earlier revision possible
> within one revision? Is it a good idea to require a "svn commit" in
> between of steps 1$ and 2$. This leads to an unwanted intermediate
> revision with the file missing?
>
> Is this a bug?

Maybe, maybe not, but it was a problem with the working copy library
not being able to represent 'replace-with-history'. This has (amongst
many other WC library improvements) been fixed in the upcoming 1.4.

HTH,

Erik.
Received on Wed Sep 6 23:39:14 2006

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