[wpkg-users] ZigGenius 6.1 Update successfull but wpkg.xml not updated

Hello, yesterday, I integrated ZipGenius 6.1. On some PCs, the update works as expected. But on some the Update was successfull but wpkg.xml not updated. --- Command 'cmd /C taskkill /F /IM zipgenius.exe' returned exit code [128]. This exit code is not an error. Command in installation of ZIP-Ge

[wpkg-users] Basic behaviour of WPKG

I've been thinking about WPKGs default behaviour (following from earlier discussions) and I'd like to start a genuine discussion on changing its current behaviour. Currently, WPKG will attempt to remove an existing package from the local compuer wpkg.xml file if it decides that an existing packag

[wpkg-users] locale' is undefined Error number: 800a1391

Hi, I'm trying to set up WPKG for the first time. Everything seems to work fine until I hit this error: 'locale' is undefined Error number: 800a1391 followed by: Script execution: failure. Exit code: 2 This seems to happen whenever I try and install a package. If I just use a simply comm

Re: [wpkg-users] locale' is undefined Error number: 800a1391

Hi Simon, Simon Kelsall wrote: > I'm trying to set up WPKG for the first time. Everything seems to work > fine until I hit this error: 'locale' is undefined Error number: 800a1391 > followed by: Script execution: failure. Exit code: 2 Looks like an error thrown by wpkg.js. Which version of WPKG a

Re: [wpkg-users] ZigGenius 6.1 Update successfull but wpkg.xml not updated

Johannes.Brix wrote: Hello, yesterday, I integrated ZipGenius 6.1. On some PCs, the update works as expected. But on some the Update was successfull but wpkg.xml not updated. --- Command 'cmd /C taskkill /F /IM zipgenius.exe' returned exit code [128]. This exit code is not an error. Command in in

Re: [wpkg-users] locale' is undefined Error number: 800a1391

Quoting Rainer Meier : Which version of WPKG are you using (not var WPKG_VERSION = "1.1.1"; Please attach a full debug log. "HKCU\Control Panel\International\Locale". Value is 0809 Maybe a cscript error. On which systems/OS are you running wpkg.js? Windowsm XP Pro with service

Re: [wpkg-users] Basic behaviour of WPKG

> > > I've been thinking about WPKGs default behaviour (following from earlier > discussions) and I'd like to start a genuine discussion on changing its > current behaviour. > > Currently, WPKG will attempt to remove an existing package from the local > compuer wpkg.xml file if it decides that

Re: [wpkg-users] ZigGenius 6.1 Update successfull but wpkg.xml not updated

Hello, I changed the flag reboot="false" to reboot="true" to take into account that ZipGenius needs a reboot after deinstallation before an update is possible. Changing back to the original value, the update of wpkg.xml worked fine. This explaines why it worked on some PCs, because wpkg

Re: [wpkg-users] ZigGenius 6.1 Update successfull but wpkg.xml not updated

Hi Johannes, johannes.b...@evidian.com wrote: > So, the problem is, how can I change a package, e.g. flags so that it will > be taken into account > by a client. Increase the package revision. Please note that this will make WPKG to re-execute the update commands. Probably your checks are inap

Re: [wpkg-users] ZigGenius 6.1 Update successfull but wpkg.xml not updated

Hello, here is the package definition NEW build: == OLD build: = --- Johannes Ra

Re: [wpkg-users] ZigGenius 6.1 Update successfull but wpkg.xml not updated

Hi Johannes, johannes.b...@evidian.com wrote: > here is the package definition > > > > NEW build: > == > >id="zipgenius" > name="ZIP-Genius" > revision="610" > reboot="false" > priority="1"> > > > > >cmd='\\%WPK

Re: [wpkg-users] patches for minor typos, status message suggestion

Hi Malte, Malte Starostik wrote: > there are a few occurrences of "chained" misspelt as "chaned" both in > comments > and a log message (found while trying to write a log parser). wpkg-typos.diff > fixes this. Thanks for reporting. I just checked in the fixes (and found some others).

Re: [wpkg-users] Basic behaviour of WPKG

Hi Simon, simplesi wrote: > > I've been thinking about WPKGs default behaviour (following from earlier > > discussions) and I'd like to start a genuine discussion on changing its > > current behaviour. OK, let's try to get a common understanding of the ideas first. > > Currently, WPKG will atte