site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com User-agent: Microsoft-Entourage/11.1.0.040913 A sad update... After yet another day lost on this insanity, I am giving up... I managed to isolate the issue to the fact that its related to the fact that one of the items my postflight moves has a resource fork. Sure enough, I read a bit and learn that cp on 10.3 doesn't do them (an is throwing the package exception that I'm seeing?). Fine, I say, I'll install CpMac to /tmp and use *that* to move my .bundle (that has the resource) to where it needs to go. Even more outrageously, when I now install it under 10.3 sometimes it errors out, and sometimes it's successful (my guess is that CpMac is erroring out in certain situations when the dest file already exists--I don't know what situations--its not documented). So, basically, after two days of zero productivity and no answers, it's time to ditch PackageMaker and go with a readme containing install instructions. It's a little disappointing that 10.3 can't suit a lowly developer like me who just wants to move a couple files around during an install, but here I are. More specifically, I wish I could understand why 10.3 wasn't patched so that it'd be on par with any installer made for 10.4. The whole reason I got in the crisis that I'm in now (where all my 10.3 users are sending me angry emails) is that I assumed a simple package that worked under 10.4 would work under 10.3. Sigh. ----- Hey guys.. Hopefully folks here can solve this one--I would have thought it would have been addressed by now, but I didn't get any hits from an archive search... So I have my shiny new package built by PackageMaker 2.0, and all is well tiger... So we launch the new version of our software this morning and emails from 10.3 users start pouring in about the installer erroring out. I don't have a 10.3 machine handy, so I has to go to some lengths to get access to one, and look at the console, and I see: 2005-06-08 13:20:41.371 Installer[657] Exception raised during posting of notification. Ignored. exception: Some files for ... may not have been written correctly. (code 1) 2005-06-08 13:24:53.585 Installer[692] Exception raised during posting of notification. Ignored. exception: Some files for ... may not have been written correctly. (code 1) The only thing semi-unusual about the installer is that the installed files are alongside the installer and are moved to user locations via the preflight script. Therefore, there's no source files to speak of inside the package. Apparently, the 10.3 package installer crashes when there's no files to install, so I put in a little .txt file placeholder and I have the package's default output location set to "/tmp" (and the crash goes away). Now I'm just left with the above console errors with the package saying errors occurred during installation. Again, everything works fine under Tiger (and I have no info for if it works on Jaguar). If you'd like to try the installer, it's at: http://seeyourmusic.com/g-force/dl/G-Force_300_iTunes.sit Sorry if I missed something obvious, and I appreciate people's time. Thanks in advance, Andy _______________________________________________ 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... This email sent to site_archiver@lists.apple.com