subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Sachs <jmsa...@gmail.com>
Subject Re: bug in mixed-version detection + single-file externals
Date Tue, 22 Feb 2011 16:07:38 GMT
>> If you could write a script that starts with an empty repository, gets a
>> working copy, and runs svn commands until the problem triggers, that would
>> help greatly (and avoids any ambiguity in the problem description!).
>
> See attached python script (tested only on WinXP + Python 2.6.5)
>

Script output:
=========
C:\tmp\svn\ext1>python trybug.py
Checked out revision 0.
A         C:\tmp\svn\ext1\working\foo
A         C:\tmp\svn\ext1\working\foo\trunk
A         C:\tmp\svn\ext1\working\bar
A         C:\tmp\svn\ext1\working\bar\trunk
A         working\foo\trunk\blah.txt
Adding         working\bar
Adding         working\bar\trunk
Adding         working\foo
Adding         working\foo\trunk
Adding         working\foo\trunk\blah.txt
Transmitting file data .
Committed revision 1.
Sending        working\foo\trunk\blah.txt
Transmitting file data .
Committed revision 2.
Sending        working\foo\trunk\blah.txt
Transmitting file data .
Committed revision 3.
property 'svn:externals' set on 'working\bar\trunk'
Sending        working\bar\trunk

Committed revision 4.

Fetching external item into 'working\bar\trunk\blah.txt'
E    working\bar\trunk\blah.txt
Updated external to revision 1.

Updated to revision 4.
1:4

=========
This just creates a sample repos + working copy and illustrates the
problem with svnversion, which should print out "4" but instead prints
out "1:4".

I didn't create a testcase for performing a merge, that's more complex
than I can deal with right now.

Mime
View raw message