Bugzilla – Bug 8518
unable to install higher major revision when minor revision is lower
Last modified: 2009-09-08 09:21:48 UTC
I am unable to "downgrade" Windows versions of SC when a higher build number already exists on the system, even if the Version number is different. Steps to reproduce: Install 7.1 - 20942 to a Windows XP/Vista system Run SN to make sure it works With the server either running OR off, install 7.0.1 (release) OR Install 7.2 - 20932 Notice that SC 7.1 - 20942 is still present on the system. I would need to uninstall SC first in order to install a previous version. ---- NOTE: Add/Remove programs (Windows Uninstall) shows the "proper" version as having been installed and available for removal, even though the incorrect version is installed ----- NOTE: This is also a problem with 7.0.1 > 7.0 (release versions)
Think this is a bug for Michael.
I was tempted to set the severity to minor. Isn't this related to what I've fixed today: if you try to install another SC while the scanner is still running, it can't fully uninstall. Obviously this can't be fixed in the older versions. So downgrading will always be a bit of a problem: we can't fix the older version. I'd assume that a reboot in between would resolve this.
Michael: no this is not related to the scanner, as NO files are over written. Not just the scanner, but any of the files never get over written. This is the case even if I stop SC
> > I'd assume that a reboot in between would resolve this. > NO, rebooting between installs does not result in expected behavior.
Well, maybe the official way to downgrade should be getting rid of your install first? I don't see why we should bother about this, really. Installers usually don't overwrite newer versions of a file, as they might have been updated by something else. Downgrading might even be impossible, because incompatible changes happened. Really, this is no blocker - does 7.1 require to be downgraded to be released? If this is needed, then there's something wrong with our release which needs be fixed. I'd like to close this as "wontfix".
Michael: you make very good points, I think the major issue here is that I could not install 7.2 over 7.1 when the minor version number was higher. Install 7.1 - 20942 > Install 7.2 - 20932 = FAIL This is a bigger issue then attempting to install 7.0.1 > 7.1. In any case, why not just have any version of SC auto-uninstall a previous version before installing a new version? Many other software applications do this already, including the MAC version.
Wow, good catch! This got me puzzled, as on installing a different version the revision number would change, but not the version number. It turned out that while the binary indeed wasn't replaced, all the perl modules and other files (skin, revision.txt etc.) were. This issue very likely showed up due to change 20597 (in response to bug 8166), adding version information to the binaries. change 21031 - ignore the version information during install. Please note that this will not help installing 7.0.x over 7.1, or an earlier 7.1 over todays+ builds. As mentioned earlier: we can't fix the previous installers.
Verified error still happens when installing 7.2-21119 over 7.1-21126 Squeezecenter.exe / scanner.exe not overwritten, even if the server is stopped. Files that have version information show that 21126 still installed.
change 21164 - don't use comparetimestamp flag in Windows installer - even the InnoSetup author does not recommend it
Change 21031 I did made the installer ignore version information in the file. But it would still compare timestamps of the files. Thus 7.2-21119 < 7.1-21126, as the latter has been built after the former. Change 21164 removes the timestamp check too. 7.1-21175 on top of 7.2-21168: ok, version checking is disabled. 7.2-21168 over 7.1-21175: ok, revision checking & timestamp check disabled we'll have to test the case where version and revision are smaller, too. Please re-open if this still fails. Thanks!
Verified fixed in 7.1-21576 > 7.2-21568
This bug has now been fixed in the 7.1 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
This bug has been fixed in the 7.3.0 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Reduce number of active targets for SC