Bug 716872 - Installing of version 1.3.21-1.fc15 on arch x86_64 pulling in i686 binaries also
Summary: Installing of version 1.3.21-1.fc15 on arch x86_64 pulling in i686 binaries also
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: wine
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-27 10:35 UTC by vikram goyal
Modified: 2011-06-27 12:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 12:13:24 UTC
Type: ---

Attachments (Terms of Use)
output of yum install wine (19.12 KB, application/octet-stream)
2011-06-27 10:35 UTC, vikram goyal 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description vikram goyal 2011-06-27 10:35:54 UTC 
Created attachment 510063 [details]
output of yum install wine

Description of problem:
As mentioned in the subject line

Version-Release number of selected component (if applicable):
1.3.21-1.fc15

How reproducible:


Steps to Reproduce:
1.yum install wine
2.
3.
  
Actual results:
Pulls in i686 binaries also which are duplicates of x86_64. Means duplicate packages are being installed but of different arch

Expected results:


Additional info:
attaching file
Comment 1 vikram goyal 2011-06-27 10:44:25 UTC 
Please change the attachment mime info to text file. It has taken it as application/octet-stream.

Rather the mime type should be drop down list selectable.

Thanks
Comment 2 Andreas Bierfert 2011-06-27 12:13:24 UTC 
Pulling in x86-32 wine files is _intended_ upon installation of the wine meta package. A x86-64 only installation of wine will only be able to run win64 applications. This is not what most users need/want. If you really need a 64bit only wine you can remove all x86-32 packages together with the wine(x86-64) meta package.
Note You need to log in before you can comment on or make changes to this bug.