FW: bug: when merging back newly added binary files, a conflict is issued

Hi,

we've been running into some problems with tortoiseSVN recently where binary
files such as images that have been added to a subbranch create a conflict
when the branch is merged back into the trunk. tortoiseSVN uses the
commandline client code of SVN, so i was told to forward the bug to you.

the error occurred with TSVN 1.2.0, which apparently uses the SVN 1.2.0
codebase.

it usually goes as this:
- branch /trunk to /branches/newbranch
- check out /branches/newbranch to a new directory
- add a new binary file (test.png) to /branches/newbranch
- commit the changes
- merge the trunk into this branch
- go back to the directory where you have checked out /trunk
- merge /branches/newbranch into /trunk

no conflict is being displayed in the gui, but as soon as you want to check
in your merge, you get a conflict displayed with test.png. a zero byte file
named test.png.r0 exists along with test.png and test.png.r<revision where
test.png was committed>. the conflict can be solved by deleting both .r*
files. test.png contains the intended image.

note that test.png has never existed in the project before.

the expected behaviour is that no conflict is generated, instead the new
binary file is properly added to the local working image of the trunk.

it is possible that this scenario isn't 1:1 reproducible, but we encountered
above mentioned symptoms a several times in relation to this. unfortunately
we had no time digging into this issue further so far.

please let me know if you have maybe already have an idea what it could be,
or if we shall help by submitting a 100% reproduce?

Best regards,

Leonard Ritter
Development

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 12 18:51:36 2005