On Tue, Apr 29, 2008 at 4:41 PM, David Summers
<david_at_summersoft.fay.ar.us> wrote:
>
> On Tue, 29 Apr 2008, Mark Phippard wrote:
> > Did you ever use this with one of the 1.5 pre-release versions before
> > we nailed down the repository format? The repository internals
> > changed a lot over time and people that used the in-between stage
> > binaries could definitely get weird results.
> >
> >
> >
>
> As stated in my first email, I've used the web-dav proxy feature since
> 2006/12 within several days of when the feature was first made available, so
> my answer is "yes"; I'ved used the 1.5 pre-release versions before the
> repository format was nailed down.
>
> What is "strange" or "interesting" is that I didn't have a problem up
> through r27613 but rc3 seems to have this problem.
>
> I guess it is possible that I need to create or re-create my repo(s) with
> some new parameters or something, but what would that be? The only
> parameter I know of at the moment would be the --pre-1.5-compatible which
> I'm currently using.
>
> But I did do that before sending my first email, I re-created the
> repository with the rc3 version and tried and got the stated results.
>
> If I can reproduce the problem on a strictly 1.5.0-rc4 repo then I could
> also try doing a binary search through the intervening commits between rc3
> and r27613 and try to find out when it broke.
I was thinking more of things like repositories back when we still had
SQLite and then there were several variations of the node-origins
cache. Not withstanding some of the bugs fixed between rc3 and rc4
there is no reason doing it all with rc3 should have created a problem
other than some kind of previously unknown bugs.
--
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
Received on 2008-04-29 22:48:00 CEST