[wpkg-users] Remove does not start upgrade
Rainer Meier
r.meier at wpkg.org
Thu Nov 13 20:42:46 CET 2008
Hi Hennes,
Marc Hennes wrote:
> I am using WPKG 1.0.2. I thought this version has this upgrade-before-remove feature implemented (At least I found a hint in the release notes for version 1.0).
> But I have a broken uninstall command at the moment.
> So I increased the package version and corrected the uninstall string but there is no update triggered.
> WPKG just tries to use the local uninstall string.
>
> Here is some debug output:
>
> 2008-11-13 18:52:53, DEBUG : Using profile(s):|HP PC Office 2007|
> 2008-11-13 18:52:53, INFO : Removing GTK+ 2.10.13 runtime environment (gtk269)...
> 2008-11-13 18:52:53, DEBUG : Found system locale: 407
> 2008-11-13 18:52:53, DEBUG : Found language definition node for language ID 407
> 2008-11-13 18:52:55, DEBUG : Executing command: "%CommonProgramFiles%\GTK\2.0\unins000.exe" /VERYSILENT
> 2008-11-13 18:52:55, ERROR : Command '"%CommonProgramFiles%\GTK\2.0\unins000.exe" /VERYSILENT" was not successful.|Das System kann die angegebene Datei nicht finden.|
> 2008-11-13 18:52:55, DEBUG : Command returned result: undefined
> 2008-11-13 18:52:55, ERROR : Exit code returned non-successful value: undefined|Package: GTK+ 2.10.13 runtime environment.|Command:|"%CommonProgramFiles%\GTK\2.0\unins000.exe" /VERYSILENT
> 2008-11-13 18:52:55, DEBUG : Checking existence of package: GTK+ 2.10.13 runtime environment
> 2008-11-13 18:52:55, DEBUG : Uninstall entry for GTK+ 2.10.13 runtime environment was found: test successful
> 2008-11-13 18:52:55, DEBUG : Checking gtk269 zombie state.
> 2008-11-13 18:52:55, ERROR : Could not process (remove) GTK+ 2.10.13 runtime environment.|Package still installed.
> 2008-11-13 18:52:55, DEBUG : Saving sorted settings to 'C:\WINDOWS\system32\wpkg.xml'.
I think this log misses some entries. Especially I cannot see the whole
debug output where WPKG checks the existene of a package and verifies
the install state by checks. Probably you could post the following:
- Full log file
- Current package definition (XML file)
- Client settings file (%SystemRoot%\system32\wpkg.xml)
It is true that WPKG will do an upgrade of a package before the remove
process is started. Are you sure the package is still available to WPKG
on the server side? WPKG can do an upgrade only if the same package
(package ID "gtk269") in your case is still available on the server.
Probably you canged the package ID too - if you did so, then your "new"
package is not related to the installed GTK package from WPKG point of
view. So if you changed the package ID to "gtk2691" or something else,
then WPKG cannot do the upgrade.
br,
Rainer
More information about the wpkg-users
mailing list