Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | OO not functioning after upgrading 638 to 638C w/o deleting all files at deinstallation | ||
---|---|---|---|
Product: | Installation | Reporter: | simonbr |
Component: | code | Assignee: | Unknown <non-migrated> |
Status: | CLOSED IRREPRODUCIBLE | QA Contact: | issues@installation <issues> |
Severity: | Trivial | ||
Priority: | P1 (highest) | CC: | issues |
Version: | current | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 98 | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
simonbr
2001-10-03 12:02:19 UTC
Hi Matthias, should this be possible? Or must OOo have the same Build IDs to install 'over' the rest of an unistalled version? *** Issue 1959 has been marked as a duplicate of this issue. *** I don't understand that. Did you install 638c into the same directory as your 638? This would be definitely a desaster. How did you manage to install a 638c without deinstalling the 638? Usually this is prohibited because we don't have an update installation feature (IMHO). Without manipulating the sversion.ini file it is not possible to use two versions of OO with the same major version ( like OO638 and OO628c ) in paralell. But if you know how to manipulate sversion.ini, there is no problem to let OO638 and OO638c cooperate. So please give more information about what you've done exactly. Hi Mathias, I *did* deinstall 638 first! I just checked the option in the deinstall script so it would not delete any documents I might have prepared using it. It seems reasonable to assume that you can then safely install a new version in the same location. In any case, it appears I'm not the only one to have assumed this (see issue 1959). I agree with Jonathan's suggestion that, if a new version of OOo is being installed in a location that contains incompatible files from previous versions, the install script should emit a warning. Best regards, Simon. Perhaps we have a problem in this kind of "update" installation. This should be examined by the installation team. It looks like OO 638C doesn't like the registry files of 638. After removing ..\share\config\registry\.. and ..\user\config\registry\.. and doing a setup repair everything works fine. The 641C doesn't have these problems. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. |