Bugs for Sorcery are reported here

[bugzilla-daemon AT metalab.unc.edu]

http://bugs.sourcemage.org/show_bug.cgi?id=7653

acedit AT armory.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
            Summary|cast perl/tcl cycle blocks  |perl/tcl and conflicting
                   |forever                     |files on resurrect
            Version|1.11.x                      |1.12.x



------- Additional Comments From acedit AT armory.com  2004-11-19 22:52 -------
bug 7648 is fixed so the title is incorrect, however theres an interesting
situation here...

Im going to fill in the details so its clear whats going on as its not 
entirely
obvious in the first report.

1) perl has the right md5sum
2) tcl has the right md5sum
3) perl has the wrong md5sum but is immediatly fixed by cleanse
4) tcl, being the only owner of the file removes the file on dispel
5) on resurrect Thread.3 is installed, but ressurect doesnt appear to replace
the logs since they already exist. So we have the logs from step 3 with 
Thread.3
removed, and thus thread.3 is now an alien
6) resurrecting tcl the md5sum log is unpacked but thread.3 is not (it already
exists)

cleanse is run on tcl, which discovers that the md5sum of Thread.3 is wrong
because its from the perl spell, it then cant find any owner of Thread.3 since
it became an alien in step 5. Not having an owner means it cant just defer
ownership to that spell. Thus the spell is recast.

So what the problem really is, is that the md5sum and install logs are stale 
and
resurrect isnt overwriting them. The easy thing to do is to remove them before
the resurrect so we get the right logs.

Im anxious about doing this in immediatly 1.11 because resurrect has always 
left
the old logs, its a risky fix in my opinion, this problem is really a spell
problem. Also if the user keeps their logs cleaned up with cleanse the stale
logs wont exist and the problem would not occur. Of course also, recasting the
spell now works out of resurrect so the problem does resolve itself, just not 
in
the best way possible. Probably course of action is to fix it in 1.12, let it
soak in for a while then if theres a need for the fix move it in. It sounds 
like
this is a pretty rare case as it is since no one even noticed bug 7648 for a
long time.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.