site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com K.Mino, Chris Hi, Chris. Thanks for your reply. My package is a simple package, not a meta package. Can you send me the Info.plists from the two packages and the names of these packages? I will send my plist files to Chris privately, but differences between those plists are the following 2 points. * Only the new package has CFBundleIdentifier. * Only the new package has IFPkgFlagInstalledSize. As told in my last post, removing CFBundleIdentifier from Info.plist of the new package enables the upgrade process correctly. So, this problem seems to come from the existence or implementation of Bundle ID. Regards, K.Mino ----- Original Message ----- From: "Christopher Ryan" <ryanc@apple.com> To: "Koichiro Mino" <mino.koichiro@fxpsc.co.jp> Cc: <installer-dev@lists.apple.com> Sent: Saturday, January 07, 2006 1:09 AM Subject: Re: Upgrade process fails on Tiger What is your package layout? Are you using a meta package? Can you send me the Info.plists from the two packages and the names of these packages? There is a bug in 10.4 where the reason for not being able to install doesn't percolate up to the top and display in the Target Select panel. Either way, the installer has decided your package can't be installed and will not let you further. Chris Hi, all. My installer fails to upgrade modules on Tiger (10.4.3). (No problem on Panther.) In the last step of upgrade process, the 'Install' button (not 'Upgrade') appears on the Installer's window, and clicking it raises the error message which tells that there is nothing to install. Both of my old & new installers have the same CFBundleName, and each has BundleVersions.plist described correctly. The difference between them is that only the new has CFBundleIdentifier in its Info.plist (because Tiger's PackageMaker requires that). This issue seems to come from the fact only the new installer has the ID. Upgrade works fine when removing it from the new one or adding it to the receipt of the old. Is there any way to make my new installer work correctly on upgrade with the old one? Regards, K.Mino _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/ryanc%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... I have responded directly off list, but I will share my findings with the list as well. Because the old package does not have a CFBundleIdentifier and since there is no CFBunldeShortVersion string (and Minor and Major versions are set to 0 in both) the installer is not seeing these packages are equal, and it cannot say for sure that it newer, so it considers itself a downgrade and does not allow install. The workaround is to set the CFBundleShortVersion of the new package to something other then 0 that makes sense. Ideally all packages would have CFBundleIdentifier and CFBundleShortVersion, but since you can't change what you have already shipped, you should start adding them now. What is your package layout? Are you using a meta package? I searched some clue in the archive, and found this post. http://lists.apple.com/archives/installer-dev/2005/Jun/ msg00000.html In my case, however, setting the unique ID doesn't solve the problem. This email sent to ryanc@apple.com This email sent to site_archiver@lists.apple.com