[wpkg-users] [Bug 174] New: Using the upgrade entry from the client is troublesome

[bugzilla-daemon at bugzilla.wpkg.org]

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

           Summary: Using the upgrade entry from the client is troublesome
           Product: WPKG
           Version: 1.1.x-M
          Platform: PC
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: wpkg.js
        AssignedTo: mangoo at wpkg.org
        ReportedBy: pendl2megabit at yahoo.de
         QAContact: wpkg-users at lists.wpkg.org


With WPKG 1.1 the upgrade entries from the client seem to be used instead the
ones from the server.

Now if you need to change the upgrade command you will first have to downgrade
the client to update the upgrade command and then upgrade the client, which now
uses the new upgrade commands.

For instance the upgrade command for the WPKG client was as follows:

<upgrade cmd="%comspec% /c if %PROCESSOR_ARCHITECTURE% == x86 msiexec /qn /i
"%SOFTWARE%\AppDeploy\WPKG Client\WPKG32_2009-01-24.msi" ALLUSERS=1
SETTINGSFILE="%WPKG_ROOT%\settings.xml"">
    <exit code="1641"/>
</upgrade>
<upgrade cmd="%comspec% /c if %PROCESSOR_ARCHITECTURE% == AMD64 msiexec /qn /i
"%SOFTWARE%\AppDeploy\WPKG Client\WPKG64_2009-01-24.msi" ALLUSERS=1
SETTINGSFILE="%WPKG_ROOT%\settings.xml"">
    <exit code="1641"/>
</upgrade>

The new upgrade command on the server is:

<upgrade cmd='msiexec /norestart /qn /log "%TMP%\WpkgClient.log" /i
"%SOFTWARE%\AppDeploy\WPKG Client\WPKG Client
1.3.9-%PROCESSOR_ARCHITECTURE%.msi" ALLUSERS=1
SETTINGSFILE="%WPKG_ROOT%\settings.xml"' >
    <exit code="1641" />
    <exit code="3010" />
</upgrade>

Now the upgrade command fails with error 1603, because the old files would be
used for upgrading, which have been deleted already.

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