Issue 33328 - Upgrade to 1.1.2 for user does not work
Summary: Upgrade to 1.1.2 for user does not work
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.1.2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: atr
QA Contact: issues@installation
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2004-08-23 21:40 UTC by akk
Modified: 2004-09-09 10:09 UTC (History)
1 user (show)

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


Attachments
Hope thix patch fixes the problem correctly (1.09 KB, patch)
2004-08-31 10:02 UTC, akk
no flags Details | Diff
Adding LANGUAGE line to responce file helps, but if setup is run interactively, it fails. (30.08 KB, image/png)
2004-08-31 23:39 UTC, akk
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description akk 2004-08-23 21:40:02 UTC
When a user, who already have has OOo installed, runs OOo 1.1.2 upgrade fails
with message:
wrong language for update (installed language doesn't match installation language)

I have checked this trying to upgrade 1.1.1 to 1.1.2 with English(01) and
Russian(07) installations.
Comment 1 Olaf Felka 2004-08-24 15:30:03 UTC
I can't reproduce with english OOo 1.1.1 and 1.1.2 versions.
Please be more detailed. Tell us which platform you are talking about. Which OOo
version should be upgraded. We need a detailed step-by-step walkthrough.
Comment 2 akk 2004-08-25 13:39:57 UTC
I've noticed this problem on Linux x86.

I've built OpenOffice_1_1_1 and OpenOffice_1_1_2 tags. (I've also built
cws_srx645_ooo112fix2, and the problem is reproducible with it also). Then I
install both versions somewhere and run setups from one user. (Actually, I run
it with a responce file, with a script I paste below, but even if you run it
interactively you should get a message that no appropriate language is already
installed for upgrade).

