Bug 76940 - koffice-1.2-0.73.1.i386.rpm won't install
koffice-1.2-0.73.1.i386.rpm won't install
Product: Red Hat Linux
Classification: Retired
Component: koffice (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Depends On:
  Show dependency treegraph
Reported: 2002-10-29 15:49 EST by Paul Bolle
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-10-29 15:49:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Paul Bolle 2002-10-29 15:49:02 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827

Description of problem:
failed dependencies when installing koffice-1.2-0.73.1.i386.rpm 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.rpm -Uvh --test koffice-1.2-0.73.1.i386.rpm

Actual Results:  error: failed dependencies:
        libartsflow-gcc2.96.so.1   is needed by koffice-1.2-0.73.1
        libartsflow_idl-gcc2.96.so.1   is needed by koffice-1.2-0.73.1
        libkmedia2_idl-gcc2.96.so.1   is needed by koffice-1.2-0.73.1
        libmcop-gcc2.96.so.1   is needed by koffice-1.2-0.73.1
        libqtmcop-gcc2.96.so.1   is needed by koffice-1.2-0.73.1
        libsoundserver_idl-gcc2.96.so.1   is needed by koffice-1.2-0.73.1

Expected Results:  koffice installed without errors

Additional info:

These might be files provided by arts. I'm using arts-1.0.3-0.7, which I suppose
is up to date (enough), since I've installed KDE 3.0.3. Anyway, it's unclear to
me whether these files actually exist.
Comment 1 Ngo Than 2002-11-04 07:22:43 EST
i assume you have downloaded the kde rpms for 7.3 from ftp.kde.org.
Please make sure that you have to download all rpms from there and update with
rpm -Uvh * afterwards.

Note You need to log in before you can comment on or make changes to this bug.