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

[Johannes.Brix at evidian.com]

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 was running before 
I cnaged the flag.

So, the problem is, how can I change a package, e.g. flags so that it will 
be taken into account
by a client.

---
Johannes






Pendl Stefan <stefan.pendl at haidlmair.at>
10.07.2009 12:45

 
        To:     "Johannes.Brix at evidian.com" <Johannes.Brix at evidian.com>, 
"wpkg-users at lists.wpkg.org" <wpkg-users at lists.wpkg.org>
        cc: 
        Subject:        AW: [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 installation of ZIP-Genius returned exit code [128]. This exit
code indicates success.
Command '\\%WPKG-Master%\wpkg\zipgenius\zg6.1.0.1000std.exe /VERYSILENT
/NORESTART /NOICONS' returned exit code [0]. This exit code is not an
error.
Command in installation of ZIP-Genius returned exit code [0]. This exit
code indicates success.
Installation of ZIP-Genius successful, system rebooting.
System reboot was initiated but overridden.
---

ZipGenius is properly installed and works fine, but the local wpkg.xml is
not updated.
Next run of the update script tries to install again ...

Any hints?

Thank you and kind regards,
Johannes

---------------------------------------------------------------------------
Hi Johannes,
there was a reboot and this reboot occurred directly after ZIPgenius was 
installed.
What is the reboot attribute set for this package?

You may consider setting it differently, check the packages.xml page at 
the WPKG site, which was updated yesterday to include a better description 
of what value causes which behavior.

---
Stefan