Issue 93400 - Installer lost critical functionality and has become unusable in Dev300m30
Summary: Installer lost critical functionality and has become unusable in Dev300m30
Alias: None
Product: Installation
Classification: Application
Component: ui (show other issues)
Version: OOo 3.0 Beta 2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: needhelp, needmoreinfo, oooqa
Depends on:
Reported: 2008-09-02 23:30 UTC by tadawson
Modified: 2013-02-03 02:59 UTC (History)
4 users (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description tadawson 2008-09-02 23:30:10 UTC
The installer no longer allows the user to state install path, and if an old
installation is anywhere other than /opt, gets confused and splatters the
install in the wrong location.  The installer also has begun checking
unnecessary dependencies which causes install to fail on non RPM native systems,
where it used to function since version 2.x . . .
Comment 1 Rainer Bielefeld 2008-09-03 05:45:56 UTC
Thank you for your report.
Please read our guidelines on
<> and  
<>, then
contribute a clear step by step instruction containing all observations (error
messages ...), every key press and every mouse click how to reproduce the
problem, and explain why you believe that your results are unexpected.

What Linux distribution do you use?
Comment 2 tadawson 2008-09-03 22:48:04 UTC
Slackware with a lot of my own modifications.  It has RPM support,
but the entire OS is installed without it, such that "rpm -qa" is a blank
report until OO goes on.  With no dependency checks, OO loads and runs
perfectly (and always has) - the checks cause the install to fail, and if I
go push the "basis" packages on by hand with "rpm --nodeps", and let the
installer do the rest, this release works as well, with the only problem being
that I do *NOT* want it in /opt . . . I have a partition for large software
releases that, until this cut, was usable . . .

The issue is not that the versions mismatch, it's that some distros don't have
RPM databases populated from the install at all . . . . 
Comment 3 tadawson 2008-09-03 22:49:31 UTC
Oh, and to duplicate the problem, simply attempt any installation, wait for it
to fail, and then look at the log, and I see failed dependencies on rudimentary
stuff like /bin/sh and such . . . 
Comment 4 Olaf Felka 2009-06-09 07:00:50 UTC
@ is: Please comment.
Comment 5 Olaf Felka 2010-12-07 13:14:59 UTC
I don't see that someone will prepare a slackware solution. If someone has a fix
he might reopen that issue.
Comment 6 tadawson 2010-12-07 15:26:27 UTC
The fix is simple - allow the option to install to any path entered, and to
install without dependency checks in the RPM command lines.  C'Mon guys - this
is simple to fix to the point of being brainless . . . .

- Tim
Comment 7 Rob Weir 2013-02-02 02:57:14 UTC
This Issue requires more information ('needmoreinfo'), but has not been updated
within the last year. Please provide feedback as requested and re-test with the the latest version of OpenOffice - the problem(s) may already be addressed. 

You can download Apache OpenOffice 3.4.1 from

Please report back the outcome of your testing, so this Issue may be closed or
progressed as necessary - otherwise the issue may be Resolved as Invalid in the
Comment 8 tadawson 2013-02-03 02:59:27 UTC
I frankly have no clue what additional information I can provide.  Plainly and simply, you don't have any provision in the installer to bypass RPM checks to use on systems which don't use RPM for management!

This is as simple as a check box "Omit RPM checks", "Force Install" etc. in the installer, which will pass --nodeps to the installer. 

For now, I have to manually install all the RPMs from the command line, and skip the OpenOffice installer entirely . . . The product works fine, but the reduction in functionality in the installer is pretty negligent from a support standpoint. 

Regarding 3.4.1, all I get in the download is RPMS - no installer, so if the fix was to remote the installer completely . . . . that seems like more backsliding. 
If I missed something, IE the installer, please advise, and I will look some more. The two readme files provided in the tarball are pretty much useless on how one is intended to install 3.4.1 as well . . . I could do CLI rpm -i, but that was the point - for a product of this level of complexity and support, I should not have to!

Please advise . . . 

- Tim