bzr missing --xml has incorrect XML format

Bug #936184 reported by Frits Jalvingh on 2012-02-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Using bzr missing --xml the output format is:
<?xml version="1.0" encoding="UTF-8"?>
You have 1 extra revision(s):
 <committer>Frits Jalvingh &lt;<email address hidden>&gt;</committer>
 <timestamp>Tue 2012-02-14 18:14:25 +0100</timestamp>
 <message><![CDATA[Upto 4.0]]></message>

 You are missing 1 revision(s):
 <committer>Puzzler &lt;<email address hidden>&gt;</committer>
 <timestamp>Thu 2012-02-16 09:23:58 +0100</timestamp>
 <message><![CDATA[Merged Call 34326 - Puzzler merge of <email address hidden> by xxxx on 16-feb-2012 9:08:58
<b>Objectverdeling - Minpunten bij wiegering voordracht.</b><br><br>Met deze fix wordt het mogelijk om woningzoekende die een voordracht weigeren te  straffen door punten af te trekken van het totaal aantal inschrijfpunten. Zie hiervoor de handleiding.]]></message>

The messages about missing/extra revisions is not part of the XML proper.

description: updated
Frits Jalvingh (fjalvingh) wrote :

Whoa. In addition a lot of end tags are missing when the command has only one side with changes (/merge, /log).

Guillermo Gonzalez (verterok) wrote :


Thanks for reporting this problem.

the bzr missing --xml command will only output the log info as xml, if you want to get full xml output please use: bzr xmlmissing

And regarding the missing en tags, that's correct there is a bug regardign end tags in the case of using: bzr missing --xml.


Changed in bzr-xmloutput:
status: New → Confirmed
importance: Undecided → Medium
Frits Jalvingh (fjalvingh) wrote :

Hi, thanks for answering ;-)

bzr xmlmissing cannot/does not output data for merges, and my code review tool needs that data....


To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers