[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Time for RC4 or more issues?

From: Paul Burba <ptburba_at_gmail.com>
Date: Thu, 17 Apr 2008 15:15:54 -0400

On Thu, Apr 17, 2008 at 3:02 PM, Mark Phippard <markphip_at_gmail.com> wrote:
> This is to get feedback on where we are in terms of producing an RC4.
> I believe the "main" issues that blocked us from releasing RC3 have
> all been fixed and backported. That said, there are some items left
> in STATUS that need votes:
> * r30574
> Use `neon-config --libs` when `neon-config --la-file` isn't available.
> Votes:
> +1: arfrever, cmpilato
> * r30633, r30634
> Make 'svn merge' output state when the merge is from a foreign repository.
> Notes:
> If we don't backport this, we need to increment the @since line
> for svn_wc_notify_foreign_merge_begin.
> Votes:
> +1: cmpilato, pburba
> * r30644
> Make --record-only merges record and elide mergeinfo on subtrees.
> Notes:
> Record only merges without this functionality are a lot less useful.
> Votes:
> +1: pburba

This change is causing mergeinfo corruptions and a segfault in
merge_tests.py 17 and 22. The tests passed for me on Win32 because
there is no checking of exit codes and the tests themselves don't
examine the mergeinfo. I just changed my +1 to -1. I'm looking into
the problem.

> I suppose none of these are critical, but it would be good to get them
> in to RC4 if someone can review.
> What else is out there? I think there are 3 specific issues.
> 3172 DEFECT P2 NEW 'svn log -g' seems to encounter error on server
> 3067 DEFECT P3 REOPEN subtrees with intersecting mergeinfo,
> that don't exist at th
> 3174 DEFECT P3 NEW Merge algorithm chokes on subtrees
> needing special attention
> I have heard it suggested that some or all of these can wait until a
> 1.5.1. I am fine with that, but I'd also be fine with waiting for any
> or all of these if someone thinks a fix is imminent. So I am raising
> this as a chance for people to declare if they are working on any of
> these and give a status update.
> Paul is signed up for 3067, and I assume he is looking at it.

I think 3067 is fairly serious. In some not uncommon use cases
involving subtrees with mergeinfo it prevents merges from completing
and there is no simple workaround. Working on this one too, but I
can't say a fix is imminent :-(

> Kamesh added some good detective work to 3172 if someone wants to look at it.
> Paul has committed XFAIL tests for 3067 and 3174.
> Anyway, I am not so much pushing for an RC4 as I am just trying to get
> some clarity on what needs to be done to get there. I am sure I am
> not the only one that is wondering.
> --
> Thanks
> Mark Phippard
> http://markphip.blogspot.com/
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: dev-help_at_subversion.tigris.org

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-17 21:16:15 CEST

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.