keeleysam / instadmg

Automatically exported from code.google.com/p/instadmg
0 stars 0 forks source link

415: InstaUp2Date download attempt for Java For MacOS X 10.5 Update 5 results in 404 error #87

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Check out revision 415 with SVN.
2. Run InstaUp2Date with the 10.5_vanilla.catalog.

What is the expected output? What do you see instead?

The InstaUp2Date process should complete with out errors/exceptions.

What version of InstaDMG are you running? What revision number (this should
be the second line of your package log)?

Updated to revision 415 this morning. This includes some InstaUp2Date catalog 
updates for recent Apple releases.

What OS are you running on (booted from)?

Mac OS X 10.6.3.

What OS are you installing?

Mac OS X 10.5.8.

Please provide any additional information below.

The 10.5_vanilla.catalog file contains “Java For MacOS X 10.5 Update 5“ 
which appears to no longer be available -- at least at the URL in the catalog 
file. “Java For MacOS X 10.5 Update 9” which supersedes it does download 
through InstaUp2Date rev 415.

Original issue reported on code.google.com by jaha...@gmail.com on 16 Mar 2011 at 2:40

GoogleCodeExporter commented 9 years ago
I checked the 10.6_vanilla.catalog and did NOT see that it contained a 
reference to both an old and new version of Java For MacOS X 10.6. This issue 
appears to only affect the Leopard catalog file.

Original comment by jaha...@gmail.com on 16 Mar 2011 at 2:56

GoogleCodeExporter commented 9 years ago
Hey there,
I looked for you on twitter, you've been getting work done lately or something?
You're right about the 404 for update 5, sorry about that!  Unfortunately, that 
looks like its been... pulled? I can't find it, perhaps we need to file a bug, 
but nothing I can do at this point unless my google-fu is just weak.

You cannot, afaik, build 10.5.8 on 10.6.3, so please revise your build method 
accordingly.
As I understand it, Java Update 9 does not replace update 5, it builds upon it. 
 It supersedes java updates 6,7, and 8.  At least that's what I found in my 
testing.  Thanks, may I keep this at least downgraded to low priority while we 
wait for apple's response? 

Original comment by allister...@gtempaccount.com on 16 Mar 2011 at 3:33

GoogleCodeExporter commented 9 years ago
Actually, @bruienne found a working CDN link - thanks, wacky bittorrent 
scrapers!
 http://supportdownload.apple.com/download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/Mac_OS_X/downloads/061-6808.20090903.jva41/JavaForMacOSX10.5Update5.dmg
I'm still making sure the sha1 matches up before checking in fix.

Original comment by allister...@gtempaccount.com on 16 Mar 2011 at 4:02

GoogleCodeExporter commented 9 years ago
I’m taking a Twitterbreak, but e-mail still works.

Once I got a working 10.5.8 image that would restore (see my post in the AFP548 
forum), I found that Update 5 would still be visible via Software Update. My 
memory is dim as to what was special about that update that would make it 
important to continue offering via SU. Maybe I’ll check the release notes. Hm.

Original comment by jaha...@gmail.com on 17 Mar 2011 at 1:57

GoogleCodeExporter commented 9 years ago
The URL from @bruienne worked for me when I added it and the associated 
checksum to the 10.5_vanilla.catalog. I ran the build process for 10.5.8 and it 
produced a bootable image that had no further updates available via Software 
Update. The image was restored to a Power Mac G5 DP 2.7.

If you're editing the catalog further, I would name all the Java Updates "Mac 
OS X" instead of "MacOS X." (Notice spacing, which is a small difference.)

Original comment by jaha...@gmail.com on 17 Mar 2011 at 7:42

GoogleCodeExporter commented 9 years ago
I'm still somewhat unsettled by this, it seems Apple rev'd it without making a 
QA'd package publicly available, which we should file a bug against. I'll 
update this ticket once mine is filed.  The internal numbering for this update 
seems to have gone from 061-6808 to 6809, and since that's what is available on 
the CDN, I've decided to consider that more important to replace the 404'd 
entry.  I usually don't like swscan.apple cdn url's, but I like *ahem* 
'foreign' url's even less, so I'll leave in the older version in, commented out.
Going live shortly.

Original comment by allister...@gtempaccount.com on 29 Mar 2011 at 3:08

GoogleCodeExporter commented 9 years ago
fixed as part of r417 - thanks jaharmi and 

Original comment by allister...@gtempaccount.com on 20 May 2011 at 2:14