You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openoffice.apache.org by bu...@apache.org on 2012/02/15 03:45:27 UTC
DO NOT REPLY [Bug 118915] New: No way to upgade previous OO to AOO
3.4 now
https://issues.apache.org/ooo/show_bug.cgi?id=118915
Bug #: 118915
Issue Type: DEFECT
Summary: No way to upgade previous OO to AOO 3.4 now
Classification: Application
Product: Installation
Version: OOo 3.4 Beta
Platform: PC
OS/Version: Windows XP
Status: CONFIRMED
Severity: normal
Priority: P3
Component: code
AssignedTo: olaf-openoffice@gmx.de
ReportedBy: doudou1976@hotmail.com
CC: ooo-issues@incubator.apache.org
Build: dev snapshot Rev. 1240836
Now no matter for Windows, Mac or Linux, I can install AOO 3.4 first and then
install OO 3.3, or in verse. That is, different OO/AOO version can exist on
same machine for same user. No way to do upgrade.
--
Configure bugmail: https://issues.apache.org/ooo/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
DO NOT REPLY [Bug 118915] No way to upgade previous OO to AOO 3.4
now
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=118915
Ariel Constenla-Haile <ar...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--
Configure bugmail: https://issues.apache.org/ooo/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
DO NOT REPLY [Bug 118915] No way to upgade previous OO to AOO 3.4
now
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=118915
zhao xia <do...@hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Flags| |3.4_release_blocker?
Severity|normal |blocker
--- Comment #1 from zhao xia <do...@hotmail.com> 2012-02-15 02:46:37 UTC ---
Mark as AOO 3.4 blocker.
--
Configure bugmail: https://issues.apache.org/ooo/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
3.4_release_blocker requested: [Bug 118915] No way to upgade
previous OO to AOO 3.4 now
Posted by bu...@apache.org.
zhao xia <do...@hotmail.com> has asked for 3.4_release_blocker:
Bug 118915: No way to upgade previous OO to AOO 3.4 now
https://issues.apache.org/ooo/show_bug.cgi?id=118915
------- Additional Comments from zhao xia <do...@hotmail.com>
Mark as AOO 3.4 blocker.
DO NOT REPLY [Bug 118915] No way to upgade previous OO to AOO 3.4
now
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=118915
Ariel Constenla-Haile <ar...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
CC| |arielch@apache.org
Resolution| |INVALID
--- Comment #2 from Ariel Constenla-Haile <ar...@apache.org> 2012-02-16 01:16:49 UTC ---
(In reply to comment #0)
> Build: dev snapshot Rev. 1240836
>
> Now no matter for Windows, Mac or Linux, I can install AOO 3.4 first and then
> install OO 3.3, or in verse. That is, different OO/AOO version can exist on
> same machine for same user. No way to do upgrade.
Because you are using Developer Snapshots, and these aren't supposed to be
considered as upgrade for a normal installation.
You can try that the same happens with previous OpenOffice.org Developer
Snapshots: you can install them in parallel to your normal OpenOffice.org
installation.
Developer Snapshots are a useful way to test new features and find bugs without
forcing the tester to damage his/her default installation. Unfortunately, some
aspects can not be tested this way.
To test the upgrade you'll have to install a nightly build, warned that this
will override your current installation.
Resolved as invalid. This is the way Dev. Snapshots work by design.
--
Configure bugmail: https://issues.apache.org/ooo/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.