Hide Forgot
Installed packages: wine-1.3.33-1.fc16.x86_64 wine-alsa-1.3.33-1.fc16.x86_64 wine-capi-1.3.33-1.fc16.x86_64 wine-cms-1.3.33-1.fc16.x86_64 wine-common-1.3.33-1.fc16.noarch wine-core-1.3.33-1.fc16.x86_64 wine-courier-fonts-1.3.33-1.fc16.noarch wine-desktop-1.3.33-1.fc16.noarch wine-devel-1.3.33-1.fc16.x86_64 wine-docs-1.2-1.fc14.noarch wine-fonts-1.3.33-1.fc16.noarch wine-ldap-1.3.33-1.fc16.x86_64 wine-marlett-fonts-1.3.33-1.fc16.noarch wine-ms-sans-serif-fonts-1.3.33-1.fc16.noarch wine-openal-1.3.33-1.fc16.x86_64 wine-pulseaudio-1.3.33-1.fc16.x86_64 wine-small-fonts-1.3.33-1.fc16.noarch wine-symbol-fonts-1.3.33-1.fc16.noarch wine-systemd-1.3.33-1.fc16.noarch wine-system-fonts-1.3.33-1.fc16.noarch wine-sysvinit-1.3.33-1.fc16.noarch wine-tahoma-fonts-1.3.33-1.fc16.noarch wine-twain-1.3.33-1.fc16.x86_64 See attached for the required data. Please note, for example, that wine x86_64 is dependent on wine-core.i686 even though wine-core-1.3.33-1.fc16.x86_64 is installed. My general assumption is that it is probably not a great idea to have i686/x64 duplicates on the same system. All of the 64 bit packages that were duplicated by an i686 package were re-installed via yum. However, once the i686 duplicates are removed, wine no longer functions.
Created attachment 549233 [details] Yum output
What you are seeing is correct and intended behavior. Wine(x86-64) can run Windows 64bit applications Wine(x86-32) can run Windows 32bit applications Thus we pull in x86-32 packages on x86-64 since the common use is more on 32bit applications. You can avoid this by not installing the wine meta package but the dependent packages except the 32bit versions.