This weekend, Apple seems to have updated the OS X Mavericks Golden Master (GM) version to a new build. The new build is 13A603 while the original GM seed was 13A598. It’s not common for Apple to change the GM build for a Mac OS, but it is not without precedent. Apple has altered GM iOS seeds before they shipped to customers on a few occasions in the past. Users of the new build have not reported any noticeable user-facing alterations…
The new Mavericks build is not available via the Mac Developer Portal or via Software Update. Instead, it is appearing for users installing OS X Mavericks GM for the first time. Additionally, multiple readers have had success installing the new build by re-installing the Mavericks GM over the 13A598 version. It is currently unclear why Apple felt it necessary to create a new GM build, but it is likely built to squash some remaining bugs. Also unclear: which build Apple plans to actually ship and if this new silent 13A603 release is simply an error.
In early September, we reported that OS X Mavericks will ship in late October, and recent information has pinpointed a release later this week. The new Mac OS will arrive alongside new MacBook Pros, with the new Mac Pro to ship in the coming months. It’s unclear if the new GM of Mavericks will push back the launches as the new build would likely require Apple to re-install Mavericks on the new Macs.
9to5Mac Reader Tom was curious to know what the differences were between the two GM builds so he ran a diff -rq against the installation sources of both builds. Well, here’s what’s changed:
SystemMigration.framework:
BaseSystemBinaries/System/Library/PrivateFrameworks/SystemMigration.framework
Essentials/System/Library/PrivateFrameworks/SystemMigration.framework
Mail + supporting stuff (build # went 1812 -> 1816):
Essentials/Applications/Mail.app
Essentials/System/Library/InternetAccounts/Mail.iaplugin
Essentials/System/Library/InternetAccounts/SetupPlugins/MailAccountSetup.iaplugin
Essentials/System/Library/PrivateFrameworks/EmailAddressing.framework
Essentials/System/Library/PrivateFrameworks/IMAP.framework
Essentials/System/Library/PrivateFrameworks/Mail.framework
Essentials/System/Library/PrivateFrameworks/MailCore.framework
Essentials/System/Library/PrivateFrameworks/MailService.framework
Essentials/System/Library/PrivateFrameworks/MailUI.framework
Essentials/System/Library/QuickLook/Mail.qlgenerator
Essentials/System/Library/Spotlight/Mail.mdimporter
This file went down in size by ~50% (maybe debug symbols were compiled in originally):
BSD/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/scipy/linalg/calc_lwork.so
A single element in this XML file changed:
Essentials/System/Library/Frameworks/OpenCL.framework/Versions/A/Resources/BridgeSupport/OpenCL.bridgesupport
As you can see, it’s mostly Mail.app-related. Nothing to do with SMB shares as some guy out there is reporting.
FTC: We use income earning auto affiliate links. More.
If this new build is not available via the dev portal, how is it that “multiple readers” have reported that they”ve been able to install the new build on top of the old build – how did they get their hands on the new build?
by downloading it again with app store ?
i agree with you
Only people downloading it from now on are getting the new build. It seems like the new build and the older build are identifying themselves as the same version.
I’ve tried reinstalled the 13A598 GM, yet saw the 13A603. I don’t think the 13A603 thing is true.
I just reinstalled it as well and it came back as 598 as well. It must have been pulled or it was a pre-mature beta build for like 10.9.1 or something. We may find out eventually.
If this is an error, when reinstalled without internet connection it should indicate build 13A603 right?
and what happens if it is reinstalled a third time?
Reblogged this on William's iBlog and commented:
Strange indeed.
Speculation = mental masturbation
.
Updated to this new GM. I had an absolutely huge bug before which I reported to Apple. I couldn’t connect to an SMB share and Https share at the same time at work. They were both on the same Windows server. This bug has been present since the very first beta. The latest GM has fixed this. Crisis averted :)
Thanks for the telling this, I also connects to Windows server via SMB, I’ll be updating let them roll OSX Maverick today