Hi Stefan,
Thanks for this.
As I mentioned, the repo in question is no longer corrupt without any
intervention by me to fix, so this isn't a problem. In any case, I'm glad
to hear that bumping up the SQLite version should possibly resolve the
problem for others in future.
Kind regards, Dan
On
On 10/28/2016 16:12, Dan Atkinson wrote:
> Hi Johan,
>
> The repository is on a local drive and I have several other
> repositories on the same drive as well that were unaffected.
>
> I do some tasks (update/tag) on the repository via the command line. I
> just checked and the version of SVN used
Hi Johan,
The repository is on a local drive and I have several other repositories on
the same drive as well that were unaffected.
I do some tasks (update/tag) on the repository via the command line. I just
checked and the version of SVN used on the command line is 1.8.15.14429.
In any case,
[ Added Dan Atkinson to cc, because he asked us to :-). Dan, see below. ]
On Fri, Oct 28, 2016 at 12:51 AM, Stefan wrote:
> On 10/27/2016 16:36, Dan Atkinson wrote:
>> Hi there,
>>
>> Firstly, I am not subscribed to this mailing list so would appreciate
>> being explicitly
On 10/27/2016 16:36, Dan Atkinson wrote:
> Hi there,
>
> Firstly, I am not subscribed to this mailing list so would appreciate
> being explicitly CC'd in any responses. :-)
>
> When I attempted to update my repository, I received the following update:
>
> Error: The working copy database at