reintegrate merge failing because "can only be used if revisions <snip> were previously merged", but it's a lie (I think?)
From: Charlet, Ricky <ricky.charlet_at_hp.com>
Date: Thu, 21 May 2015 00:51:26 +0000
Howdy,
I have a trunk and a feature branch. Time has come (it was long, over a year) to reintegrate back into trunk. I have subversion 1.8 on both server and client (though a year ago, we were using 1.6 server and client).
I have recently (like yesterday) merged trunk to branch successfully. It passes verification and sanity testing. I like the branch.
From within an up-to-date trunk working copy, if I attempt the merge branch back to trunk I get some complaints:
[charletr_at_ariesbld trunk]$
Soo... that's a bit hard to believe because I did just recently merge trunk to branch. Furthermore, if I go into my branch working copy and attempt to merge an exact change (let me pick revision 19595 as an example because it's first in the listing above), nothing happens:
FYI, here is the view of mergeinfo from my trunk and branch:
[charletr_at_ariesbld DUAL_SSL_Inspection]$ svn propget svn:mergeinfo ports/lsm/lsmclient/test/cukes/features/1_package_update
Notice that 19595 is, infact, missing from branch's mergeinfo.
In summary, A recent merge from trunk to branch suceeded, trunk cannot reintegrate because it claims that some change sets are not merged to branch, attempts to merge those exact change sets into branch produce a no-op, mergeinfo on branch confirms those change sets are missing.
I'm stuck... any ideas what to try next?
-- Ricky Charlet Software Dev / Routing Dude: Aries team, Roseville CA ricky.charlet_at_hp.com USA: 916.785.2090Received on 2015-05-21 02:53:06 CEST |
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.