Installation using catalogs, rev 294 broken?

[Theilgaard]

I created a catalog, combining 10.6_vanilla lines with my own packages in InstaUp2DatePackages folder.

Checksumming and all is working perfectly, and then I run the InstaUp2Date with the -p option, like this:
[code]sudo ./instadmg/AddOns/InstaUp2Date.py MYmac -p[/code]

Result: An empty disk image, 3 MB in size. (And it was supposed to be 10.6 as well as 10.6.3 combo update, and a lot more).

The result is new for me (as rev 294 also is). with rev 293 (or maybe 292) from a few days ago, I got a more or less working disk image (At least the size of the image was what I expected), but my package that installs a /varDB.AppleSetupDone file didn’t work, so the startup assistant startet.

Then I have build an image, by calling instadmg.bash manually:
[code]./instadmg.bash -c ./InstallerFiles/CustomPKG_MYmac -n MYmac -m MYmac -r -z[/code]

Yes, using the same packages, but copied to a different folder, placed in numbered folders.

That used to work, including above mentioned package (as well as my create admin user package, that InstaUp2Date stumbled on). Now this image is broken, too. It’s like the base OS installation is missing.

Is rev 294 broken?

[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

[hkim823]

I maybe to blame. I was having problems working with InstaUp2Date and XCode 3.2.2, and the modifications made to the code basically made other functionality fubar (well hopefully not fubar).

I’ve decided not to use InstaUp2Date with XCode, but rather create my own custom XCode 3.2.2 pkg file myself using Composer. I’m sure we can go back to rev 293 where none of the mucking around was done on my behalf.

[Author]

Posts