Leopard image, flat packages

[pteeter]

Been a while since I posted to the forum, hope everyone is doing well.

Trying to use r405 to spin a Leopard image, running on a 10.5.8 machine.

It’s entirely possible I just missed it in the documentation so please tell me RTFM if needed but – at some point since r272 was a requirement for flat packages defined? I just rebuilt a bunch of custom setup pkgs to be flat, now they work with r405. But a few Apple created updates, necessary for Leopard, are not flat and are still making instadmg barf.

AirPort Base Station Update 2010-001 (5.5.1)
Front Row Update 2.1.7
Remote Desktop Client Update 3.3.2

The latest release of ARD still spits out a non-flat/old style pkg installer BTW…bugreport.apple.com that.

I’m perfectly happy to re-package those updates but it seems a shade unnecessary, no?

(Admittedly, this will probably be the last time I build Leopard images but this should work for backward compatibility support.)

[pteeter]

I will add that 2 of the 3 packages I mentioned are also required for SnowLeopard.

The non-flat/old style pkg installers for the Airport and Remote Desktop Client updates both install just fine when InstaDMG is run on a 10.6.5 machine when trying to build a 10.6 image.

Gonna pull some logs from a Leopard build and look through the bash code for instadmg.bash.

[foilpan]

do they work if you wrap them in a dmg? worth a shot…

[Allister Banks]

Are you using instaUp2Date? Without a doubt, any type of package works in 10.5.8 – I tested every vanilla catalog file in r407 myself on a MacPro and a MacBookPro from 2008.
For 10.5 custom packages modifying line 85 for your custom pkgs bundle identifier is necessary, but not for Apple pkgs.
How ‘pristine’ an install are you building from? I remember you mentioning an issue in the past, can you post the relevant parts of your debug log again please? Could it have anything to do with your installer binary, have you tried installing the same pkgs from the shell?
If you aren’t using(or aren’t interested in using) instaup2date, could you please run [code]openssl sha1 /path/to/each/pkg[/code] and post the results here? Thanks,

Allister

[pteeter]

[QUOTE][u]Quote by: foilpan[/u][p]do they work if you wrap them in a dmg? worth a shot…[/p][/QUOTE]

Not sure how it would make a difference.

[pteeter]

[QUOTE][u]Quote by: Allister[/u][p]Are you using instaUp2Date? Without a doubt, any type of package works in 10.5.8 – I tested every vanilla catalog file in r407 myself on a MacPro and a MacBookPro from 2008.
For 10.5 custom packages modifying line 85 for your custom pkgs bundle identifier is necessary, but not for Apple pkgs.
How ‘pristine’ an install are you building from? I remember you mentioning an issue in the past, can you post the relevant parts of your debug log again please? Could it have anything to do with your installer binary, have you tried installing the same pkgs from the shell?
If you aren’t using(or aren’t interested in using) instaup2date, could you please run [code]openssl sha1 /path/to/each/pkg[/code] and post the results here? Thanks,

Allister[/p][/QUOTE]

Always use InstaUp2Date. Not sure what you mean about ‘line 85’? Using either 10.5.6 install media from MacBookPro, 10.5.4 install media for Leo Server, build 10A432 of 10.6, or build 10A433 of 10.6 Server.

Have to re-rerun on Leopard with the non-flat packages to generate new logs.

Same non-flat packages work from CLI, with SnowLeopard host OS / target image + r405, & work with older r236 or r272 of instadmg.

It’s less of an issue now as re-pkg’ing the 3 updates worked.

But would like to get to the bottom of the issue.

[dead2sin]

InstaDMG does not support building Server images nor building the images themselves on Server OS. Try building a 10.5 image on a 10.5 Client machine and see what happens.

I believe he is referring to line 85 in the instadmg.bash file.

Hope that helps,

Nate

[pteeter]

Server vs client image isn’t the issue, however it’s quite simple to ‘trick’ instadmg into making server images (link in a server install DMG as ‘Mac OS X Install.dmg’, skip InstallerChoices.xml, and don’t run any custom pkgs to clear out the registration information). Have been building them successfully for a while.

When the failures have occurred it’s been 10.5 client on 10.5 client.

Am generating those logs right now. Will look at line 85 in bash script.

Thanks.

[pteeter]

