On Mon, 2009-05-04 at 20:44 +0200, Tomasz Chmielewski wrote: > Craig White schrieb: > > I have updated the Apple installer to a version newer than that listed > > on the wiki... > > > > I am including the output of each at the bottom of this e-mail (watch > > the line wraps) but I did have one issue that is confusing me. > > > > When upgrading itunes application, the msiexec exit code seems to emit > > and exit code 3010 and not 0 which makes wpkg think it has failed and > > since the applemobile.xml and quicktime.xml 'require' itunes, they fail > > to upgrade and the computer is mostly unusable because the > > iTunesHelper.exe application goes into a race condition when a user logs > > in. Subsequent restart (or restart of wpkg service) then realizes that > > the correct itunes version actually is installed and then proceeds to > > process the updates for applemobile.xml and quicktime.xml and everything > > is happy. So I'm gathering that the upgrade from say itunes 8.0.1.11 to > > 8.1.1.10 actually requires a restart. > > Exit code 3010 from msiexec means that a reboot is needed: > > http://wpkg.org/MSI:_Windows_Installer > > > > Should I just remove the '/norestart' parameter from the upgrade command > > for itunes? > > See also: > > http://wpkg.org/Rebooting ---- so I am gathering that doing it this way makes more sense (the exit code in 'upgrade' section and subsequent reboot=true will override the reboot=false in the main section)... <?xml version="1.0" encoding="UTF-8"?> <packages> <package id="itunes" name="Apple iTunes" revision="8.1.1.10" reboot="false" priority="1"> <check type="file" condition="versiongreaterorequal" path="% PROGRAMFILES%\iTunes\iTunes.exe" value="8.1.1.10"/> <install cmd="msiexec.exe /qn /norestart /i %SOFTWARE%\iTunes\8.1.1.10 \iTunes.msi" /> <upgrade cmd="msiexec.exe /qn /i %SOFTWARE%\iTunes\8.1.1.10 \iTunes.msi"> <exit code="3010" reboot="true" /> <exit code="0" /> </upgrade> <remove cmd="msiexec.exe /qn /uninstall {5EFCBB42-36AB-4FF9-B90C-E78C7B9EE7B3}" /> </package> </packages> Thanks Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |