id,summary,reporter,owner,description,type,status,priority,component,version,resolution,keywords,cc
24,breakage in wiki parsing from normalize_rev,fx,lele,"I have tickets with backtrace information like this:
x00000000005c5787
{{{
#0  0x00000000005c5787 in cull_hash_free_descr (descr=0x38003800000034)
    at ../libs/cull/cull_hash.c:642
}}}

They won't display because, for some reason, the address fields
seem to be parsed as some sort of revision, and DarcsRepository.normalize_ref
raises an error.  I don't know why such processing is done at all,
but it seems to be VCS-independent, since a test with svn for the
repo format also tried to make the hyperlinks, although it didn't
fail to display the ticket.  (I looked in the docs without success
for why such processing might be done at all.)

Anyhow, the equivalent function in the svn backend doesn't raise
an error, so I'm currently using this change.  I haven't sent it
as a darcs patch because I suspect it's not entirely right.

{{{
--- old-trac-darcs/tracdarcs/repository.py	2010-10-28 11:18:49.000000000 +0100
+++ new-trac-darcs/tracdarcs/repository.py	2010-10-28 11:18:49.000000000 +0100
@@ -159,7 +159,11 @@
             try:
                 rev = int(rev)
             except ValueError, le:
-                raise TracError('Ill-formed revision: %s, error: %s' % (rev, le))
+                # This causes errors e.g. listing tickets with backtrace
+                # addresses (like ""00002b7aee34e080"").  The svn equivalent
+                # just passes, so do that instead.
+                # raise TracError('Ill-formed revision: %s, error: %s' % (rev, le))
+                pass
             if rev > youngest:
                 rev = youngest
         return rev
}}}

I'm using Trac 0.12.1 and the current trac-darcs.  A preview in this
instance doesn't show the effect of trying to parse those fields,
so I assume that's either specific to the trac version or to some
plugin I have, but I don't know what plugin might be relevant.
I assume you could get the breakage in other circumstances, though,
if the error gets raised.",defect,closed,major,darcs backend,,fixed,,
