[Allister Banks]

Hey there,

You may want to post this over at the instadmg.googlecode.com project’s issues section. I can’t speak to why or how this behavior changed, but I can confirm it’s happening since 292. I can’t speak for what is considered a warranty’d feature and what’s not, so I can’t say what your chances are. I, too, liked the simplicity of not needing to explicitly set the order of certain sets.
It would of course be faster if you can diff 266 and 292 and make sense of why this stopped working, and if you can figure it out, please share with the group. Thanks,

Allister

[Allister Banks]

Hey all,
I’m pleased to report the change larkost checked in last night has fixed the symptom I’ve described. [code]svn update[/code] is your friend. Thanks!

Allister

[Allister Banks]

Hey there,
Please post which version of instaUp2Date and instadmg you are using, unless you downloaded the zip from code.google.com. Your catalog entry probably isn’t the issue.
I am working on documentation so I sound less as if I’m spreading my feelings that it works like voodoo sometimes, but that’s just because I need to learn more about the code. There’s a lot better exception handling recently, but the error you’re running into is one of the ones where I ‘punt’ and try it as a DMG instead, meaning there’s no need to pull the mpkg out. And you should be able to put it anywhere, but I choose either the /Caches/InstaUp2DateCache or /Installer/InstaUp2DatePackages folders.
Give it another shot(you’ll want to re-do the checksum as well, since this is the dmg now) and let us know. Thanks,
Allister

[Allister Banks]

Hmmm, I’m not sure how best to post the full setup, the catalog file only has three customizations on top of a vanilla 10.6(firefox in third-party, and create user & clearreg in system settings.) I’m calling it with nothing other than –process, and this was after a reboot, it bailed early when I interrupted a earlier run so I made sure to restart. I reviewed the debug log extensively vs. the plain ‘pkgs in folders’ method, and it seems that each install is thinking its done early, (200 seconds early in the case of 10.6.3v1.1) and can’t remove the temp directories:
[code] Unmounted the Package DMG image from /private/tmp/InstaDMG_temp_folder.vYjUzl/mount_point.uC3Ojn
Removing the copied folder: /private/tmp/InstaDMG_temp_folder.vYjUzl/mount_point.kkyWAa
rm: /private/tmp/InstaDMG_temp_folder.vYjUzl/mount_point.kkyWAa/System/Library: Directory not empty
rm: /private/tmp/InstaDMG_temp_folder.vYjUzl/mount_point.kkyWAa/System: Directory not empty
rm: /private/tmp/InstaDMG_temp_folder.vYjUzl/mount_point.kkyWAa: Resource busy [/code]

I’ll do another run of instaUp2Date and ‘pkgs in folders’ with only one package each to see if I can pinpoint anything.

Please let me know what other info I can provide, and you’ll pardon me taking this opportunity to mention I still don’t know how to pass other flags to instadmg via instaUp2Date’s –process flag. Thanks as always, Allister

[Allister Banks]

Hey there,

I am experiencing the same issue when instadmg is called by instaUp2Date, but not when using the same packages, things just seem to be stricter now when it comes to having to separate out a package per folder. We may have to wait on larkost to respond to why instaUp2Date seems to have lost functionality of passing updates to instadmg.bash.

Allister

[Allister Banks]

Going back to the first question malroy had, it bothered me that I gave an incomplete answer. If you’re copy-pasting your Third Party Software section, I just wanted to verify that theres actual tab characters between the three parts of each line.
Also, the sha1 checksum actually needs to be appended to the filename, so for example your first package, once it’s dmg’d(I haven’t tried with a plain pkg yet) would have this filename: [code]EPSONPrinterDrivers sha1-5abfb7dfe780a87382f16b78ba02d2d389420fbb.dmg[/code]

Allister

[Allister Banks]

Well then.
These are two possibly related issues, but let me please check basics for both scenarios:
Are you using the install disc that came with the laptop? Don’t expect the image you’d build using that disc to work on any other models(there are almost certainly dependencies for the new graphics hdwe at least,) but it is doubtful the 10.6.3 combo update contained drivers for that model, so until 10.6.4 you’d need to use the bundled disc.

malroy, the instaUp2Date error message does state it’s expecting a dmg, so please repackage the pkg using disk utility and re-checksum.

