Bug 477642 - evolution-2.24.2-2.fc10.i386 conflicts with evolution-2.24.2-2.fc10.x86_64
evolution-2.24.2-2.fc10.i386 conflicts with evolution-2.24.2-2.fc10.x86_64
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
10
All Linux
low Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-12-22 11:50 EST by H.J. Lu
Modified: 2008-12-22 12:37 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-12-22 12:15:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description H.J. Lu 2008-12-22 11:50:05 EST
When I was updating Fedora 10, I got
...
  file /usr/share/locale/zh_HK/LC_MESSAGES/evolution-2.24.mo conflicts between attempted installs of evolution-2.24.2-2.fc10.x86_64 and evolution-2.24.2-2.fc10.i386
  file /usr/share/locale/zh_TW/LC_MESSAGES/evolution-2.24.mo conflicts between attempted installs of evolution-2.24.2-2.fc10.x86_64 and evolution-2.24.2-2.fc10.i386

Error Summary
Comment 1 Matthew Barnes 2008-12-22 12:04:53 EST
That's strange.  Is that the only conflicting file?

What does "rpm -q evolution" say?
Comment 2 H.J. Lu 2008-12-22 12:10:56 EST
My Fedora 10 was upgraded from Fedora 8 via Fedora 9. It had
both evolution.i386 and evolution.x86-64. I have removed
evolution.i386. Now "yum update" finished OK.
Comment 3 Matthew Barnes 2008-12-22 12:15:46 EST
Ah, that would explain it.  Closing as NOTABUG then.
Comment 4 H.J. Lu 2008-12-22 12:19:08 EST
If evolution-2.24.2-2.fc10.i386 can't be installed on x86-86, why
is it in x86-64 yum repository?
Comment 5 Matthew Barnes 2008-12-22 12:37:01 EST
It can, but I think they're meant to be mutually exclusive.

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