Nathan Hartman wrote on Fri, 09 Nov 2018 09:27 -0500:
> On Thu, Nov 8, 2018 at 4:24 PM Daniel Shahaf wrote:
>
> > It's a wild guess but perchance it's a 'svn co ${URL}@{DATE}' and the
> > binary search (to resolve {DATE} to a number) is failing due to authz?
> >
>
> Or due to non-chronological c
On Thu, Nov 8, 2018 at 4:24 PM Daniel Shahaf wrote:
> It's a wild guess but perchance it's a 'svn co ${URL}@{DATE}' and the
> binary search (to resolve {DATE} to a number) is failing due to authz?
>
Or due to non-chronological commits? (Just another wild guess.)
Mark Phippard wrote on Wed, 07 Nov 2018 08:20 -0500:
> Yes, the user that got this error was using SVNKit. I do not know if it
> was via Jenkins, Eclipse or something else and that is why I am not sure
> what the command was. I asked to recreate using SVN command line so we
> could better underst
On Wed, Nov 7, 2018 at 8:16 AM Pavel Lyalyakin <
pavel.lyalya...@visualsvn.com> wrote:
> Hello,
>
> On Wed, Nov 7, 2018 at 4:10 PM, Mark Phippard wrote:
> >
> > Anyone seen this error before? This is in the Apache error logs and not
> sure what it means:
> >
> > [dav:error] Could not access revi
Hello,
On Wed, Nov 7, 2018 at 4:10 PM, Mark Phippard wrote:
>
> Anyone seen this error before? This is in the Apache error logs and not sure
> what it means:
>
> [dav:error] Could not access revision times. [500, #175002]
>
> Searching at svn.haxx.se only finds the commit where the message was
Anyone seen this error before? This is in the Apache error logs and not
sure what it means:
[dav:error] Could not access revision times. [500, #175002]
Searching at svn.haxx.se only finds the commit where the message was
added. I think it is happening for a user doing a checkout but I am trying
