Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

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

           Summary: stageing doesn't yet fully protect modified files...
           Product: Sorcery
           Version: 1.14.x
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Unknown
        AssignedTo: sm-sorcery-bugs AT lists.ibiblio.org
        ReportedBy: ruskie+smbugs AT mages.ath.cx
                CC: vin.public AT gmail.com


So here's what I found to happen(assuming I never installed the spell before).

1. cast spell
2. installs first time
3. edit the config file in etc
4. cast -c the spell again/upgrade
5. config file remains the same
6. cast -c the spell again/upgrade
7. config file gets replaced by the original one

The way I figure it the problem is as follows:
1,2,3 work fine the issue happens at step 4:

4.1 build
4.2 dispel
4.3 stage install
4.4 install stage
4.5 create hash log(which includes the ON DISK files hash instead of the 
stagged
one)

6.1 build
6.2 dispel(dispels all files since the hashes are unchanged)
6.3 stage install
6.4 install stage
6.5 create the logs again with the original hash


One solution would be to actually create the install and hash logs(the cache
tarball should come at the end though to take the real files into effect plus 
it
takes some time :) ) between
stage install(installing to stage)(4.3) and installing that stage to the
system(4.4). So that after the stage gets installed nothing changes with the
logs. I don't know if this is actually the optimal solution but it's the only
thing I can think of atm without needing to modify spells to manually track
config files.

This issue experienced by both me and public hence the CC to him as well...

-- 
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.