Hi Paul, sorry for late response. Do you still have the original XML file? GTG makes backups every day in ~/.local/share/gtg or ~/.local/share/gtg/backup depending on if you use GTG 0.2.9 or development version. I would need that file to debug this bug. You can anonymize your file using:
bzr branch lp:gtg
cd gtg
./scripts/anonymize_task_file.py ~/.local/share/gtg/backup/gtg_tasks-3d246e96-5a69-4f7d63b-eaf1e188b679.xml.2012-09-10.bak
and upload the final file from /tmp/gtg-tasks.xml. (At the moment, tags are not anonymized, it is already reported as a bug. Nevertheless, the names of tags are the only thing that is not anonymized.)
Hi Paul, sorry for late response. Do you still have the original XML file? GTG makes backups every day in ~/.local/share/gtg or ~/.local/ share/gtg/ backup depending on if you use GTG 0.2.9 or development version. I would need that file to debug this bug. You can anonymize your file using:
bzr branch lp:gtg anonymize_ task_file. py ~/.local/ share/gtg/ backup/ gtg_tasks- 3d246e96- 5a69-4f7d63b- eaf1e188b679. xml.2012- 09-10.bak
cd gtg
./scripts/
and upload the final file from /tmp/gtg-tasks.xml. (At the moment, tags are not anonymized, it is already reported as a bug. Nevertheless, the names of tags are the only thing that is not anonymized.)
Please upload that XML for further investigation.