If it doesn’t hit an exception and pops an image out, you normally wouldn’t think the tool has malfunctioned and produced something corrupted, so I’d consider that possibility last. Sorry if this isn’t as helpful or clear as it could be, please ask more questions if there’s something I’m saying that isn’t clear.

Allister

[Allister Banks]

Thanks for your patience guys, we should try to make this easier at some point.
I can’t say why it worked on the first try for me without the less-than-helpful error message, all I can say is make sure your path is right; I drag-dropped the disc icon from the top of the windows into terminal to figure out which one I wanted(in the example below, two other installers were mounted so this got the suffix ‘2’. YMMV:
[code]sudo installer -showChoicesXML -pkg /Volumes/Mac\ OS\ X\ Install\ DVD\ 2/System/Installation/Packages/OSInstall.mpkg[/code]
and it spit out the options, this disc is build 10C2234.

Here’s the end result, parsed to only include the ones you should interact with:

choiceIdentifier
Host_PrinterDrivers
—
choiceIdentifier
Popular_PrinterDrivers
—
choiceIdentifier
All_PrinterDrivers
—
choiceIdentifier
PrinterDriversGroup
—
choiceIdentifier
AdditionalFonts
—
choiceIdentifier
Japanese
—
choiceIdentifier
German
—
choiceIdentifier
French
—
choiceIdentifier
Spanish
—
choiceIdentifier
Italian
—
choiceIdentifier
Dutch
—
choiceIdentifier
Danish
—
choiceIdentifier
Finnish
—
choiceIdentifier
Korean
—
choiceIdentifier
Norwegian
—
choiceIdentifier
Russian
—
choiceIdentifier
Swedish
—
choiceIdentifier
BrazilianPortuguese
—
choiceIdentifier
SimplifiedChinese
—
choiceIdentifier
TraditionalChinese
—
choiceIdentifier
Portuguese
—
choiceIdentifier
Polish
—
choiceIdentifier
LanguageTranslations
—
choiceIdentifier
X11
—
choiceIdentifier
Rosetta
—
choiceIdentifier
QuickTimePlayer7

FYI, I checked it with the -target flag pointing at an empty volume as well, same difference.

[Allister Banks]

I don’t have one of those iMacs or the most recent mini(without server), but I can only say the most recent retail-boxed disc(10.6.3) SHOULD work. I’ve seen this error when attempting to get installer choices from the Server OS disc, which hasn’t worked for me yet either.

Anyone have either the new 10.6.3 disc or one of these machine-specific discs?
http://support.apple.com/kb/ht1159

Allister

[Allister Banks]

Hey sketch,

This is 10.6 client, right ? What is the build number of the OS on the disc?

Allister

[Allister Banks]

Hey Jowy,

Please use a more recent version to make 10.6 images, you’d find a stable version here: http://instadmg.googlecode.com/files/InstaDMG.zip. Another thing to make sure of is you aren’t trying to create this image on a PPC or 10.5 machine, as that will not work, AFAIK time has not been invested in making it possible to make a different point-version OS build from the running system. Does that make sense? Thanks, I don’t expect this to instantly solve all your answers, but give it a shot and let us know.

Allister

[Allister Banks]

Hey sketch,

The -target flag and path after it is unnecessary.

Allister

[Allister Banks]

Hey there,
I’m personally not maintaining 10.5 images at this point so I can’t be of too much help, but please do try to use a more recent version of instadmg than 1.4b4. There will be less people using the older versions, and significant code cleanup and changes have happened since back then.

Allister

[Allister Banks]

Hey Jowy,

You are not required to do anything that post described to use functionality that cannot be re-enabled at this point. Other plumbing changes happened under the hood in months past to regain some of that chroot functionality, but I think your issue may possibly be more fundamental.
Could you paste your package.log, anything suspicious looking in your debug.log, and describe how you’re setting up your build train? Please also let us know what version of instadmg you’re using(best way is to find the revision number at the beginning of the instadmg.bash file.) Thanks,

Allister

[Allister Banks]

Hey There,

Please post the revision number inside the instadmg.bash script, and the relevant part of your debug .log from that run. I can’t say with absolute certainty, but my gut reaction is that is not to be messed with, unless you don’t want to resulting build to have screwy links that there are specific dependencies in place for. Sorry to be pessimistic without hard facts, but it is expected behavior that that is the most time consuming part of the process.

Allister

[Author]

Posts