I get from setup:
wrong language for update (installed language doesn't match installation language)
ExitCode: 32

I wanted to test this with official builds, but OOo1.1.1 is removed from
mirrors, so I had to make tests with my own ones.

#!/bin/sh
installOOo() {
  
  TMPFILE=`mktemp -t responsefilie.XXXXXXX` || exit 1

  cat > $TMPFILE <<EOF
[ENVIRONMENT]
INSTALLATIONMODE=INSTALL_WORKSTATION
INSTALLATIONTYPE=WORKSTATION
UPDATEMODE=IF_AVAILABLE
DESTINATIONPATH=$HOME/.openoffice
OUTERPATH=
LOGFILE=
#LANGUAGELIST=<LANGUAGE>

[JAVA]
JavaSupport=preinstalled_or_none
EOF
  
  if ! OOo/OpenOffice.org1.1.1_en/setup -nogui -R:$TMPFILE
  then
    echo failed
    rm $TMPFILE
    exit 13
  fi

  rm $TMPFILE

}

installOOo
Comment 3 Olaf Felka 2004-08-25 13:52:51 UTC
You can't update the user part only. You have to update the -net installation
first. Then the user installation will make the update automatically: Start
setup -net -update <path to OOo 1.1.1>. You can only update versions with the
same language.
Comment 4 akk 2004-08-25 14:23:10 UTC
So do I.
Say, I have two builds.
I execute:
$ cd /home/builder3/OpenOffice_1_1_1/instsetoo/unxlngi4.pro/01/normal
$ ./install --prefix /home/builder3/OOo
<many lines skiped>
$ cd /home/builder3/OpenOffice_1_1_2/instsetoo/unxlngi4.pro/01/normal
$ ./install --prefix /home/builder3/OOo
<many lines skiped>

After this I get:
$ ls ~/OOo/
OpenOffice.org1.1.1  OpenOffice.org1.1.2

Now let us put

[ENVIRONMENT]
INSTALLATIONMODE=INSTALL_WORKSTATION
INSTALLATIONTYPE=WORKSTATION
UPDATEMODE=IF_AVAILABLE
DESTINATIONPATH=<home>/.openoffice
OUTERPATH=
LOGFILE=

into /tmp/inst.res

and run

$ ~/OOo/OpenOffice.org1.1.1/setup -nogui -R:/tmp/inst.res
$ ~/OOo/OpenOffice.org1.1.2/setup -nogui -R:/tmp/inst.res
wrong language for update (installed language doesn't match installation language)
ExitCode: 32
Comment 5 Olaf Felka 2004-08-25 14:49:42 UTC
I can't see that you have made an update installation of Ooo 1.1.1 with OOo
1.1.2. You have two OOo destinations: "$ ls ~/OOo/
OpenOffice.org1.1.1  OpenOffice.org1.1.2". With this configuration you can't
update a workstation installation.
Comment 6 akk 2004-08-25 16:05:35 UTC
I am almost sure and I belive, it is so: there is no need to make an upgrade of
system OOo installation to make a user one. Just think:
1. sysadm installs OOo1.1.1
2. user starts using it
3. sysadm removes OOo
4. sysadm installs OOo1.1.2
5. user is not able to upgrade?!

Anyway, hope I've done an upgrade as you wished me to do:
$ cd /home/builder3/OpenOffice_1_1_1/instsetoo/unxlngi4.pro/01/normal
$ ./install --prefix /home/builder3/OOo
$ ~/OOo/OpenOffice.org1.1.1/setup -nogui -R:/tmp/inst.res
$ cd /home/builder3/OpenOffice_1_1_2/instsetoo/unxlngi4.pro/01/normal
$ ./setup -nogui -R:/tmp/inst2.res -net -update
/home/builder3/OOo/OpenOffice.org1.1.1/
glibc version: 2.3.3

Initializing installation program....................
ln: `python': File exists
$ ~/OOo/OpenOffice.org1.1.1/setup -nogui -R:/tmp/inst.res
wrong language for update (installed language doesn't match installation language)
ExitCode: 32
$ cat /tmp/inst2.res 
[ENVIRONMENT]
INSTALLATIONMODE=INSTALL_NETWORK
INSTALLATIONTYPE=STANDARD
DESTINATIONPATH=/home/builder3/OOo/OpenOffice.org1.1.1
OUTERPATH=
LOGFILE=
LANGUAGELIST=<LANGUAGE>

[JAVA]
JavaSupport=preinstalled_or_none

Comment 7 akk 2004-08-26 21:19:40 UTC
I've made a small investigation on this trouble. If OOo sees that it should
probably upgrade previous version it checks if previously installed and running
languages are the same. The installed language is tried to be fetched from
~/<user's openoffice home>/instdb.ins, as value of Languages. But! This
variables exists in instdb.ins of net installation (/<openoffice
home>/program/instdb.ins), and does not in user's instdb.ins! So setup get empty
string for its request for installed languages, line ~720 of
setup2/source/ui/mainevt.cxx:
ByteString sProductLanguage = pCurrentInstall->GetLanguages();

Comment 8 akk 2004-08-31 10:02:45 UTC
Created attachment 17449 [details]
Hope thix patch fixes the problem correctly
Comment 9 Olaf Felka 2004-08-31 10:15:56 UTC
of @ atr: Please have a look at the responsfile. Maybe that the attached patch
is someting for DV. Please reassign if the problem can't be  solved by changes
in the responsfile.
Comment 10 atr 2004-08-31 10:28:35 UTC
ATR->AKK: I checked your reponsefile, and I think it could be a problem with the
languagelist entry. Please use LANGUAGELIST=01 for an english version or '07'
for the russian one. 
Comment 11 akk 2004-08-31 23:39:58 UTC
Created attachment 17465 [details]
Adding LANGUAGE line to responce file helps, but if setup is run interactively, it fails.
Comment 12 atr 2004-09-01 08:29:04 UTC
ATR->AKK: Please write a new bug for the new issue, after the problem of your
responsefile installation is solved. So it's easyer for all to understand the
bugdescription without the old stuff, which is no longer needed.
Comment 13 atr 2004-09-08 15:22:27 UTC
ATR: I close this bug now because the reporter change the state to 'worksforme'. 
Comment 14 atr 2004-09-08 15:22:42 UTC
.
Comment 15 akk 2004-09-08 17:50:21 UTC
INTERACTIVE UPGRADE DOES NOT WORK
Comment 16 atr 2004-09-09 07:04:12 UTC
ATR->AAK: See my comment from Sep 1 00:29:04 -0700 2004 and write a new bug,
please. This issue was a resonsefile-issue, the new bug is a issue for the gui
setup. So it's easyer for all to reproduce and understand the new problems of
your  installation whitout the old description.
Comment 17 atr 2004-09-09 07:04:23 UTC
.
Comment 18 akk 2004-09-09 07:29:36 UTC
I do not want to open a new issue because:
1. It will fall under current summary.
2. Comments on this issue will dissapear, even I think it is helpful.
3. Attachements of this issue will need to be transfered to the new one

Too much work I do not know what for.

And you should not close the issue until another is not opened for this problem
(Hm, this is idiotic).
Comment 19 atr 2004-09-09 10:08:56 UTC
ATR: Look at the comment from of, written on Aug 24. He couldn't reproduce your
issue in a interactive Update. Also I have no problems with the update feature,
in both ways (responsefile or with gui).

Your first attachment is a responsefile, and this problem is obsolete since Aug
31. The second attachment is a picture of the errormessage that an update isn't
possible.

But this is no info that help us to reproduce your NEW problem.

And all of the old comments in this bugdescription are not helpful in this new
issue.

Once again, please write a new issue with a step by step description of your
interactive update procedure.
Comment 20 atr 2004-09-09 10:09:06 UTC
.