Issue 17564 - Workstation installation of 1.1RC2 affects already installed 1.0.3
Summary: Workstation installation of 1.1RC2 affects already installed 1.0.3
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Olaf Felka
QA Contact: issues@installation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-29 11:47 UTC by stroeder
Modified: 2003-09-16 12:06 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description stroeder 2003-07-29 11:47:54 UTC 
$ /opt/OpenOffice.org1.1RC/setup

syntax error at token : /home/michael/OpenOffice.org1.0.3/instdb.ins: line 169,
'mimelnk' expected ';'

If I remove (rename) /home/michael/OpenOffice.org1.0.3 workstation installation
works as expected.
Comment 1 Olaf Felka 2003-07-29 14:57:38 UTC 
I've made a -net installation of OOo 1.0.3.1 and 1.1 (current inhouse
version 645m15), then I've started a workstation installation of
1.0.3.1. After  that I've started the workstation installation of 1.1.
Setup offers to install 1.1 in a new directory or to update 1.0.3.
After doing an update everything works fine, no error at installation.
I suggest that if there has been a bug, it's fixed for (one of) the
next builds.
Comment 2 Olaf Felka 2003-07-29 14:58:02 UTC 
Thanx for your help.
Comment 3 stroeder 2003-08-16 13:02:44 UTC 
Sorry, this issue still has not been solved with 1.1RC3. Still the
same error message is shown on the console and setup program hangs. I
wanted to install in a *separate* directory having 1.0.3.1 and 1.1RC3
used parallel.
Comment 4 Olaf Felka 2003-08-17 12:05:59 UTC 
So there must be a problem in your 1.0.3 installation.
Comment 5 Olaf Felka 2003-08-25 10:32:53 UTC 
It's not reproducible for me.
Comment 6 Olaf Felka 2003-09-16 12:06:46 UTC 
I think this depends on a somehow damaged 1.0.3 file.