Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 10189] New: Dispel not obeying dependency options

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 10189] New: Dispel not obeying dependency options
  • Date: 11 Dec 2005 06:08:06 -0000

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

Summary: Dispel not obeying dependency options
Product: Sorcery
Version: 1.13.x
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Dispel
AssignedTo: sm-sorcery-bugs AT lists.ibiblio.org
ReportedBy: dhaley AT hot.rr.com


sorcery: 1.13.3-rc5
===================

sorcery set to always dispel newly orphaned spells as they occur during a
dispel. I noticed recently that when I do soemthing like:

dispel --user-deps mikmod

I get:

Dispelled spell: mikmod
Dispelled spell: libmikmod

However using the same thing if I add one or more spells to the list such as:

dispel --user-deps mikmod gpart

I get:

Dispelled spell: mikmod
Dispelled spell: gpart

You will noticed that the newly orphaned spell created (libmikmod) that was in
fact dispelled as it should be in teh first example was not in the second. The
Examples posted are real spells I used to test this out before posting this
bug.

Is anyone noting the same problem on their machine. I do not have another SMGL
box here at home that I can verify this find on so another set of eyes is
always
welcome :)

Sincerely,
SilverSlayer

--
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.



  • [SM-Sorcery-Bugs] [Bug 10189] New: Dispel not obeying dependency options, bugzilla-daemon, 12/11/2005

Archive powered by MHonArc 2.6.24.

Top of Page