sm-sorcery-bugs AT lists.ibiblio.org
Subject: Bugs for Sorcery are reported here
List archive
[SM-Sorcery-Bugs] [Bug 15611] New: Cleanse doesn't handle spells that get removed due to conflicts gracefully
- From: bugzilla-daemon AT bugs.sourcemage.org
- To: sm-sorcery-bugs AT lists.ibiblio.org
- Subject: [SM-Sorcery-Bugs] [Bug 15611] New: Cleanse doesn't handle spells that get removed due to conflicts gracefully
- Date: 11 Mar 2010 10:33:39 -0000
http://bugs.sourcemage.org/show_bug.cgi?id=15611
Summary: Cleanse doesn't handle spells that get removed due to
conflicts gracefully
Product: Sorcery
Version: Untargetted future release
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Cleanse
AssignedTo: sm-sorcery-bugs AT lists.ibiblio.org
ReportedBy: wich AT sourcemage.org
Say spell a and b are both installed but conflict one another, which may
happen
because of a problem during cast, interrupted cast, etc., or if the spells
when
installed were not conflicting, but are after a grimoire update.
Then when one runs a cleanse --fix both spells are queued to be checked. Say
spell a is first to be checked and fails the check, then it is cast. Since it
conflicts spell b, b is dispelled. Then later when it is time for cleanse to
check spell b, it will rightfully complain that the install log is missing,
(since file check is first,) and try to cast the spell to repair it.
A better solution would probably be to check whether the spell is still
installed before each spell check with spell_ok and, if it isn't, don't do any
check and report it was removed, went missing, or some other appropriate
message in the final summary.
--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
- [SM-Sorcery-Bugs] [Bug 15611] New: Cleanse doesn't handle spells that get removed due to conflicts gracefully, bugzilla-daemon, 03/11/2010
Archive powered by MHonArc 2.6.24.