GNOME Bugzilla – Bug 318480
planner files are difficult to diff because of constantly changing ids
Last modified: 2021-06-09 20:34:18 UTC
Please describe the problem: The output format for planner, both to database and to file, has a bad problem. It supports an id="" attribute for all items in the file, and uses this to cross-reference - fine. However, planner generates these ID's as integers numbered-from-1 every time the plan is output. This means that it is impossible to do concurrent work on a plan! If the plan is kept under a source-code-management system, the ID numbers make it impossible to merge plans. Likewise in databases. The in-program datastructures don't make use of the ID. If the ID were a string, generated like "<username>-<host>-<datestamp>", which was GQuarked on load/save of the file, then it would be possible to store the plans sensibly under CVS, which would make this program useful. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information: This is an old bug report remaining in the Debian BTS. It probably was fixed already but I'm hereby polling the upstream authors to verify. If it's fixed, I will close the corresponding bugs in the Debian BTS.
This issue is still there. It prevents effective use of CVS.
Right, I also came across this problem, since I thought I could keep track on changes in the xml file within my subversion. But unfortunately there are these switching id's which confuse very much. So I already gave up on that, until I saw this post, which states that this is indeed a bug. (I hope it is.)
*** Bug 334086 has been marked as a duplicate of this bug. ***
> Debian Bug #279692 -> full http link would probably be better. To sum up with the bug I just closed as duplicate of this one, the big problem is that entries are not persistant across sessions, as in, their metadata changes even if the actual data it refers too hasn't changed. As a consequence, this makes the whole format not diff friendly which makes it hard to store under (d)vcs or have any other kind of collaborative editing.
*** Bug 380795 has been marked as a duplicate of this bug. ***
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/World/planner/-/issues/93.