Right now, we seem to have two different issues.
1. Some release builds of MediaPortal are triggering an error in the logs that a GIT build is installed.
2. Some MediaPortal files are not correctly updated by the installer.
What we do not know is whether the two issues are in any way related.
The way things work, the main installer (DeployTool) runs two different (NSIS) installers (the ones I mentioned in the post above).
The NSIS installers will always try to upgrade. The DeployTool installer is responsible for checking the installed version to see if an update is allowed.
Therefore, you would think that if it actually gets to trying to install, then everything would be okay.
Clearly we need to do more digging into this problem. Maybe some people have tried different versions of binary files to fix bugs. Maybe people are posting bugfix binaries in the forum.
Maybe for some reason a file has become locked. I don't think the NSIS installer checks that the files have been correctly replaced in every instance.
Prior to release, we were aware that if someone had installed a GIT build, the installer detected this but did not prevent installation. Since in our testing, the updates were correctly handled anyway, we felt that it was safe enough to release. In effect, this is a separate problem from issue 1, although the cause may well be related.
Basically, until we have more information, we are blundering around in the dark on this one.
Also, we have very little real information about how many people are updating to 1.2.2 without problems. If the problems are 1% then it may be something unusual on your systems. If the problems are 25%, then it is definitely a more serious issue.
Please help by reporting the problems, providing installer logs and information on which version you were updating from, and if you have installed any other fixes.
Thanks,
Mark
1. Some release builds of MediaPortal are triggering an error in the logs that a GIT build is installed.
2. Some MediaPortal files are not correctly updated by the installer.
What we do not know is whether the two issues are in any way related.
The way things work, the main installer (DeployTool) runs two different (NSIS) installers (the ones I mentioned in the post above).
The NSIS installers will always try to upgrade. The DeployTool installer is responsible for checking the installed version to see if an update is allowed.
Therefore, you would think that if it actually gets to trying to install, then everything would be okay.
Clearly we need to do more digging into this problem. Maybe some people have tried different versions of binary files to fix bugs. Maybe people are posting bugfix binaries in the forum.
Maybe for some reason a file has become locked. I don't think the NSIS installer checks that the files have been correctly replaced in every instance.
Prior to release, we were aware that if someone had installed a GIT build, the installer detected this but did not prevent installation. Since in our testing, the updates were correctly handled anyway, we felt that it was safe enough to release. In effect, this is a separate problem from issue 1, although the cause may well be related.
Basically, until we have more information, we are blundering around in the dark on this one.
Also, we have very little real information about how many people are updating to 1.2.2 without problems. If the problems are 1% then it may be something unusual on your systems. If the problems are 25%, then it is definitely a more serious issue.
Please help by reporting the problems, providing installer logs and information on which version you were updating from, and if you have installed any other fixes.
Thanks,
Mark