[wpkg-users] [Bug 137] WSH: 'null' is null or not an object

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=137


Jason Oster <parasytic at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|mangoo at wpkg.org             |parasytic at gmail.com




--- Comment #7 from Jason Oster <parasytic at gmail.com>  2009-04-24 00:06:32 ---
Created an attachment (id=142)
 --> (http://bugzilla.wpkg.org/attachment.cgi?id=142)
Example workaround

I finally got around to debugging this one. To reproduce, I have two packages:

pkg_a
-- pkg_b

Where pkg_a depends on pkg_b:

* Profiles.xml contains a reference to pkg_a only.
* WPKG installs both packages.
* Remove the pkg_a reference from Profiles.xml and do a /synchronize.
* WPKG removes both packages, then throws the exception.

I traced the exception back to synchronizeProfile(), which builds its own list
of packages to be removed, and removes one at a time. In cases like the above,
WPKG knows to remove both packages, pkg_a and pkg_b. Removing pkg_a first
removes both packages. Then synchronizeProfile() tries to uninstall pkg_b
(again). Since the setting node has been removed, null gets passed to
removePackage().

Attached is a patch that works around the problem. This should probably be tied
to the packagesRemoved[] array in some way.


-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.