[wpkg-users] [Bug 145] Dependancy error when removing packages
bugzilla-daemon at bugzilla.wpkg.org
bugzilla-daemon at bugzilla.wpkg.org
Tue Apr 21 16:30:47 CEST 2009
http://bugzilla.wpkg.org/show_bug.cgi?id=145
--- Comment #4 from Falko Trojahn <ftrojahn at smi-softmark.de> 2009-04-21 16:30:39 ---
Helo Rainer,
I've tested with 1.1.0-M22 (release 53). The dependancy error seems to be
resolved, but a more seriously one arises after removal of a certain dependent
package:
Removing packages depending on 'Adobe Shockwave Player' (shockwave11).
Removing Adobe Shockwave Player Firefox Plugin (shockwave11firefox)...
Command 'cmd /c del "%ProgramFiles%\Mozilla Firefox\plugins\np32dsw.dll"'
retur
ned exit code [0]. This exit code is not an error.
Command in removal of Adobe Shockwave Player Firefox Plugin returned exit code
[0]. This exit code indicates success.
Removal of Adobe Shockwave Player Firefox Plugin successful.
Removing Adobe Shockwave Player (shockwave11)...
Removal of Adobe Shockwave Player successful.
Message: 'null' ist Null oder kein Objekt
Description: 'null' ist Null oder kein Objekt
Error number: 800a138f
Stack: undefined
Line: undefined
The error is reproducable and does not exist when I use wpkg.js version 1.0.
Explanation in short:
- old packages shockwave11 and shockwave11firefox (depends from shockwave11)
- new packages adobeswfplayer and shockwave11firefox3 (depends from
adobeswfplayer)
- situation: old packages installed, but removed from profile, new packages
assigned
- cscript wpkg.js /synchronize gives the above error after removal of the two
packages. Next run completes successfully.
BUT:
- when the packages shockwave11 and shockwave11firefox do not exist any more in
the xml files (I think this is not so unusual when I try to replace packages
with other names), the following error persists:
Message: 'null' ist Null oder kein Objekt
Description: 'null' ist Null oder kein Objekt
Error number: 800a138f
Stack: undefined
Line: undefined
I've got no hint from logfile, since it is not created.
In the same situation, with wpkg.js version 1.0 all actions run flawlessly
without any error.
I send you the log and xml files via PM.
Best regards,
Falko
--
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the wpkg-users
mailing list