Description of problem: Due to yums desire to install both i386 and x86_64 packages on a x86_64 system a conflict arises when installing mono-core Version-Release number of selected component (if applicable): mono-core-1.1.16-1.1 How reproducible: 100% Steps to Reproduce: 1. yum install mono-core Actual results: massive conflict output Expected results: Succesful install Additional info: AMD64 X2 4400+ running Development 22072006
Why does yum try to install mono-core-i386 on x86_64 ?
Jesse Keating explained to me that this is the default behavior on FC6, I find it endlessly annoying as it causes problems left and right, takes up diskspace and takes longer to download.. however this is a debate to take up with Seth Vidal I guess.
I think this would be fixed by moving mono to %libdir. As per bug 185690.
Hmm.. How are we going to fix this in time for FC6? I was anticipating the move to libdir would be too big a change until FC7.
Yeah. I'm not sure. Does this conflict really happen in a default install on x86-64?
This is a bog standard install
Ugh, then we might have to move to libdir in fc6 anyway. I'll be gone next week, but i'll take a look at this the week after that.
I think this should be fixed in mono-1.1.16.1-1. This version has libmono split out into mono-lib, and the only devel package is mono-lib-devel. Both these packages are multilib safe, and they should be the only 32bit ones pulled into the 64bit distro.