CLOSED WORKSFORME Bug 35854
"Nightly builds of WebKit are not supported on Mac OS X 10.5 at this time" message when attempting to install latest nightly 
https://bugs.webkit.org/show_bug.cgi?id=35854
Summary "Nightly builds of WebKit are not supported on Mac OS X 10.5 at this time" me...
sideshowbarker
Reported 2010-03-08 01:12:03 PST
Auto-updated to r55610 and relaunched my WebKit and I got the message "Nightly builds of WebKit are not supported on Mac OS X 10.5 at this time". Tried relaunching several times, but always got same message. Downloading a fresh copy fixed the problem. Zip of borked build is at http://people.w3.org/mike/webkit/WebKit.BORKED.app.zip Note that when I zipped it up, I got the following message: zip warning: name not matched: WebKit.BORKED.app/Contents/Frameworks/10.6/WebKit.framework/Frameworks
Attachments
Add attachment proposed patch, testcase, etc.
Mark Rowe (bdash)
Comment 1 2010-03-08 01:34:07 PST
Is there anything in your system console from either Safari or WebKit from around the time of the update? You can see this by running /Application/Utilities/Console.app and selecting All Messages. Please attach any output that appears to be relevant. Comparing against a known good build of r55610 it is obvious that a number of directories are missing from the bad bundle: Only in /Volumes/WebKit/WebKit.app/Contents/Frameworks: 10.4 Only in /Volumes/WebKit/WebKit.app/Contents/Frameworks: 10.5 Only in /Volumes/WebKit/WebKit.app/Contents/Frameworks/10.6: JavaScriptCore.framework Only in /Volumes/WebKit/WebKit.app/Contents/Frameworks/10.6: JavaScriptGlue.framework Only in /Volumes/WebKit/WebKit.app/Contents/Frameworks/10.6: Sparkle.framework Only in /Volumes/WebKit/WebKit.app/Contents/Frameworks/10.6/WebCore.framework: PrivateHeaders Only in /Volumes/WebKit/WebKit.app/Contents/Frameworks/10.6/WebCore.framework: Resources Binary files /Volumes/WebKit/WebKit.app/Contents/Frameworks/10.6/WebCore.framework/WebCore and ./Contents/Frameworks/10.6/WebCore.framework/WebCore differ Only in /Volumes/WebKit/WebKit.app/Contents/Frameworks/10.6/WebKit.framework: Frameworks The difference between the two WebCore binaries is also interesting. They’re identical sizes. The bad one has valid data for the first 32MB, but the remaining 2.5MB or so is zero-filled.
sideshowbarker
Comment 2 2010-03-08 02:01:13 PST
(In reply to comment #1) > Is there anything in your system console from either Safari or WebKit from > around the time of the update? Nope -- I just checked it and I see nothing at all in there from either Safari or Webkit anywhere around the time I auto-updated. > Comparing against a known good build of r55610 it is obvious that a number of > directories are missing from the bad bundle: > > Only in /Volumes/WebKit/WebKit.app/Contents/Frameworks: 10.4 > Only in /Volumes/WebKit/WebKit.app/Contents/Frameworks: 10.5 > Only in /Volumes/WebKit/WebKit.app/Contents/Frameworks/10.6: > ...etc. > The difference between the two WebCore binaries is also interesting. They’re > identical sizes. The bad one has valid data for the first 32MB, but the > remaining 2.5MB or so is zero-filled. Could this be due to me having lost my network connection around the time it was attempting to update and relaunch WebKit? Anyway, this does just seem like some kind of fluke that it's not likely is going to be reproducible, so I'm fine with this just being closed out if that's what you end up doing.
Mark Rowe (bdash)
Comment 3 2010-03-09 01:05:01 PST
I tested a few different uncommon error scenarios to verify that the updater bailed out with an error rather than resulting in a corrupt build: * Applying an incomplete patch update * Applying a patch update with insufficient disk space to construct the full build * Applying a patch to a source build that had been modified. These all behaved as expected. > Nope -- I just checked it and I see nothing at all in there from either Safari or Webkit anywhere around the time I auto-updated. That’s really surprising. The patch-based updater in the nightly builds logs its progress to stderr, which is routed to the system console. A typical update will print messages like the following to the console: Verifying source... Copying files... Patching... Verifying destination... Done! If there’s really no output here then I’m not entirely sure how to investigate this further.
sideshowbarker
Comment 4 2010-03-09 03:00:29 PST
(In reply to comment #3) > > Nope -- I just checked it and I see nothing at all in there from either Safari > or Webkit anywhere around the time I auto-updated. > > That’s really surprising. The patch-based updater in the nightly builds logs > its progress to stderr, which is routed to the system console. A typical > update will print messages like the following to the console: > > Verifying source... > Copying files... > Patching... > Verifying destination... > Done! I guess I could have been mistaken about what time it was when I updated. But going in to look at All Messages now, I still don't see any messages of that kind (even after using the search box to try to filter for them). I suppose that could be because the console messages aren't archived any longer than a day or two? > If there’s really no output here then I’m not entirely sure how to investigate > this further. Understood -- if/when I ever manage to reproduce it, I'll stop next time and check the console messages right away, and get a copy.
Note You need to log in before you can comment on or make changes to this bug.