Bug while trying to handle a property conflict caused by update
From: Alexander Sinyushkin <Alexander.Sinyushkin_at_svnkit.com>
Date: Wed, 29 Jul 2009 22:58:36 +0200
Hello,
I'd like to report two problems.
First of all, imagine you've two similar working copies of trunk from
1. And here comes the first problem. If you run 'svn up --accept base'
2. If instead of running an update with the key --accept you run simply
Conflict for property 'xx' discovered on 'A'.
This leaves the wc in an incomplete state:
I've attached scripts for both of the two use-cases.
---- Alexander Sinyushkin, TMate Software, http://svnkit.com/ - Java [Sub]Versioning Library! ------------------------------------------------------ http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2376718
#!/bin/bash
mkdir testReposImport
svnadmin create testRepos
svn import testReposImport file:///`pwd`/testRepos -m "initial import"
svn co file:///`pwd`/testRepos wc1
cd wc1
#set property xx on A
cd ..
cd wc2
#set property xx on A but with different value than is in the repository
#update wc2 witch --accept = base
#now update back to revision where no property xx exists on A
#!/bin/bash
mkdir testReposImport
svnadmin create testRepos
svn import testReposImport file:///`pwd`/testRepos -m "initial import"
svn co file:///`pwd`/testRepos wc1
cd wc1
#set property xx on A
cd ..
cd wc2
#set property xx on A but with different value than is in the repository
#run update and choose first (df) and then (r)
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.