I seem to have fixed my issue. MasterTicketPlugin apparently cant
handle a pre-existing circular dependency when upgrading from 11.X (mine
was 11.7) to 12.X (I tried 12.1 and **
<http://sterlingthoughts.homelinux.com/projects/Spit/about>Trac
0.12.2dev-r10430). By Deleting one direction of the circular dependency
from the mastertickets table within the trac.db, I was able to properly
close tickets again. The dependency tree also looked normal again.
Here is the sql query I ran in the trac.db:
sqlite> DELETE mastertickets WHERE source IS 25 AND dest IS 29;
Thanks,
Sterling Peet
On 1/23/2011 9:17 PM, Sterling Peet wrote:
When I upgraded from 11.7 to 12.1, I discovered that the
MasterTickets plugin appeared to be ignoring any dependencies already
in the database at the time of upgrade when you tried to change them.
I can add new dependencies and then remove the new dependencies.
However, attempting to remove old dependencies appears to not have any
effect. In hopes that upgrading the plugin would help, I upgraded it
to the latest version (3.0.2).
In this particular example, ticket number 29 and 25 originally had
a circular dependency, but by accident. What is supposed to happen is
#29 is blocking #25 and the comment history verifies these changes
were indeed made. However, #25 still shows up in the blocked by field
for # 29, and I cannot close ticket #29.
I have included a screen shot of the resulting depgraph. I feel
like this problem has to do with either caching or a change in
schema. Does anyone know how to correct this?
Thanks,
Sterling Peet
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en.
