You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Murli Varadachari <mv...@facebook.com> on 2009/03/05 04:26:27 UTC
Trunk to branch merge error on renamed component
I am trying to merge from trunk to branch and I get this error "svn: File not found: revision 148570, path '/branches/yp/www/html/intern/ods/alarms'. The command I am using
is "svn merge -r144695:148570 svn+ssh://prod/trunk/www <WC-of-//prod/branches/yp/www>".
The branch in question '/branches/yp/www' was created from '/trunk/www' @140482. Subsequently I did a merge from /trunk and from a couple of other branches. I am now trying to merge from the trunk to branch one last time before I re-integrate back to trunk. However I am stuck with the above issue. A substantial number of files /dirs etc were merged or added successfully before it burped.
A thorough examination of the history of the trunk indicates that @rev# 145142 /trunk/www/html/alerts was moved / renamed to '/trunk/www/html/intern/ods/alarms'. Are there issues with svn merge w.r.t its ability to handle renamed components. I am currently using svn 1.5.3 .
The history of this particular merge can be seem from svn:mergeinfo properties
svn:mergeinfo : ==>
/prod/branches/v3x/www:140558-142418
/prod/branches/xx/www:83462-126155
/prod/releases/r126219-10122008/www:126613,126628,126633-126634
/prod/trunk/www:140483-144695
Any help will be appreciated.
Cheers
murli
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1270364
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Trunk to branch merge error on renamed component
Posted by Murli Varadachari <mv...@facebook.com>.
I removed the double-delete patch [ http://svn.haxx.se/dev/archive-2008-02/0883.shtml ] and recompiled subversion 1.5.6 without this patch.
At this point I was able to commit all my changes successfully [ with some weird warnings]. However this patch is needed so I am not sure I can remove this
patch in my production environment.
Environment:
Svn 1.5.6, Linux FC4, Repository on shared storage.
The sequence of operation was as follows:
1: Created a new branch
svn cp -m "making branch from prod/trunk 140481" svn+ssh://prod /trunk@140481 svn+ssh://prod/branches/yp/www
2: Merged the newer revisions from trunk to WC-branch
svn merge -r140481:148570 svn+ssh://prod/trunk/www .
This merge include the following history
(a) intern/alerts was renamed to intern/ods/alarms
(b) a new directory / file created again intern/alerts/handlers/alerts.php
Svn status at this point in my branch-WC ~/www :
=======================>>
R + intern/alerts
D + intern/alerts/search.phpt
D + intern/alerts/ajax
D + intern/alerts/ajax/delete_sub.php
D + intern/alerts/css
D + intern/alerts/css/alerts.css
R + intern/alerts/handlers
R + intern/alerts/handlers/alerts.php
D + intern/alerts/js
D + intern/alerts/js/typeahead.js
A + intern/ods/alarms
A + intern/ods/alarms/search.phpt
A + intern/ods/alarms/ajax
A + intern/ods/alarms/ajax/delete_sub.php
A + intern/ods/alarms/css
A + intern/ods/alarms/css/alerts.css
A + intern/ods/alarms/handlers
A + intern/ods/alarms/handlers/alerts.php
A + intern/ods/alarms/js
A + intern/ods/alarms/js/typeahead.js
==>>
3: Committed these changes:
..... Commit completed
svn: Error bumping revisions post-commit (details follow):
svn: Directory '/tmp/MV/www/intern/alerts/js' is missing
svn: Directory '/tmp/MV /www/intern/alerts/js' is missing
These messages are spurious. I did a fresh checkout of the branch and the committed files were GOOD.
4: Now I repeat the same sequence of operations with the "double delete" PATCH built into subversion [ svnserve ]. The commit fails with
The error
svn: File not found: revision 148570, path '/branches/yp/www/intern/ods/alarms'
I understand that 1.6.0 has the double delete issue fixed. In which I would expect the commit to fail unless the fix is different from the patch I received.
Appreciate if some developers can take a look at this issue and let me know what to do next
Cheers
murli
On 3/8/09 12:22 PM, "Internal Use" <mv...@facebook.com> wrote:
Unfortunately It is not possible to reproduce this problem in an isolated test environment - I am sure the merge issues were resolved in 1.5.6 [ confirmed ] and the commits went through in your unit / regression tests. That is not in dispute.
However the problem does come up in our existing repository [ 100GB ] which has a considerable history and not reproducible in any meaningful way via the test script you have provided - as of today another 3 /4 developers have hit the same problem [ specially those who had created these branches prior to the renaming of the component ].
I did run a couple of more tests --
-- created a completely new branch from trunk based on the original branch point @145142
-- merged and committed all changes from trunk to the point just prior to the renaming of the components. This was OK.
-- next I just picked up a single revision from trunk [ where the component was renamed ] and merged it to the updated branch. The commit failed once again.
This does seem to be a server side problem. The only change w.r.t to my server setup [ 1.5.6 ] was the addition the double deletion patch to prevent empty revisions.
http://svn.haxx.se/dev/archive-2008-02/0883.shtml
>>Subversion should cancel a commit that includes the deletion of a file
>> or directory that has already been deleted in the repository.
However in this case the dir in question has not been deleted earlier. Any ways I am going to recompile svnserve without this patch and see if that helps.
It would be useful if I can get a patch that allows svnserve to spit out more diagnostics for this specific type of error. I could recompile svnserver, generate the error and send you the output.
Cheers
murli
On 3/6/09 11:50 AM, "Stefan Sperling" <st...@elego.de> wrote:
On Fri, Mar 06, 2009 at 09:01:20AM -0800, Murli Varadachari wrote:
> I personally ran this with svn 1.5.6. As I mentioned earlier this
> took me past the merge but crashed on commit.
> A developer here used 1.6.0-rc2 to test the same on a different
> host. [ I asked him to do so that would eliminate any environmental
> / host specific issues]. He got the same results.!!
So it looks like the problem is caused by a directory
being renamed on trunk, and merging this rename into
the branch, right?
I can reproduce the problem using the script below, with
1.5.6, some recent build from the 1.6.x branch, and trunk.
But in all cases svn does not stop me from committing
after running 'svn update'.
Is this what you are seeing, too? If not, you have a different
situation, and we need more information to reproduce this
problem locally. Can you try to tweak the script pasted below
so that it does reliably recreate your specific problem?
Thanks,
Stefan
1.5.6 allows me to commit after updating:
--- Merging r2 through r5 into '.':
A epsilon/gamma
A epsilon/gamma/delta
D gamma
$ svn ci -m sync with trunk renamebug/branch
Sending renamebug/branch
svn: Commit failed (details follow):
svn: Directory '/branch' is out of date
$ cd renamebug/branch/
$ svn up
At revision 5.
$ svn ci -mm
Sending .
Adding epsilon/gamma
Adding epsilon/gamma/delta
Deleting gamma
Committed revision 6.
1.6.x and trunk detect a tree conflict and I can commit
after I mark it resolved:
--- Merging r2 through r5 into '.':
A epsilon/gamma
A epsilon/gamma/delta
D gamma
$ svn ci -m sync with trunk renamebug/branch
Sending renamebug/branch
subversion/libsvn_client/commit.c:867: (apr_err=160028)
svn: Commit failed (details follow):
subversion/libsvn_repos/commit.c:124: (apr_err=160028)
svn: Directory '/branch' is out of date
$ cd renamebug/branch/
$ svn up
C gamma
At revision 5.
Summary of conflicts:
Tree conflicts: 1
$ svn status
M .
D C gamma
> local delete, incoming edit upon update
D gamma/delta
A + epsilon/gamma
A + epsilon/gamma/delta
$ svn resolved gamma
Resolved conflicted state of 'gamma'
$ svn ci -mm
Sending .
Adding epsilon/gamma
Adding epsilon/gamma/delta
Deleting gamma
Committed revision 6.
renamebug.sh:
#!/bin/sh
set -e
cwd=`pwd`
basename=`basename $0`
scratch_area="`echo $basename | sed -e s/\.sh$//`"
repos=$scratch_area/repos
trunk=$scratch_area/trunk
branch=$scratch_area/branch
trunk_url=file:///$cwd/$repos/trunk
branch_url=file:///$cwd/$repos/branch
set -x
rm -rf $scratch_area
mkdir -p $scratch_area
mkdir -p $trunk
echo alpha > $trunk/alpha
echo beta > $trunk/beta
mkdir $trunk/gamma
echo delta > $trunk/gamma/delta
mkdir $trunk/epsilon
echo zeta > $trunk/epsilon/zeta
svnadmin create $cwd/$repos
svn import $trunk $trunk_url -m "importing project tree"
svn copy $trunk_url $branch_url -m "creating branch"
rm -rf $trunk
svn checkout $trunk_url $trunk
svn checkout $trunk_url ${trunk}2
svn checkout $branch_url $branch
svn mv $trunk/gamma $trunk/epsilon/
svn ci -m "moved dir gamma into epsilon" $trunk
echo "alpha, modified" > $branch/alpha
svn ci -m "changed alpha" $branch
echo "delta, modified" > $branch/gamma/delta
svn ci -m "changed delta" $branch
(cd $branch && svn merge $trunk_url)
# this causes an out-of-date error
svn ci -m "sync with trunk" $branch
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1293334
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Trunk to branch merge error on renamed component
Posted by Murli Varadachari <mv...@facebook.com>.
Unfortunately It is not possible to reproduce this problem in an isolated test environment - I am sure the merge issues were resolved in 1.5.6 [ confirmed ] and the commits went through in your unit / regression tests. That is not in dispute.
However the problem does come up in our existing repository [ 100GB ] which has a considerable history and not reproducible in any meaningful way via the test script you have provided - as of today another 3 /4 developers have hit the same problem [ specially those who had created these branches prior to the renaming of the component ].
I did run a couple of more tests --
-- created a completely new branch from trunk based on the original branch point @145142
-- merged and committed all changes from trunk to the point just prior to the renaming of the components. This was OK.
-- next I just picked up a single revision from trunk [ where the component was renamed ] and merged it to the updated branch. The commit failed once again.
This does seem to be a server side problem. The only change w.r.t to my server setup [ 1.5.6 ] was the addition the double deletion patch to prevent empty revisions.
http://svn.haxx.se/dev/archive-2008-02/0883.shtml
>>Subversion should cancel a commit that includes the deletion of a file
>> or directory that has already been deleted in the repository.
However in this case the dir in question has not been deleted earlier. Any ways I am going to recompile svnserve without this patch and see if that helps.
It would be useful if I can get a patch that allows svnserve to spit out more diagnostics for this specific type of error. I could recompile svnserver, generate the error and send you the output.
Cheers
murli
On 3/6/09 11:50 AM, "Stefan Sperling" <st...@elego.de> wrote:
On Fri, Mar 06, 2009 at 09:01:20AM -0800, Murli Varadachari wrote:
> I personally ran this with svn 1.5.6. As I mentioned earlier this
> took me past the merge but crashed on commit.
> A developer here used 1.6.0-rc2 to test the same on a different
> host. [ I asked him to do so that would eliminate any environmental
> / host specific issues]. He got the same results.!!
So it looks like the problem is caused by a directory
being renamed on trunk, and merging this rename into
the branch, right?
I can reproduce the problem using the script below, with
1.5.6, some recent build from the 1.6.x branch, and trunk.
But in all cases svn does not stop me from committing
after running 'svn update'.
Is this what you are seeing, too? If not, you have a different
situation, and we need more information to reproduce this
problem locally. Can you try to tweak the script pasted below
so that it does reliably recreate your specific problem?
Thanks,
Stefan
1.5.6 allows me to commit after updating:
--- Merging r2 through r5 into '.':
A epsilon/gamma
A epsilon/gamma/delta
D gamma
$ svn ci -m sync with trunk renamebug/branch
Sending renamebug/branch
svn: Commit failed (details follow):
svn: Directory '/branch' is out of date
$ cd renamebug/branch/
$ svn up
At revision 5.
$ svn ci -mm
Sending .
Adding epsilon/gamma
Adding epsilon/gamma/delta
Deleting gamma
Committed revision 6.
1.6.x and trunk detect a tree conflict and I can commit
after I mark it resolved:
--- Merging r2 through r5 into '.':
A epsilon/gamma
A epsilon/gamma/delta
D gamma
$ svn ci -m sync with trunk renamebug/branch
Sending renamebug/branch
subversion/libsvn_client/commit.c:867: (apr_err=160028)
svn: Commit failed (details follow):
subversion/libsvn_repos/commit.c:124: (apr_err=160028)
svn: Directory '/branch' is out of date
$ cd renamebug/branch/
$ svn up
C gamma
At revision 5.
Summary of conflicts:
Tree conflicts: 1
$ svn status
M .
D C gamma
> local delete, incoming edit upon update
D gamma/delta
A + epsilon/gamma
A + epsilon/gamma/delta
$ svn resolved gamma
Resolved conflicted state of 'gamma'
$ svn ci -mm
Sending .
Adding epsilon/gamma
Adding epsilon/gamma/delta
Deleting gamma
Committed revision 6.
renamebug.sh:
#!/bin/sh
set -e
cwd=`pwd`
basename=`basename $0`
scratch_area="`echo $basename | sed -e s/\.sh$//`"
repos=$scratch_area/repos
trunk=$scratch_area/trunk
branch=$scratch_area/branch
trunk_url=file:///$cwd/$repos/trunk
branch_url=file:///$cwd/$repos/branch
set -x
rm -rf $scratch_area
mkdir -p $scratch_area
mkdir -p $trunk
echo alpha > $trunk/alpha
echo beta > $trunk/beta
mkdir $trunk/gamma
echo delta > $trunk/gamma/delta
mkdir $trunk/epsilon
echo zeta > $trunk/epsilon/zeta
svnadmin create $cwd/$repos
svn import $trunk $trunk_url -m "importing project tree"
svn copy $trunk_url $branch_url -m "creating branch"
rm -rf $trunk
svn checkout $trunk_url $trunk
svn checkout $trunk_url ${trunk}2
svn checkout $branch_url $branch
svn mv $trunk/gamma $trunk/epsilon/
svn ci -m "moved dir gamma into epsilon" $trunk
echo "alpha, modified" > $branch/alpha
svn ci -m "changed alpha" $branch
echo "delta, modified" > $branch/gamma/delta
svn ci -m "changed delta" $branch
(cd $branch && svn merge $trunk_url)
# this causes an out-of-date error
svn ci -m "sync with trunk" $branch
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1291179
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Trunk to branch merge error on renamed component
Posted by Stefan Sperling <st...@elego.de>.
On Fri, Mar 06, 2009 at 09:01:20AM -0800, Murli Varadachari wrote:
> I personally ran this with svn 1.5.6. As I mentioned earlier this
> took me past the merge but crashed on commit.
> A developer here used 1.6.0-rc2 to test the same on a different
> host. [ I asked him to do so that would eliminate any environmental
> / host specific issues]. He got the same results.!!
So it looks like the problem is caused by a directory
being renamed on trunk, and merging this rename into
the branch, right?
I can reproduce the problem using the script below, with
1.5.6, some recent build from the 1.6.x branch, and trunk.
But in all cases svn does not stop me from committing
after running 'svn update'.
Is this what you are seeing, too? If not, you have a different
situation, and we need more information to reproduce this
problem locally. Can you try to tweak the script pasted below
so that it does reliably recreate your specific problem?
Thanks,
Stefan
1.5.6 allows me to commit after updating:
--- Merging r2 through r5 into '.':
A epsilon/gamma
A epsilon/gamma/delta
D gamma
$ svn ci -m sync with trunk renamebug/branch
Sending renamebug/branch
svn: Commit failed (details follow):
svn: Directory '/branch' is out of date
$ cd renamebug/branch/
$ svn up
At revision 5.
$ svn ci -mm
Sending .
Adding epsilon/gamma
Adding epsilon/gamma/delta
Deleting gamma
Committed revision 6.
1.6.x and trunk detect a tree conflict and I can commit
after I mark it resolved:
--- Merging r2 through r5 into '.':
A epsilon/gamma
A epsilon/gamma/delta
D gamma
$ svn ci -m sync with trunk renamebug/branch
Sending renamebug/branch
subversion/libsvn_client/commit.c:867: (apr_err=160028)
svn: Commit failed (details follow):
subversion/libsvn_repos/commit.c:124: (apr_err=160028)
svn: Directory '/branch' is out of date
$ cd renamebug/branch/
$ svn up
C gamma
At revision 5.
Summary of conflicts:
Tree conflicts: 1
$ svn status
M .
D C gamma
> local delete, incoming edit upon update
D gamma/delta
A + epsilon/gamma
A + epsilon/gamma/delta
$ svn resolved gamma
Resolved conflicted state of 'gamma'
$ svn ci -mm
Sending .
Adding epsilon/gamma
Adding epsilon/gamma/delta
Deleting gamma
Committed revision 6.
renamebug.sh:
#!/bin/sh
set -e
cwd=`pwd`
basename=`basename $0`
scratch_area="`echo $basename | sed -e s/\.sh$//`"
repos=$scratch_area/repos
trunk=$scratch_area/trunk
branch=$scratch_area/branch
trunk_url=file:///$cwd/$repos/trunk
branch_url=file:///$cwd/$repos/branch
set -x
rm -rf $scratch_area
mkdir -p $scratch_area
mkdir -p $trunk
echo alpha > $trunk/alpha
echo beta > $trunk/beta
mkdir $trunk/gamma
echo delta > $trunk/gamma/delta
mkdir $trunk/epsilon
echo zeta > $trunk/epsilon/zeta
svnadmin create $cwd/$repos
svn import $trunk $trunk_url -m "importing project tree"
svn copy $trunk_url $branch_url -m "creating branch"
rm -rf $trunk
svn checkout $trunk_url $trunk
svn checkout $trunk_url ${trunk}2
svn checkout $branch_url $branch
svn mv $trunk/gamma $trunk/epsilon/
svn ci -m "moved dir gamma into epsilon" $trunk
echo "alpha, modified" > $branch/alpha
svn ci -m "changed alpha" $branch
echo "delta, modified" > $branch/gamma/delta
svn ci -m "changed delta" $branch
(cd $branch && svn merge $trunk_url)
# this causes an out-of-date error
svn ci -m "sync with trunk" $branch
Re: Trunk to branch merge error on renamed component
Posted by Murli Varadachari <mv...@facebook.com>.
On 3/6/09 7:29 AM, "Stefan Sperling" <st...@elego.de> wrote:
On Thu, Mar 05, 2009 at 06:45:52PM -0800, Murli Varadachari wrote:
>
> I just tried using subversion 1.5.6 as well as 1.6
> It did go past the previous point of failure and the merge completed
> OK. However it fails on commit with the following error message =>>
> ==>>
> svn: Commit failed (details follow):
> svn: File or directory '/branches/yp/www/html/intern/alerts/ajax' is
> out of date
> ==>>
>>>With which version of Subversion did this error happen?
>>>With 1.5.6, or 1.6.0-rc3, or both? Please be precise.
I personally ran this with svn 1.5.6. As I mentioned earlier this took me past the merge but crashed on commit.
A developer here used 1.6.0-rc2 to test the same on a different host. [ I asked him to do so that would eliminate any environmental / host specific issues]. He got the
same results.!!
> As far as I can see the branch WC is fully up-to date. Problem still
> seems to be related to the moved / renamed component
> "trunk/www/html/intern/alerts" -> "trunk/www/html/intern/ods/alarms" .
> Is it possible the bug fix for merge may need a corresponding fix for
> commit?
>>>Did you really try to run 'svn update' after you got the out-of-date error?
>>>What happens if you run 'svn update'?
Yes - I ran svn update maybe a dozen times - I get "At revision 149313." each time --- .
Just before sending this reply I checked out a fresh copy, ran through the same merge sequence and tried to commit. [ with svn 1.5.6 ]. Once again I get this same error message.
It does appear to be a bug.
Right now I am stuck!
>>>Stefan
murli
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1278125
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Trunk to branch merge error on renamed component
Posted by Stefan Sperling <st...@elego.de>.
On Thu, Mar 05, 2009 at 06:45:52PM -0800, Murli Varadachari wrote:
>
> I just tried using subversion 1.5.6 as well as 1.6
> It did go past the previous point of failure and the merge completed
> OK. However it fails on commit with the following error message =>>
> ==>>
> svn: Commit failed (details follow):
> svn: File or directory '/branches/yp/www/html/intern/alerts/ajax' is
> out of date
> ==>>
With which version of Subversion did this error happen?
With 1.5.6, or 1.6.0-rc3, or both? Please be precise.
> As far as I can see the branch WC is fully up-to date. Problem still
> seems to be related to the moved / renamed component
> "trunk/www/html/intern/alerts" -> "trunk/www/html/intern/ods/alarms" .
> Is it possible the bug fix for merge may need a corresponding fix for
> commit?
Did you really try to run 'svn update' after you got the out-of-date error?
What happens if you run 'svn update'?
Stefan
Re: Trunk to branch merge error on renamed component
Posted by Murli Varadachari <mv...@facebook.com>.
I just tried using subversion 1.5.6 as well as 1.6
It did go past the previous point of failure and the merge completed OK. However it fails on commit with the following error message =>>
==>>
svn: Commit failed (details follow):
svn: File or directory '/branches/yp/www/html/intern/alerts/ajax' is out of date
==>>
As far as I can see the branch WC is fully up-to date. Problem still seems to be related to the moved / renamed component
"trunk/www/html/intern/alerts" -> "trunk/www/html/intern/ods/alarms" .
Is it possible the bug fix for merge may need a corresponding fix for commit?
Cheers
murli
On 3/5/09 4:35 AM, "Mark Phippard" <ma...@gmail.com> wrote:
All known causes of this problem were fixed in 1.5.5 client. Try 1.5.5/1.5.6.
Mark
On Wed, Mar 4, 2009 at 11:26 PM, Murli Varadachari
<mv...@facebook.com> wrote:
>
> I am trying to merge from trunk to branch and I get this error "svn: File
> not found: revision 148570, path '/branches/yp/www/html/intern/ods/alarms'.
> The command I am using
> is "svn merge -r144695:148570 svn+ssh://prod/trunk/www
> <WC-of-//prod/branches/yp/www>".
>
> The branch in question '/branches/yp/www' was created from '/trunk/www'
> @140482. Subsequently I did a merge from /trunk and from a couple of other
> branches. I am now trying to merge from the trunk to branch one last time
> before I re-integrate back to trunk. However I am stuck with the above
> issue. A substantial number of files /dirs etc were merged or added
> successfully before it burped.
>
> A thorough examination of the history of the trunk indicates that @rev#
> 145142 /trunk/www/html/intern/alerts was moved / renamed to
> '/trunk/www/html/intern/ods/alarms'. Are there issues with svn merge w.r.t
> its ability to handle renamed components. I am currently using svn 1.5.3 .
>
> The history of this particular merge can be seem from svn:mergeinfo
> properties
>
> svn:mergeinfo : ==>
>
> /prod/branches/v3x/www:140558-142418
>
> /prod/branches/xx/www:83462-126155
>
> /prod/releases/r126219-10122008/www:126613,126628,126633-126634
>
> /prod/trunk/www:140483-144695
>
>
>
> Any help will be appreciated.
>
> Cheers
> murli
>
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1274991
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Trunk to branch merge error on renamed component
Posted by Mark Phippard <ma...@gmail.com>.
All known causes of this problem were fixed in 1.5.5 client. Try 1.5.5/1.5.6.
Mark
On Wed, Mar 4, 2009 at 11:26 PM, Murli Varadachari
<mv...@facebook.com> wrote:
>
> I am trying to merge from trunk to branch and I get this error “svn: File
> not found: revision 148570, path '/branches/yp/www/html/intern/ods/alarms'.
> The command I am using
> is “svn merge -r144695:148570 svn+ssh://prod/trunk/www
> <WC-of-//prod/branches/yp/www>”.
>
> The branch in question ‘/branches/yp/www’ was created from ‘/trunk/www’
> @140482. Subsequently I did a merge from /trunk and from a couple of other
> branches. I am now trying to merge from the trunk to branch one last time
> before I re-integrate back to trunk. However I am stuck with the above
> issue. A substantial number of files /dirs etc were merged or added
> successfully before it burped.
>
> A thorough examination of the history of the trunk indicates that @rev#
> 145142 /trunk/www/html/alerts was moved / renamed to
> '/trunk/www/html/intern/ods/alarms’. Are there issues with svn merge w.r.t
> its ability to handle renamed components. I am currently using svn 1.5.3 .
>
> The history of this particular merge can be seem from svn:mergeinfo
> properties
>
> svn:mergeinfo : ==>
>
> /prod/branches/v3x/www:140558-142418
>
> /prod/branches/xx/www:83462-126155
>
> /prod/releases/r126219-10122008/www:126613,126628,126633-126634
>
> /prod/trunk/www:140483-144695
>
>
>
> Any help will be appreciated.
>
> Cheers
> murli
>
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1271989
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].