[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


Rainer Meier <r.meier at wpkg.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




--- Comment #3 from Rainer Meier <r.meier at wpkg.org>  2008-12-23 14:12:46 ---
OK, I will try investigating in this special case. In general WPKG seems to do
what it is supposed to do. It removes the packages which are not assigned to
the current host any longer due to removal of the profile.

However you should probably think about a smooth removal procedure. WPKG will
try to uninstall the packages by executing their remove command. If there are
no commands defined it will simply execute none of the commands and then check
if it is still installed (most probably it will). Then it depends on the
current package state on the server what happens. If the package is still
defined within your server-side package database, then the package reference
will be kept locally and for each run WPKG will try again removing it. You
might get out of this loop by adding a proper remove command to the package and
then increase the version. Then WPKG will first upgrade to your new version of
the package (even if it is not assigned any more) and then properly remove it.

If you also remove the package definition from the server completely then WPKG
will remove the package reference from the local wpkg.xml and just forget about
the package (no matter if the remove command was successful or not).

To make it clear - this might help you to sort out your problem but it does not
explain null pointer references. I will have to investigate.

br,
Rainer


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