This night (as of about midnight CEST) the up2date package was changed. Those installations that had already downloaded the previous package did receive a notification for the new package. I don't know where the 3rd notification came from, but I look into the up2date log might be helpful to find the cause.
As to the up2date package: the content of the package was not changed. We added one installation instruction in order to bypass a problem showing up when updating with SSL VPN enabled. The first package works fine for those who didn't have it enabled; it would fail to install on machines that had it enabled, and those would need the second package. So if you're on 7.360 you're OK either way; if not, the up2date mechanism will already have reloaded the new package. If you're unsure, you can check; the correct MD5sum and size of the second package are:
MD5sum: 0f08e7bee6afdb40449cd337e2aaa652
Size : 92787967 bytes
I got notifications about every 30 minutes starting around noon yesterday (had around 7 of them before I just hit install)... I just got tired of them, so I turned those notifications off.
CTO, Convergent Information Security Solutions, LLC
Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
That is another bug that was fixed yesterday. The downloader did not correctly check if the package has already been verified and unpacked, therefore triggering a new package unpack and a new notification. Unfortunately, there's no way around that at the moment except for disabling the notification or installing the up2date.
That is another bug that was fixed yesterday. The downloader did not correctly check if the package has already been verified and unpacked, therefore triggering a new package unpack and a new notification. Unfortunately, there's no way around that at the moment except for disabling the notification or installing the up2date.
