] [mailto:[EMAIL PROTECTED] On Behalf Of Marco Gaiarin
Sent: 22 April 2008 09:30
To: wpkg-users@lists.wpkg.org
Subject: Re: [wpkg-users] WPKG client upgrade
Mandi! Rainer Meier
In chel di` si favelave...
I don't think it is very hidden or a hack. Just did a quick (very quick)
Google search
I tested this upgrade (I have condition=versionequalto, on website is
condition=sizeequals and value=1.0.0.8)
package
id=wpkg
name=WPKG Client 1.2.1
revision=2
reboot=false
priority=3000
When I upgrade WPKG client this way (without start):
upgrade cmd='%COMSPEC% /C %SOFTWARE%\wpkg\wpkg_upgrade.bat' /
it doesn't work, on client I see errors:
Product: WPKG -- Error 1722. There is a problem with this Windows Installer
package. A program run as part of the setup did not finish
Brian May schrieb:
Tomasz Chmielewski wrote:
I added some (hopefully) more detailed instructions and verified that
they work on my workstation:
http://wpkg.org/WPKG
Could you verify if it works for you?
There seem to be some typos, I changed it to:
package
id=wpkg
name=WPKG
Brian May schrieb:
Brian May wrote:
It seems to work.
Can I please confirm why you use start? Is this for extra debugging?
Looks like a race condition exists, due to using start. The process is
started for upgrading wpkg, and at the same time wpkg continues and
checks the latest version
Vladimír Pšenička schrieb:
When I upgrade WPKG client this way (without start):
upgrade cmd='%COMSPEC% /C %SOFTWARE%\wpkg\wpkg_upgrade.bat' /
it doesn't work, on client I see errors:
Product: WPKG -- Error 1722. There is a problem with this Windows Installer
package. A program run as
Vladimír Pšenička schrieb:
Yes I use logon delay feature, I try batch file with killing
wpkgmessage.exe and I have no luck, still no upgrade is done...
I try upgrade cmd with and without start
upgrade cmd='%COMSPEC% /C %SOFTWARE%\wpkg\wpkg_upgrade.bat' /
upgrade cmd='%COMSPEC% /C start
Rainer Meier schrieb:
(...)
It's an ugly work-around trying to kill applications which are currently
running just to unlock these files. Especially since you never know
which other applications (indexing serivice, 3rd party tools...) open
the same file. So replacing a file might fail at
Hi Tomasz,
Tomasz Chmielewski wrote:
- there is a switch/hack, but we don't know it yet
I don't think it is very hidden or a hack. Just did a quick (very quick)
Google search and found the following interesting pages:
Tomasz Chmielewski wrote:
I asked some Microsoft MVPs and it doesn't look too promising:
1) Most (all?) installers do an upgrade by stopping the service first
Another approach might be to look at what is done my Mozilla Firefox,
Mozilla Thunderbird, etc.
I am not sure of the details, I
Vladimír Pšenička schrieb:
Is possible to upgrade WPKG client from 1.2-rc6 to 1.2.1 by itself
automaticaly after reboot (not directly running wpkg.js) on remote machines?
I tested upgrade (http://wpkg.org/WPKG) and it doesn't work:
I added some (hopefully) more detailed instructions and
Tomasz Chmielewski wrote:
I added some (hopefully) more detailed instructions and verified that
they work on my workstation:
http://wpkg.org/WPKG
Could you verify if it works for you?
There seem to be some typos, I changed it to:
package
id=wpkg
name=WPKG Client 1.2.1
Brian May wrote:
It seems to work.
Can I please confirm why you use start? Is this for extra debugging?
Looks like a race condition exists, due to using start. The process is
started for upgrading wpkg, and at the same time wpkg continues and
checks the latest version is already installed -
Is possible to upgrade WPKG client from 1.2-rc6 to 1.2.1 by itself
automaticaly after reboot (not directly running wpkg.js) on remote machines?
I tested upgrade (http://wpkg.org/WPKG) and it doesn't work:
package
id=wpkg
name=WPKG Service
revision=2
14 matches
Mail list logo
