Error parsing config file

[Simon Large <si...@gmail.com>]

Hi guys,

I've seen this error reported twice on the TSVN mailing list and can
now reproduce it. The symptom is and error message on all subversion
operations:

Error while parsing config file: BlahBlah\config:
line 109: Option expected

It seems that if there is any leading space before the option name,
this error is thrown. I tested with Windows and Unix line endings and
the result was the same. Although it is easy to fix, it seem
unnecessarily restrictive to require no white-space before option
names, when any or no white-space is permitted elsewhere in the line.


Simon

Re: Error parsing config file

[Branko Čibej <br...@wandisco.com>]

On 08.08.2013 16:24, Simon Large wrote:
> Hi guys,
>
> I've seen this error reported twice on the TSVN mailing list and can
> now reproduce it. The symptom is and error message on all subversion
> operations:
>
> Error while parsing config file: BlahBlah\config:
> line 109: Option expected
>
> It seems that if there is any leading space before the option name,
> this error is thrown.

Yes. There must be no leading space -- that is documented in
~/.subversion.README.txt:

    An option, which must always appear within a section, is a pair
    (name, value).  There are two valid forms for defining an option,
    both of which *must start in the first column* ...

-- Brane

-- 
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane@wandisco.com