dia not opening autodia files

[Jens Fursund]

Binary package hint: autodia

When creating autodia files by using "autodia.pl -d trunk/ -C -l C++" ... I recieve an error when opening the file in dia.

PyDia Error (diamodule.c:277):
<type 'exceptions.SyntaxError'>SyntaxError('invalid syntax', ('<string>', 1, 4, 'Dia:diagram()'))Traceback (most recent call last):
  File "/usr/share/dia/python/doxrev.py", line 482, in import_file
    classes = GetClasses ([sFile])
  File "/usr/share/dia/python/doxrev.py", line 400, in GetClasses
    classes.extend (Parse (f.read()))
  File "/usr/share/dia/python/doxrev.py", line 391, in Parse
    p.Parse(sData)
  File "/usr/share/dia/python/doxrev.py", line 344, in start_element
    o = eval (s + "()")

[orth (orth-layonara)]

I experienced the same problem. Turns out all you have to do is rename the extension with .dia instead of .xml or use -o filename.dia.

I guess Dia tries to import the file as xml and not native dia.

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 alpha/beta?

[Greg Toombs (greg-toombs)]

Yes, this still happens in Intrepid releases of autodia and graphviz.

[TEEJAY / HASHBANGPERL (aaron-trevena)]

This has been fixed in version 2.07 upstream, which was released on 20/05/2008, about 7 months ago.

Would be nice if package maintainers would contact upstream developers, the details are in the README, or you can use rt.cpan.org to file bugs.

I only found out about this orphaned bug queue after reading http://dag.wieers.com/blog/when-bugtracking-systems-are-fences-not-bridges and wondering what downstream bug reports weren't reaching me.

regards,

Aaron Trevena

[etali (etali)]

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.