>That would be Debian Sarge. Debian backports has svn 1.4 ... too old, I'm
>afraid.
>
>> I could try to build SVN using source, but I have my doubts.
>
>It's not inconceivable that you could build 1.6, but getting all the
>dependencies lined up could be a pain on Sarge, indeed.
>
> I'll just kee
On 15.06.2017 23:41, Peter Willis wrote:
>> Really? Version 1.1.4? Because support for file externals was added in
>> version 1.6.0, so I'm not really surprised your checkout fails. :)
>>
>> Perhaps you could consider upgrading your client?
>>
>> -- Brane
> O.K. thanks that makes sense.
> Out of d
>Really? Version 1.1.4? Because support for file externals was added in version
>1.6.0, so I'm not really surprised your checkout fails. :)
>
>Perhaps you could consider upgrading your client?
>
>-- Brane
O.K. thanks that makes sense.
Out of date package of SVN.
The failed client is on an embedd
On 15.06.2017 23:21, Peter Willis wrote:
>> Can you show the output of 'svn --version' on that computer where it doesn't
>> work? It looks like your Subversion was compiled without support for the
>> svn:// protocol (which would be really strange).
>>
>> -- Brane
> Yes, the output of that is:
>
>
>Can you show the output of 'svn --version' on that computer where it doesn't
>work? It looks like your Subversion was compiled without support for the
>svn:// protocol (which would be really strange).
>
>-- Brane
Yes, the output of that is:
svn --version
svn, version 1.1.4 (r13838)
compiled
On 15.06.2017 22:35, Peter Willis wrote:
>
> Hello,
>
>
>
> I am having an issue with an external (pointing to a file) included in
> one of my projects.
>
>
>
> I have a single external in my repository that points to a file.
>
>
>
> On my windows desktop I can check out the directory contain
