AFP548 - Topic: 10.5.3 Combo update shows as 10.5.2

This topic has 10 replies, 9 voices, and was last updated 16 years, 10 months ago by thegooch49.

Viewing 10 posts - 1 through 10 (of 10 total)

Author

Posts
May 29, 2008 at 2:22 pm #372916

mdspidle
Participant

I made a new image over night substituting the 10.5.2 Combo update with the newly downloaded 10.5.3.

Upon restoring the new image this morning my 2 test machines report the OS as 10.5.2, and then running Software update they think they need to run the 10.5.3 delta update. Can anyone else confirm this? All my InstaDMG logs say that the 10.5.3 updater installed successfully.

May 29, 2008 at 6:53 pm #372922

thegooch49
Participant

Confirmed, I have the exact same problem. When I then run SW update, it says I need 10.5.3 still. When I try to run it, it errors about ‘not having rights to install’. I’m glad I came across this, I thought I was going mad. My baseOS is 10.5.1 (system restore disk on a MacPro). I had no other AppleUpdates in the directory. Just the 10.5.3 combo updater (NOT the delta).

Very strange, it’s not just the GUI reporting this. system_profiler and sw_vers both report 10.5.2. Crazy.

May 29, 2008 at 7:02 pm #372923

Patrick Fergus
Participant

Guessing–did you remove all the other Apple/OS updates from your AppleUpdates folder? If you “substitut[ed] the 10.5.2 Combo update with the newly downloaded 10.5.3”, did InstaDMG attempt to install all the updates that may now be rolled into 10.5.3?

– Patrick

May 29, 2008 at 7:52 pm #372927

Anthony Reimer
Participant

I have a very basic (for now) InstaDMG-generated image that was using 10.5.2 combo to update 10.5.0 (source: OS Disc) until yesterday. I subbed in the 10.5.3 combo updater, took out Security Update 2008-002 (which, by Apple’s standard operating procedure, should be rolled into this update) and generated a new image. Worked perfectly; shows as 10.5.3 and no new bugs induced. My test machine is a Mac Pro (early 2008).

Anthony

May 29, 2008 at 9:04 pm #372933

thisgarryhas2rs
Participant

Transition has been easy. I took out all the Apple updates, and ran with with all my custom pkgs in. Then I added the updates that it asked for after. It shows 10.5.3. Everything looks good.

I was using a Macbook Pro Multi-touch Installer CD image.

May 30, 2008 at 1:15 pm #372939

tncook
Participant

The transition went fine, of course I only started using InstaDMG the day before 10.5.3 came out so I spent a day figureing out what updates were needed and then was able/needed/had to start over.

May 30, 2008 at 3:42 pm #372940

dano
Participant

I added the newer Software Updates to the build train without removing any older updates as the previous poster did and had no difficulties. It shouldn’t be necessary to remove the the Mac OS X combo updater or other older updates (barring any problems with specific updates). After all, this replicates the typical update path of the average user.

May 30, 2008 at 4:58 pm #372941

eholtam
Participant

Its just adding extra time with all the unnecessary updates. If a user didn’t update since 10.5 the 10.5.3 combo update would be the same as their upgrade path as well.

May 30, 2008 at 6:18 pm #372942

dano
Participant

In the overall scheme of things the increased intall time for Apple Updates (including the 10.5.2 and 10.5.2.3 Combo Updaters together) required is minor. I’ve gone from about 20 minutes to about 25 minutes to install Apple updates. Additional time to the overall build is probably on the order of 6-10 minutes for a build that is approaching 3 hours (CS3 Design Premium and Office 2008 included) to complete. Not to mention that I can start a script and come back when it’s done for a ready to use disk image.

Having said that, I think there is value in changing the updates that are placed in the AppleUpdates folder as available updates are added and others are superseded. It really isn’t necessary but doing so would simplify the Apple Updates portion of the process and that’s never a bad thing. FYI: I will being doing just that in late July (I work at an educational institution) when I am ready to roll out Production ready images. But as I’m still fine tuning my build process I’m just adding any new Apple updates to my previous ones as they appear and it’s been working just fine for me that way.

May 30, 2008 at 8:31 pm #372943

thegooch49
Participant

I just re-built my image with a 10.5.0 baseOS and the 10.5.3 combo update. Everything came out fine. When I had an issue (Imaging with 10.5.3 combe showing as 10.5.2), I was using a 10.5.1 System Restore disk, with the same 10.5.3 combo update. I’m going to re-build this again, to see if I can recreate the problem.

But, all was fine when I used the 10.5.0 retail disk.
Author

Posts