I just discovered after some testing that the updater doesn't download the update (despite the different MD5 signature in the update file) if the file with same name and same size is found in local download location.
This means that if updater tries update the newer version of a package that would happen to be equal size that the earlier update, it skips the download and then promptly fails at the update (as it is running with the earlier package).
Now there are perfectly valid cases where for example some installation parameters are changed, that will not change the resulting file size at all. Even when all the other conditions hold true (version, productcode and md5 hash are updated accordingly) the update fails due to download skipping based on filename and file size.
I tested the behaviour with 6.4.1. Did I miss something or is this something that will get revisited perhaps?
Br,
Kalle
FOLLOW US
Get the latest news in Application Packaging