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

Re: Bad revision with svn copy WC -> URL

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Tue, 10 Mar 2009 11:35:59 -0500

On Mar 10, 2009, at 10:58 AM, Laurent F. wrote:

> Hello,
> I found a bug in svn development library and it is reproduced with :
> - Python svn native swig interface
> - Python pysvn module interface
> - svn command line
> - Tortoise SVN
> When I am tagging a project for software delivery I am using 'svn
> copy' from my WC to tags/release_X
> The original WC has:
> - some files as in head revisions
> - some files in older revisions (but not modified)
> - [and deleted files; not wanted in the deliverable]
> If we look at the current revisions of each files of the result tag
> tree:
> - files copied from head revisions still have the same revision as in
> trunk ( ...as expected !) svn display n-1 log rev.
> - files copied from older revisions get revisions of the 'copy' call
> and not the revision they had in the trunk as I expected !.
> First, returning the copy revision for files copied from old revisions
> is not the expected revision.
> I would rather have the previous one in the log; that is the revision
> of the file in the trunk, just before the copy (n-1 in the log).
> But Second, why svn applies different rules for those two cases
> (always unmodified files) ?
> Furthermore, when the trunk change after the delivery, some files
> copied from the Head are now referencing older revisions, so revisions
> in tags directory are inconsistent;
> - some files returns the last log release (log(n))
> - other files returns the previous release (log(n-1)
> Can you confirm this is a bug ?

Can you provide a complete reproduction recipe, preferably in the form
of a shell script which demonstrates the bug through the commandline


Received on 2009-03-10 17:36:24 CET

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