Strange mergeinfo lack

[Bradford Hull <bk...@gmail.com>]

I've been using 1.5 for just a few weeks now, looking forward to the
tracking of merged and eligible revisions, because I have established
the usual branch-for-release pattern and we cherry-pick trunk fixes to
promote (merge) to a release branch.

My problem is, I merge a change from the trunk and commit it, and the
revision I merged does not show up in the mergeinfo.  I can put it
there with --record-only easily enough, but it seems clear that it
should have been there as a result of the merge and commit.  This is
such a common case, I know it has to be supported; I see clear
evidence the Subversion team used my process pattern on developing 1.5
for release.

One detail that I wonder about, maybe it could be related: I relocated
my repository, at about the time I started using 1.5 (from a Windows
host to an Ubuntu Hardy Heron server).  Is it possible that  something
internal recorded the original repository location and thinks I'm
merging to a foreign repository?

I realize this is sort of a thin report, but I haven't seen anything
remotely similar in the  google world or this or the dev email list,
so I'm not sure exactly which rocks to look under for more
information.  I'm using Hardy Heron backports of subversion, which is
1.5.1 (r32289), interacting with the repository through apache.  Any
bread crumbs?

-- 
The early bird may get the worm, but the second mouse gets the cheese.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Strange mergeinfo lack

[Bradford Hull <bk...@gmail.com>]

I solved my own problem eventually.  Subversion thought the merges
were from a foreign repository, even though they were referencing the
same (relocated) repository with the same UUID in all cases.

However, when I removed the WC and checked it out again fresh, rather
than using the original copy I had done the svn switch --relocate on,
the problem disappeared.

I submit this to the list in case anybody else runs into this kind of situation.

On Fri, Nov 21, 2008 at 7:28 PM, Bradford Hull <bk...@gmail.com> wrote:
> I've been using 1.5 for just a few weeks now, looking forward to the
> tracking of merged and eligible revisions, because I have established
> the usual branch-for-release pattern and we cherry-pick trunk fixes to
> promote (merge) to a release branch.
>
> My problem is, I merge a change from the trunk and commit it, and the
> revision I merged does not show up in the mergeinfo.  I can put it
> there with --record-only easily enough, but it seems clear that it
> should have been there as a result of the merge and commit.  This is
> such a common case, I know it has to be supported; I see clear
> evidence the Subversion team used my process pattern on developing 1.5
> for release.
>
> One detail that I wonder about, maybe it could be related: I relocated
> my repository, at about the time I started using 1.5 (from a Windows
> host to an Ubuntu Hardy Heron server).  Is it possible that  something
> internal recorded the original repository location and thinks I'm
> merging to a foreign repository?
>
> I realize this is sort of a thin report, but I haven't seen anything
> remotely similar in the  google world or this or the dev email list,
> so I'm not sure exactly which rocks to look under for more
> information.  I'm using Hardy Heron backports of subversion, which is
> 1.5.1 (r32289), interacting with the repository through apache.  Any
> bread crumbs?
>
> --
> The early bird may get the worm, but the second mouse gets the cheese.
>



-- 
The law, in its majestic equality, forbids the rich as well as the
poor to sleep under bridges, to beg in the streets, and to steal
bread.
                                            Anatole France

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org