September 2015 - Installer-dev

Re: Problem with preflight script removing file
by Howard Moon 21 Sep '15

21 Sep '15

Hi Pepijn, yes, I tried adding that. But the problem seems to be that the decision to skip the plug-in component occurs BEFORE the pre-install script is run. (I had said "pre-flight" previously, but in Packages, it is called "pre-install".) So no matter what my script does, the installer has already decided it will not install my plug-in. Is there any way to get around this, other than to run an uninstaller separately before running the new installer? Thanks, Howard > On Sep 21, 2015, at 7:49 AM, Pepijn Bruienne <pepijn(a)mac.com> wrote: > > Howard, if you're manually removing files you probably also need to make sure the installer DB has no record of it. Have you tried a pkgutil --forget <your pkg id> in the preflight? > > Thanks, > Pepijn. > > > -- > Pepijn Bruienne > Sent with Airmail > > On September 21, 2015 at 10:47:40 AM, Howard Moon (howard(a)antarestech.com) wrote: > >> The installer.log file says this: >> >> > Sep 21 07:27:27 Howards-MacBook-Pro.local installd[467]: PackageKit: Skipping component "com.antares.Mic Mod EFX.aaxplugin" (2.0.2-2.0.2-*-*) because the version 4.0.0-4.0.0-*-* is already installed at /Library/Application Support/Avid/Audio/Plug-Ins/Antares Audio Technologies/Mic Mod EFX.aaxplugin. >> > >> This had previously WORKED on MY system, but no longer. Now I am getting the same behavior as my testers reported, which is that the new file is not installed. (Which is a good thing, since it’s hard to diagnose a problem one cannot replicate!) Apparently, the pre-install script is not running prior to the installer software detecting that the new version has an older version number, so even though the script runs and removes the plug-in, the installer skips it because it cannot update to an older version. >> >> How can I resolve this? >> >> Thanks, >> Howard >> >> >> > On Sep 21, 2015, at 7:12 AM, Howard Moon <howard(a)antarestech.com> wrote: >> > >> > Hi, >> > >> > One of our installers is removing the old bundle (via a pre-flight script), but failing to install the new bundle. We need help resolving the situation. >> > >> > We have a Packages-built installer (.pkg) which includes a pre-flight script to remove a particular audio plug-in bundle before continuing to install the new one. This was done because certain installations of the old bundle had version numbers that were incorrect - higher than the new bundle’s version number - and so are not replaced automatically. For our VST3 bundles, this is working correctly, but for our AAX bundles, something in the system seems to be holding onto the deleted bundle, preventing writing of the new one. After the installer runs, the old bundle is gone, but the new one has not been written. The user has to run the installer a *second* time in order to get it ti install the new bundle. Obviously, that is not a good result. >> > >> > Is there some reason for this behavior? Perhaps ownership of the containing folder hierarchy or something? More importantly, is there some way to ensure that this does not happen? >> > >> > The script line to remove the bundle is simple enough. Here it is. Is there something that I can do to modify the script to make the system let go of the old bundle and allow the new one to write? >> > >> > rm -fR /Library/Application\ Support/Avid/Audio/Plug-Ins/Antares\ Audio\ Technologies/Mic\ Mod\ EFX.aaxplugin >> > rm -fR /Library/Application\ Support/Avid/Audio/Plug-Ins/Mic\ Mod\ EFX.aaxplugin >> > >> > (That second line is just in case the plug-in was moved to the root of Plug-Ins folder, which we have seen happen.) >> > >> > Any thoughts? >> > >> > Thanks, >> > Howard >> > >> > >> > >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Installer-dev mailing list (Installer-dev(a)lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/installer-dev/pepijn%40mac.com >> >> This email sent to pepijn(a)mac.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Problem with preflight script removing file
by Pepijn Bruienne 21 Sep '15

21 Sep '15

_______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Problem with preflight script removing file
by Howard Moon 21 Sep '15

