Latest Win 7 package triggers Sophos malware warning about Uninstall.exe

[Martyn Gigg]

Get any master, clean or incremental, package from jenkins and try and install it. As the installation finishes Sophos pops up warning that MantidInstall\Uninstall.exe contains malware.

This must be a false positive but we need to track down what is causing it.

[Martyn Gigg]

Rename VISION IDF to avoid triggering Sophos malware warning.

When building a Windows package Sophos claims that the NSIS-generated Uninstall.exe contains malware. This must be a false positive and it has been submitted to Sophos for testing.

We really need to be able produce working kits for the release and the rename seems to avoid the problem. Refs #8323

Changeset: 9fb929fdfc7c786abba1d45fb9f0c3ea39b4e59c

[Martyn Gigg]

Branch: ​bugfix/8323_sophos_warning

Tester: For some reason this does not show up with the develop package but does with all of the current packages. A proper test would be to merge to master, build and then generate the package locally. This will require a complete build of Mantid, including VATES.

I think a brief check of the rename should suffice though as nothing will actually be relying on the filename.

[Martyn Gigg]

Note: I have also submitted the offending file to Sophos for inspection.

[Nick Draper]

Alternate testing approach.

Merge, let the build servers build and test the resulting package.

We would always want to test the final package anyway.

[Nick Draper]

Merge remote-tracking branch 'origin/bugfix/8323_sophos_warning'

Full changeset: ​6c3a3941e9ae44dfbbfebc33467df605ad8d8625

[Stuart Campbell]

This ticket has been transferred to github issue ​9168