[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Bugreport: invalid xml file produced by: svn log --xml --verbose --use-merge-history --search "msg1"

From: Martin Obermeir <martin.obermeir_at_lauterbach.com>
Date: Tue, 12 Dec 2017 16:37:59 +0100

Hi all,

I'd like to report a bug: "svn log --xml" produces an invalid xml when
the "--use-merge-history" option is combined with "--search"

Example: svn log --xml --verbose --use-merge-history --search "msg1".

The xml contains two closing "</logentry>" tags, but only one opening
<logentry> tag.

Details see below.

I could not find this bug in the issue tracker/mailing list. The bug can
be easily reproduced with the script attached to this email, it is also
available here:


Your operating system
- Kubuntu 17.10 (Linux 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6
10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux)
The release and/or revision of Subversion
   - svn, version 1.9.7 (r1800392)
       compiled Aug 17 2017, 10:20:03 on x86_64-pc-linux-gnu
   - also trunk 1.11.0-dev confirmed by "danielsh" on IRC:
The compiler and configuration options you built Subversion with
- (from apt)
Any private modifications you made to your Subversion
- (none)
The version of Berkeley DB you're running Subversion with, if any
- (none)
Anything else that could possibly be relevant. Err on the side of too
much information, rather than too little.
- Expected output:
     xml with just one "</logentry>" line
- Actual output (see last lines):
     <?xml version="1.0" encoding="UTF-8"?>

May I enter this bug to the issue tracker?

Best regards

Received on 2017-12-13 07:30:21 CET

This is an archived mail posted to the Subversion Users mailing list.