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 ?
Laurent
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1303736
Received on 2009-03-10 17:28:30 CET