Closed GoogleCodeExporter closed 9 years ago
I also tried comparing the md5 of xbmc-9.11-x86.dmg with comparemd5.sh (found in
/System/Library/CoreServices/Finder.app/Contents/PlugIns/XBMCLauncher.frapplianc
e/Contents/Resources)
and it checks fine.
Original comment by lgaryfal...@gmail.com
on 20 May 2010 at 8:46
Mind posting console.log?
About the still showing Launcher download:
It's just a list of downloads. It's never checked if you have already installed
one of the items in that list. But you
can check the Launcher version in Launcher's 'About' menu.
Original comment by stephan.diederich@gmail.com
on 20 May 2010 at 9:09
It's the 3.2.4 launcher apparently. I would gladly post the console.log if I
knew
where to find it :(
Original comment by lgaryfal...@gmail.com
on 20 May 2010 at 9:16
/Library/Logs/Console/501/console.log
Original comment by stephan.diederich@gmail.com
on 20 May 2010 at 9:18
here you go. console.log
Original comment by lgaryfal...@gmail.com
on 20 May 2010 at 9:21
Attachments:
Thanks! Launcher thinks the md5 is wrong (it checks the return value of
compareMD5.sh.
You could check what happens inside the compareMD5.sh script when it's started
from Launcher. For that, just
uncomment line #19:
#LOGFILE=/Users/frontrow/compareMD5.log
And /Users/frontrow/compareMD5.log should hold the log after a failed download.
Do you use a proxy or something like that?
Original comment by stephan.diederich@gmail.com
on 20 May 2010 at 9:38
The problem is that the md5 generated (or hardcoded) in launcher (as seen in
console.log) is the same as the one being generated by hashcalc on my pc for
the same
file...
If I changed md5compare.sh to always return true?
Original comment by lgaryfal...@gmail.com
on 20 May 2010 at 9:50
Launcher fetches the list of downloads with their corresponding md5 from
http://code.google.com/p/atv-xbmc-launcher/source/browse/tags/ul-info/update_url
s.plist
After the download Launcher checks if the downloaded file has the same md5.
This check was needed, as
we've seen too many network problems on users ATVs.
If you download the update script (link can be found in the plist linked above)
and XBMC-xcy.dmg manually,
you can just execute the script with the dmg as parameter. That will install
xbmc and prepare some other
things.
Though I'm still curious why the md5 check fails...
You said you checked the downloaded file with compareMD5.sh and it succeeded.
Only thing I can imagine
which fails is the download in Launcher (which uses Cocoa API). That's why I
asked for proxy settings..
Original comment by stephan.diederich@gmail.com
on 20 May 2010 at 9:58
no proxy at all in the network, don't know if my ISP has some transparent proxy
but
if it has, it hasn't caused any problems in the past even with the previous
update.
where do I have to store these files, and how will I run them? from ssh?
btw thanks for all the help :)
Original comment by lgaryfal...@gmail.com
on 21 May 2010 at 8:26
ssh into your ATV. Download the dmg (e.g. via wget), download the update
script. Run update script with dmg as
parameter.
After the download via wget, you might want to make sure that the md5 of the
download is correct, but I guess
you already did that when you checked the output of compareMD5.sh.
If you can make it, it'd be great to see the output of the compareMD5.sh script
when run from Launcher
(uncomment the logging as described in comment #6).
Original comment by stephan.diederich@gmail.com
on 21 May 2010 at 9:10
The install went great manually (I had already downloaded the dmg and just
wgeted the
update script and ran it.
the comparemd5.log is:
-bash-2.05b$ more compareMD5.log
Checking MD5 of /Users/frontrow/xbmc-9.11-x86.dmg against 8e2da36818aacd578951af
38c11cf93c
File MD5: 8e2da36818aacd578951af38c11cf93c
Test MD5:8e2da36818aacd578951af38c11cf93c
MD5 matches!
if that's any help. Thanks for the help :)
Original comment by lgaryfal...@gmail.com
on 27 May 2010 at 11:59
Looks like you did manually run the script.
The output when it was run from Launcher would be interesting...
Thanks, and glad it's working for you now ;)
Original comment by stephan.diederich@gmail.com
on 27 May 2010 at 12:39
Original comment by stephan.diederich@gmail.com
on 15 Jun 2010 at 9:16
Original issue reported on code.google.com by
lgaryfal...@gmail.com
on 20 May 2010 at 8:32