Bug 466633 - Problems installing Adobe Software from their repo with yum
Problems installing Adobe Software from their repo with yum
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Seth Vidal
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-10-11 17:33 EDT by Arnold Sutter
Modified: 2014-01-21 18:06 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-11 19:10:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
typescript describing the issue. (28.44 KB, text/plain)
2008-10-11 17:43 EDT, Arnold Sutter
no flags Details

  None (edit)
Description Arnold Sutter 2008-10-11 17:33:20 EDT
Description of problem:
Can't install Adobe Reader with yum from Adobe's repo.

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

How reproducible:
Install flash-plugin or Adobe Reader from Adobe's yum repository.

Steps to Reproduce:
Actual results:
See attached typescript.

Expected results:
Working Adobe Reader / Flash Plugin with yum

Additional info:
maybe this problem affects only the x86_64 architecture?
Comment 1 Arnold Sutter 2008-10-11 17:43:25 EDT
Created attachment 320123 [details]
typescript describing the issue.

Attached typescript illustrates this issue.
Comment 2 James Antill 2008-10-11 19:10:58 EDT
 The transcript is full of lines like:

  file /usr/share/locale/af/LC_MESSAGES/atk10.mo from install of atk-1.24.0-1.fc10.i386 conflicts with file from package atk-1.23.5-1.fc10.x86_64

...ie. atk is not multilib compatible, you have the .x86_64 version installed and acroread requires the .i386 version.
 Feel free to ask Adobe for a .x86_64 version ... or ask the atk developers to fix their locale conflicts (the later is probably easier).

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