Separate names with a comma.
Discussion in 'OS X Yosemite (10.10)' started by Voenix Rising, Oct 7, 2014.
Go get it!
...a fews secs remaining...restart
Are you seeing this in the App Store as an update?
Nothing showing for me, or is it just dev center?
Yup, App Store.
I'm too lazy to go looking for any differences.
app store now showing beta 5 in updates
its running well
Ah nuts! I think I un-ticked the box in the App Store Preferences which said something like "Allow Pre-Release Updates" the problem is the option is not there anymore to re-enable.
Anyway to fix this with out a re-install?
Main discussion of GM candidate 2 / PB 5 here: http://forums.macrumors.com/showthread.php?t=1797714
Yeah, this. I really need an answer to this
anybody got a direct link? not showing up in my software update
What is not fixed...for me...
I know that not everyone is having an issue with safari extensions, but to those that are. This did not fix it. Safari Extensions still get lost when closing Safari.
damn, i did that too. figure it out yet?
oh, it is actually downloading the GM 2 in the background regardless of clicking the do not download pre-seeds
but its actually downloading the whole GM at 5.17GB plus iMovie & iPhoto
Huh...App Store purchases still only shows me Beta 4.
it did for me too until i clicked check for unfinished downloads in the app store. then it downloaded and i had to go through the process of installing GM 1 and then everything was fine.
To clarify, I am not on the Developer Preview release train. I am on the Public Beta train. So instead of GMC1 I was given PB4. And instead of GMC2, I should be getting PB5. PB5 is being offered as an update, but so far the App Store is not offering PB5 to me as a full installer download (PB4 is still the latest full installer that shows up for download under Purchases).
A similar thing happened with PB4 as well when it was released...it was several hours after the delta update was posted that the full installer showed up on the App Store. I expect the PB5 full installer will probably be available later this evening, or tomorrow at the latest.
GM2 direct link is in apple's developer forums.
The PB5 direct link can't be published anywhere however because apple still haven't made a forum for public beta testers.
Exploring this theme further (without giving actual links here) I have discovered that there are actually several things happening here with developers without xcode beta with slightly different download sizes - or those with xcode beta also with slightly different download sizes - but in this case much bigger download sizes than those reported by public beta testers - noting that public beta testers don't have access to the xcode beta.
And for public beta testers, they too are reporting slightly different download sizes.
The slightly different download sizes thing I'm talking about has to do with the fact that there is not just a delta, but a "patch" which is sort of like a delta, but with irrelevant stuff (and here I mean irrelevant to your particular system) removed.
So here is what is really going on here:
Developers without xcode beta get either
OSXUpd10.10pkg (68.6 MB) or
OSXUpd10.10Patch.pkg (56.9 MB)
FirmwareUpdate.pkg (46.7 MB)
and if they have xcode beta:
DevSDK_OSX1010.pkg (35 MB)
CLTools_Executables.pkg (142.8 MB)
whereas public beta testers only get either:
OSXUpd10.10.pkg (69.1MB) or
OSXUpd10.10Patch.pkg (56.9 MB)
FirwareUpdate.pkg (46.7 MB)
These are not the same as the ones developers get though (but very similar).
Nobody has said anything about this before but if you replace the .pkg extension in the direct links with .pkm and open it with textedit, apple use the word delta or combo for public versions of updates but here with these developer previews and golden masters, etc., in the deltas they are using a new word I have not seen before called "convergence" build.
So for example if instead of downloading the GM2 delta file called OSXUpd10.10.pkg you download OSXUpd10.10.pkm instead and open it with textedit, you see at the top:
<pkg-info format-version="2" relocatable="true" deleteObsoleteLanguages="true" overwrite-permissions="true" identifier="com.apple.update.convergence.14A386a" useHFSPlusCompression="true" auth="root" postinstall-action="restart" version="188.8.131.52.1.1412663545">
So what exactly is a convergence build?
Contast this for the public release of mavericks 10.9.5 delta and combos pkm files we see respectively
<pkg-info format-version="2" relocatable="true" deleteObsoleteLanguages="true" overwrite-permissions="true" identifier="com.apple.pkg.update.os.10.9.5.13F34.delta" useHFSPlusCompression="true" auth="root" postinstall-action="restart" content-type="critical-update" version="184.108.40.206.1.1306847324">
<pkg-info format-version="2" relocatable="true" deleteObsoleteLanguages="true" overwrite-permissions="true" identifier="com.apple.pkg.update.os.10.9.5.13F34.combo" useHFSPlusCompression="true" auth="root" postinstall-action="restart" content-type="critical-update" version="220.127.116.11.1.1306847324">
In particular, I'm seeing a lot of people simply reporting 104MB - both developers AND public beta testers.
So what is that?
I would say it is OSXUpd10.10Patch.pkg (56.9 MB) and FirmwareUpdate.pkg (46.7 MB).
Add those together and round off to the nearest integer and you get 104.
I wonder how many of them realise they are getting a firmware update as well? Probably not many. Apple did not warn about this. Even developers!
I'm also experiencing this of sorts. Safari extension are wonky in that if I download ClickToPlugin or 1Password and if I close out of Safari after 10 minutes and Quit it too then on next launch the extensions are set up as if they were just installed.
My way around this is to launch a new window after initial install of extensions and then after that set them up with their settings, like those for ClickToPlugin.
Bugs the hell out of me.
That would be because GMC2 is not the same as PB5, but are very similar. I believe that those on the Developer Preview release train are getting updates fed to them via the "10.10seed" sucatalog whole those on the Public Beta release train are getting updates via the "10.10beta" sucatalog. Each catalog points to a different set of PKG files for the updates: the 10.10seed catalog points to PKGs that update to the latest DP#/GMC# build while the 10.10beta catalog points to PKGs that update to the latest PB# build.
I first discovered this before I had installed the public beta on my machine, and it really turned me off. Updating SMC and EFI firmwares is usually a one-way ticket (although if you have access to a copy of the older version(s) and know what you are doing, it is sometimes possible to downgrade), and there was no way in heck I was going to allow a beta OS release to update my system firmware(s) with what amounts to beta firmware, especially without even asking OR warning me.
On account of this, when I installed the first beta, I created a USB install drive, purged /System/Installation/Packages/EFIPayloads and /System/Installation/Packages/SMCPayloads from it, and then installed from that. This ensured there wouldn't be any firmware updates for the OS X installer to flash during installation. For every PB update since then, I have undergone the same procedure: prepared USB install media, removed EFIPayloads and SMCPayloads from it, and then installed the latest PB on top of my existing Yosemite partition, rather than allow the deltas to be installed via the App Store/Software Update.
For PB5, since the full installation app STILL is not available for download via the App Store, I did a "softwareupdate --download" from the terminal, deleted FirmwareUpdate.pkg from /Library/Updates (just in case), and then ran the OSXUpd10.10Patch.pkg manually. Worked like a charm.
To my knowledge, no past OS X release -- either beta OR final -- has ever bundled firmware updates with it and installed them onto a machine without warning. Firmware updates have always been offered and installed separately from the OS. I am not sure how I feel about the fact that Yosemite apparently "needs" firmware updates to be installed on certain models, and will go ahead and irreversibly install them for you without warning. I *do* know, though, how I feel about a *beta* version of an OS doing this: bad, bad, bad. Stay classy, Apple...
There have been other such firmware updates bundled with the deltas for recent builds - all without warning. So far they appeared for DP7, DP8, GM1, GM2, PB3, PB4 and PB5
I too have been avoiding most of these firmware updates, maybe not as cleverly as you did, but by just installing OSXUpd10.10.pkg files and not the FirmwareUpdate.pkg ones.
I think this strategy has made me largely immune from several of the disasters like kernel panics, etc that others have been reporting.
You don't have the luxury to pick and choose which parts of the installation you want if you just use the mac app store to install them for you. That's one reason I've been mostly just using the direct links instead. The other reason is to back all the installers up in case I need to reinstall, and also to install onto several computers without having to redownload each time.
On the other hand, if you have the direct links for the deltas and actually want the firmware updates, you can just replace the filename OSXUpd10.10.pkg with FirmwareUpdate.pkg in the same directory and it will then download the firmware update.
If Apple includes a firmware update, it must work hand-in-hand with some advanced features of Yosemite. Aren't you afraid that your blunt cut job of the firmware files could jeopardize the stability of Yosemite?
I chose to have much more control over most of the installations than apple would want me to have.
But today I just let it go (unusual for me) all through the mac app store - replete with firmware updates, because we are now getting very close to public release.
I haven't been missing out on any functionality. And I haven't had any kernel panics either. I might not have been so lucky if I just let all the firmware updates to install.
And as I said before, most developers and public beta testers were probably not even aware that the firmware updates were occurring when they used the mac app store to update. Then afterwords are wondering why they were getting kernel panics.
Anyway, today I didn't actually use the direct links for the installations, but I still used them to get information, like the post I made above with all the file sizes for each part. They don't give you that much information in the mac app store, or even on the mac dev center.