[BUG][PATCH] fileid_involved fails to unescape xml characters

[John Arbash Meinel]

Martin Pool wrote:
> On 19 Jan 2006, John Arbash Meinel <john at arbash-meinel.com> wrote:
> 
>>I tracked down the problem to the fileid function.
>>Basically, it is parsing the xml directly, and forgetting that some
>>characters (like <>) get escaped.
>>
>>So I'm using xml.sax.saxutils.unescape to get them back into normal strings.
>>Unfortunately, this also means I had to move xml.py out of the way,
>>since it conflicts with the python system package 'xml'. (fortunately,
>>only xml4.py and xml5.py actually referenced the xml.py, so it was a
>>very localized move).
>>Long term, they all should probably be called something different.
>>
>>The branch is available at:
>>http://bzr.arbash-meinel.com/branches/bzr/0.7-bugfix/
>>
>>I also fixed the stub_server issue with paramiko > 1.5.2 (it now always
>>has attribute st_mode, just set to 0).
> 
> 
> Thanks, merged into http://bazaar-ng.org/bzr/bzr-0.7-fixes/
> 

Do you have a specific timeline for releasing 0.7rc3? The
fileid_involved bug basically breaks everyone who uses an arch->bzr
conversion, since directories generally got a tag which was:
	User <email> Timestamp
Which means there are lots of <> characters in Arch ids.

John
=:->
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060119/13ffafd7/attachment.pgp