Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Errors during user workstation install | ||
---|---|---|---|
Product: | Installation | Reporter: | settantta |
Component: | code | Assignee: | khendricks |
Status: | CLOSED FIXED | QA Contact: | issues@installation <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues |
Version: | 644 | Keywords: | oooqa |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux, all | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
settantta
2003-02-28 04:42:52 UTC
Hi Kevin, do we need some changes for the install script? Hi, This has nothing to do with the" install" shell script as far as I know. But this may have something to do with recent changes to sysui, scp, and setup2 to support better desktop integration. The problem is people are getting builds to qa that I have never seen the exact source tree for and so I can't tell if there is simply an out of sync condition with sysui, scp, and setup2 or not. Right now cws_srx644_ooo20030309 has the most up to date pieces in it and does work for desktop integration. Right now cws_srx644_ooo1.1beta has the older scp, sysui, and setup2 I believe. I am trying to build this tree as we speak so that I can test things out. Unforutnately, I don't know what the source tree looked like that made the qa build and what was in it or not. Also as I understand things Mandrakesoft uses (used?) slightly non-standard desktop integration for kde and our old version never dealt well with it. So unless I can see the exact source of sysui, scp, and even setup2 I will not know how to answer your questions. Perhaps the right solution is for qa to only get test builds from the cws series of trees so that everyone can see what is going on and the exact state? Kevin Hi, I just tried a straight setup -net as root with 1.1beta built from cvs and setup -net aborts without completing the installation: (no setup symlink is made, no symlinks for versioning of libraries is made< etc). So according to my build, 1.1 beta is not properly installing everything (I get no completeion menu button at all. I am going to do some clean rebuilds over the weekend just to make sure the problem did not come from anyplace else but Hamburg might want to check the installation process to see what if anything is messed up. Kevin Hi, I have tried with OOo 1.1 Beta now and I can not create this. I will check this again for Beta 2 to make sure. Kevin Hi, This appears to be fixed in OOo 1.1 Beta 2 So resolving this as fixed. Kevin The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew |