Re: [wpkg-users] WPKG Client 1.3.3 released (testing release)

2008-07-21 Thread Marco Gaiarin
Mandi! Tomasz Chmielewski In chel di` si favelave... > Read the source, Luke ;) > Look for "Returns the package reboot attribute value". ...that is more or less what on: http://bugzilla.wpkg.org/show_bug.cgi?id=86 The source say me: * "false" No reboot unless one is defined at co

Re: [wpkg-users] WPKG Settings update through WPKG

2008-07-21 Thread Tomasz Chmielewski
Jens Geile schrieb: > Hi, > > today I tried to create a little package to update the WPKG settings on all > clients and used the script found at http://wpkg.org/WPKG as base: > > reboot="true" execute="once"> > > > > > > But everytime I ran the script the command failed and return a

Re: [wpkg-users] WPKG Client 1.3.4 stop service

2008-07-21 Thread Tomasz Chmielewski
Marc Hennes schrieb: > Hi, > > I am testing WPKG Client 1.3.4 at the moment and I have some issue with the > stop service feature. > After wpkg.js ran with /synchronize and nothing was installed the service > doesn't stop. In windows services GUI WPKG Service is marked as stopping > ("wird been

Re: [wpkg-users] The network location cannot be reached

2008-07-21 Thread Tomasz Chmielewski
Mark Nienberg schrieb: > Tomasz Chmielewski wrote: > >> Nevertheless, try if the issue is not fixed in 1.3.x. >> > > Here is a log from client 1.3.4: > > 2008-07-08 17:18:09 -> Starting WPKG on startup > 2008-07-08 17:18:09 -> Before create shared memory: successfuly done. > 2008-07-08 17:18:09

Re: [wpkg-users] Installer for windows 64 bits

2008-07-21 Thread Tomasz Chmielewski
Rainer Meier schrieb: > Hi Tomasz, > > Tomasz Chmielewski wrote: >> Which should happen after 32 bit version of WPKG Client 1.4.0 is >> released. A month or so, time permits. I'm still waiting for remarks, >> issues etc. for a "testing" 1.3.2. > > Which is entirely fine I think. The current wra

[wpkg-users] WPKG Agent Settings File

2008-07-21 Thread Leon Hedding (ICT)
For installation of the WPKG Agent would it be possible do SETTINGSFILE=settings.xml instead of --SETTINGSFILE=LongPathMaybeWithSpaces\settings.xml and assume that the settings file is in the same location as the running directory and use a MSI Custom Property the settings file? When I specify the