On 7/13/14 9:52 AM, "OmPrakash Muppirala" wrote:
>On Sat, Jul 12, 2014 at 9:11 PM, Alex Harui wrote:
>
>>
>>
>> On 7/12/14 11:05 AM, "OmPrakash Muppirala" wrote:
>>
>> >On Sat, Jul 12, 2014 at 10:55 AM, Alex Harui wrote:
>> >
>> >> The Installer 3.1 uses MD5 checksums on many of its download
On Sat, Jul 12, 2014 at 9:11 PM, Alex Harui wrote:
>
>
> On 7/12/14 11:05 AM, "OmPrakash Muppirala" wrote:
>
> >On Sat, Jul 12, 2014 at 10:55 AM, Alex Harui wrote:
> >
> >> The Installer 3.1 uses MD5 checksums on many of its downloads to verify
> >> their accuracy. The checksums for Google Clo
On 7/12/14 11:05 AM, "OmPrakash Muppirala" wrote:
>On Sat, Jul 12, 2014 at 10:55 AM, Alex Harui wrote:
>
>> The Installer 3.1 uses MD5 checksums on many of its downloads to verify
>> their accuracy. The checksums for Google Closure Library, Adobe AIR SDK
>> and playerglobal.swc change every o
On Sat, Jul 12, 2014 at 10:55 AM, Alex Harui wrote:
> The Installer 3.1 uses MD5 checksums on many of its downloads to verify
> their accuracy. The checksums for Google Closure Library, Adobe AIR SDK
> and playerglobal.swc change every once in a while and that breaks installs
> until we find out
The Installer 3.1 uses MD5 checksums on many of its downloads to verify
their accuracy. The checksums for Google Closure Library, Adobe AIR SDK
and playerglobal.swc change every once in a while and that breaks installs
until we find out, download the file, compute the new checksum and update
the s