On Thu, Oct 13, 2011 at 10:39 AM, Philip Martin <philip.mar...@wandisco.com> wrote: > Hyrum K Wright <hyrum.wri...@wandisco.com> writes: > >> Another option might be to run a pre-upgrade check to ensure this type >> of error doesn't exist, before we irrevocably upgrade (and potentially >> hose) the working copy. > > This is happening during upgrade so the working copy remains a 1.6 > working copy.
Ah. I thought this was related to the post-upgrade workqueue checksum assert we've also been seeing. /me grumbles something about wishing people would have tested the release candidates. -Hyrum -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com/
