Apache OpenOffice (AOO) Bugzilla – Issue 55114
incorrect detection of "newer version"; install fails
Last modified: 2005-10-11 13:46:42 UTC
When trying to install "OOo_2.0.0rc1_050923_Win32Intel_install.exe" it fails with the error message: "A newer version of OpenOffice.org 2.0 was found. To install an older version, the newer version needs to be removed." Then it will not install. Currently I have installed 1.9.130.
I must confirm this behaviour with the native german version OOo_2.0.0rc1_050923_Win32Intel_install_de.exe on Win98SE. My actual version is m125, but on the germanophone dev-list the bug was reported comparing to m113! For a standard milestone this is just au bug, but IMHO for a RC it must be counted as SHOWSTOPPER. We shouldn't confuse all the people trying to help us finding bugs with such messages, just because they had installed another milestone before. Many people will not follow the error message because they don't understand, why all the milestones shall be newer than the RC. (Perhaps the installer compares only the last entry - ".0" to ".125" ?) Please fix it as soon as possible. By the way - up to now I heard of Windows problems only Best regards Bernhard
This has been confirmed by various users on german-lang mailing list and replicated here as well. → confirming
This is caused by an incorrect ProductVersion "1.9130.8955" of OpenOffice.org 1.9.x -Versions (Major.Minor.Build). For OOo 2.0 we changed to the correct setting 2.0.8958. Unfortunately the Minor must not be greater the 255. Because 9130 is approximately 35 x 256, the Windows Installer interprets a "1.9130.8955" like a "35.169.8955". Therefore an OpenOffice.org with a "2.0.8958" finds a newer version. There is no easy fix for this. Always to add "34" to the Windows Installer Upgrade table making "2.0.8958" to "36.0.8958" is not really a good solution. Another solution could be, not to look for newer versions. Or, the simplest solution: Remove all 1.9.x installations and work with OOo 2.0. An OOo 2.0 which finds an OOo 1.9.x would do nothing else ;-)
I have observed that the version packaged as OOo_2.0beta2_Win32Intel_install.zip is in fact 19.m125. Thus if you have m125 installed, no upgrade/install should occur. Perhaps repacking the zipfile is in order.
reassign to is
@is: how high is the probability that OOo will get more than 34 major releases? If you can implement a query ProductVersion > 34.x.x and decide a positive result to be handled as 1.9x.x it would work for OOo2.0 and OOo3.0 (afterwards there will probably nobody update from 1.9.x to a new version). It's much better than changing the ProductVersion of OOo2.0. Perhaps this could be easier to implement. Bernhard
@is: how high is the probability that OOo will get more than 34 major releases? If you can implement a query ProductVersion > 34.x.x and decide a positive result to be handled as 1.9x.x it would work for OOo2.0 and OOo3.0 (afterwards there will probably nobody update from 1.9.x to a new version). If I am right, 1.9.versions lower than 100 are counted as 1.901.xxx and higher. That means a windows ProductVersion = 3.x.x and higher. For OOo2.0.x we could include these ProductVersion in the query. It's much better than changing the ProductVersion of OOo2.0. Perhaps this could be easier to implement. Bernhard
Well, I think the following will be the best: I will find new products only from current version till OOo 34 . Then an OOo 40 will not be found as new product, but I think this is no real problem. Versions from OOo 35.0.0 till OOo 36.0.0 will be recognized as old products. Then all producs 1.9xxx.yyyy will be removed. A fix will be available soon.
Fixed in cws hr19
As I heard, there will be no installation sets in cws hr19, I tested this by my own: 1. upgrade table looks good, containing four lines instead of three and searching only for new version till OOo 34. 2. My locally built OOo 2.0 installation set successfully deinstalled an OO 1.9130.build before installing itself. -> Verified.
*** Issue 55219 has been marked as a duplicate of this issue. ***
*** Issue 55317 has been marked as a duplicate of this issue. ***
*** Issue 55313 has been marked as a duplicate of this issue. ***
This may be marked as being "fixed" but it isn't. I downloaded a few minutes ago the 2.0rc and it reported my 1.9.125 as a "newer" version and wouldn't install. Fortunately I knew what to do, but many users will not.
markellse: FIXED is not the same as CLOSED. FIXED means it is fixed in CVS somewhere. CLOSED means it is fixed in uploaded build/milestone.
*** Issue 55402 has been marked as a duplicate of this issue. ***
In release candidate 2 this problem does no longer occur -> closing issue.