21 Sep '15

The installer.log file says this: > Sep 21 07:27:27 Howards-MacBook-Pro.local installd[467]: PackageKit: Skipping component "com.antares.Mic Mod EFX.aaxplugin" (2.0.2-2.0.2-*-*) because the version 4.0.0-4.0.0-*-* is already installed at /Library/Application Support/Avid/Audio/Plug-Ins/Antares Audio Technologies/Mic Mod EFX.aaxplugin. > This had previously WORKED on MY system, but no longer. Now I am getting the same behavior as my testers reported, which is that the new file is not installed. (Which is a good thing, since it’s hard to diagnose a problem one cannot replicate!) Apparently, the pre-install script is not running prior to the installer software detecting that the new version has an older version number, so even though the script runs and removes the plug-in, the installer skips it because it cannot update to an older version. How can I resolve this? Thanks, Howard > On Sep 21, 2015, at 7:12 AM, Howard Moon <howard(a)antarestech.com> wrote: > > Hi, > > One of our installers is removing the old bundle (via a pre-flight script), but failing to install the new bundle. We need help resolving the situation. > > We have a Packages-built installer (.pkg) which includes a pre-flight script to remove a particular audio plug-in bundle before continuing to install the new one. This was done because certain installations of the old bundle had version numbers that were incorrect - higher than the new bundle’s version number - and so are not replaced automatically. For our VST3 bundles, this is working correctly, but for our AAX bundles, something in the system seems to be holding onto the deleted bundle, preventing writing of the new one. After the installer runs, the old bundle is gone, but the new one has not been written. The user has to run the installer a *second* time in order to get it ti install the new bundle. Obviously, that is not a good result. > > Is there some reason for this behavior? Perhaps ownership of the containing folder hierarchy or something? More importantly, is there some way to ensure that this does not happen? > > The script line to remove the bundle is simple enough. Here it is. Is there something that I can do to modify the script to make the system let go of the old bundle and allow the new one to write? > > rm -fR /Library/Application\ Support/Avid/Audio/Plug-Ins/Antares\ Audio\ Technologies/Mic\ Mod\ EFX.aaxplugin > rm -fR /Library/Application\ Support/Avid/Audio/Plug-Ins/Mic\ Mod\ EFX.aaxplugin > > (That second line is just in case the plug-in was moved to the root of Plug-Ins folder, which we have seen happen.) > > Any thoughts? > > Thanks, > Howard > > > _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Problem with preflight script removing file
by Howard Moon 21 Sep '15

21 Sep '15

Hi, One of our installers is removing the old bundle (via a pre-flight script), but failing to install the new bundle. We need help resolving the situation. We have a Packages-built installer (.pkg) which includes a pre-flight script to remove a particular audio plug-in bundle before continuing to install the new one. This was done because certain installations of the old bundle had version numbers that were incorrect - higher than the new bundle’s version number - and so are not replaced automatically. For our VST3 bundles, this is working correctly, but for our AAX bundles, something in the system seems to be holding onto the deleted bundle, preventing writing of the new one. After the installer runs, the old bundle is gone, but the new one has not been written. The user has to run the installer a *second* time in order to get it ti install the new bundle. Obviously, that is not a good result. Is there some reason for this behavior? Perhaps ownership of the containing folder hierarchy or something? More importantly, is there some way to ensure that this does not happen? The script line to remove the bundle is simple enough. Here it is. Is there something that I can do to modify the script to make the system let go of the old bundle and allow the new one to write? rm -fR /Library/Application\ Support/Avid/Audio/Plug-Ins/Antares\ Audio\ Technologies/Mic\ Mod\ EFX.aaxplugin rm -fR /Library/Application\ Support/Avid/Audio/Plug-Ins/Mic\ Mod\ EFX.aaxplugin (That second line is just in case the plug-in was moved to the root of Plug-Ins folder, which we have seen happen.) Any thoughts? Thanks, Howard _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0