Debug Log Example #1:
[code]Working on folder 01 AirPortUtility (08:54:40)
Copying folder /Volumes/zzz_Dev500GB/Mac_Imaging/build_directory/instadmg-r405/InstallerFiles/InstaUp2DatePackages/AirPortUtility.pkg into the target at /private/tmp/idmg.BTFj/idmg_mp.ezkT/private/tmp/idmg_pkg.AZw0
Installing AirPortUtility.pkg inside a chroot jail
PFPkg: No file found at path: /private/tmp/idmg_pkg.AZw0/AirPortUtility.pkg
PFPackage::packageWithURL – can’t instantiate package: /private/tmp/idmg_pkg.AZw0/AirPortUtility.pkg
Error the package path specified was invalid: ‘/private/tmp/idmg_pkg.AZw0/AirPortUtility.pkg’.
Removing the copied folder: /private/tmp/idmg.BTFj/idmg_mp.ezkT/private/tmp/idmg_pkg.AZw0
Folder 01 AirPortUtility done (08:54:57)[/code]
Debug Log Example #2:
[code] Working on folder 02 FrontRowUpdate2.1.7 (08:54:57)
Copying folder /Volumes/zzz_Dev500GB/Mac_Imaging/build_directory/instadmg-r405/InstallerFiles/InstaUp2DatePackages/FrontRowUpdate2.1.7.pkg into the target at /private/tmp/idmg.BTFj/idmg_mp.ezkT/private/tmp/idmg_pkg.ucMP
cp: /Volumes/zzz_Dev500GB/Mac_Imaging/build_directory/instadmg-r405/InstallerFiles/InstaUp2DatePackages/FrontRowUpdate2.1.7.pkg//Contents/Resources/FrontRowUpdate2.1.7.sizes: No such file or directory
Installing FrontRowUpdate2.1.7.pkg inside a chroot jail
PFPkg: No file found at path: /private/tmp/idmg_pkg.ucMP/FrontRowUpdate2.1.7.pkg
PFPackage::packageWithURL – can’t instantiate package: /private/tmp/idmg_pkg.ucMP/FrontRowUpdate2.1.7.pkg
Error the package path specified was invalid: ‘/private/tmp/idmg_pkg.ucMP/FrontRowUpdate2.1.7.pkg’.
Removing the copied folder: /private/tmp/idmg.BTFj/idmg_mp.ezkT/private/tmp/idmg_pkg.ucMP
Folder 02 FrontRowUpdate2.1.7 done (08:55:11)[/code]
The cp error with FrontRowUpdate2.1.7 seems bogus, find on the file in the pkg bundle:
[code]% pwd
/Volumes/zzz_Dev500GB/Mac_Imaging/build_directory/Current/InstallerFiles/InstaUp2DatePackages/FrontRowUpdate2.1.7.pkg
% find . -name \*.sizes
./Contents/Resources/FrontRowUpdate2.1.7.sizes[/code]
Debug Log Example #3:
[code] Working on folder 10 RemoteDesktopClient (09:10:55)
Copying folder /Volumes/zzz_Dev500GB/Mac_Imaging/build_directory/instadmg-r405/InstallerFiles/InstaUp2DatePackages/RemoteDesktopClient.pkg into the target at /private/tmp/idmg.BTFj/idmg_mp.ezkT/private/tmp/idmg_pkg.7pIR
cp: /Volumes/zzz_Dev500GB/Mac_Imaging/build_directory/instadmg-r405/InstallerFiles/InstaUp2DatePackages/RemoteDesktopClient.pkg//Contents/Resources/RemoteDesktopClient.sizes: No such file or directory
Installing RemoteDesktopClient.pkg inside a chroot jail
PFPkg: No file found at path: /private/tmp/idmg_pkg.7pIR/RemoteDesktopClient.pkg
PFPackage::packageWithURL – can’t instantiate package: /private/tmp/idmg_pkg.7pIR/RemoteDesktopClient.pkg
Error the package path specified was invalid: ‘/private/tmp/idmg_pkg.7pIR/RemoteDesktopClient.pkg’.
Removing the copied folder: /private/tmp/idmg.BTFj/idmg_mp.ezkT/private/tmp/idmg_pkg.7pIR
Folder 10 RemoteDesktopClient done (09:11:01)[/code]
Same result with this .sizes file.

As for line 85 in instadmg.bash, very interesting. In my Leopard InstaUp2Date catalogs, the *only* non-flat pkg installer that has worked and continues to work is a customized createUser pkg installer. Surely I can append to the list of CHROOT_EXCLUDED_CODES & maybe that’s the intent of the variable.

Has anyone interested in this thread explicitly tried a non-flat/old style pkg installer with a Leopard-based instadmg run – download any of the 3 mentioned in the logs above? I admit my attention to that detail was remiss until now, I used to use Iceberg and that was the tool used to create many of the custom packages that were breaking with r405. I have been using Packages for quite some time and used it to re-pkg the offending non-flat pkg installers.

Next step is to exclude the FrontRow, AirPortUtility, & RemoteDesktopClient installers.

[Author]

Posts