Yesterday, I updated our Reviewboard (1.5.x) to SVN 1.7.6 and pysvn-1.7.6.
It did not have any effect on this issue--the problem is still there. So:
updating to the latest pysvn does *not* solve the problem.
m@
On Tuesday, March 6, 2012 6:01:46 AM UTC-6, daniel@googlemail.com wrote:
>
> I
I believe there was an update to pysvn at the weekend - so it might be
worth checking that and seeing if that resolves the issues.
On Feb 14, 9:26 pm, David Trowbridge wrote:
> The critical issue is that pysvn does not yet support SVN 1.7, and generates
> broken results. If someone can find a wor
The critical issue is that pysvn does not yet support SVN 1.7, and generates
broken results. If someone can find a workaround we're happy to integrate
it,
but otherwise I think we're going to wait for pysvn to update.
-David
On Tue, Feb 14, 2012 at 1:19 PM, phoke wrote:
> We upgraded to SVN 1.
