Description of problem: It's not possible to install both alsa-lib-devel.i386 and alsa-lib-devel.x86_64. There are many file conflicts due to the documentation. Version-Release number of selected component (if applicable): 1.0.18 How reproducible: Always Steps to Reproduce: 1. yum install alsa-lib-devel.i386 2. yum install alsa-lib-devel.x86_64 3. Actual results: The second install fails due to file conflicts. Expected results: Both packages install. Additional info: Many messages of the form: file /usr/share/doc/alsa-lib-devel-1.0.18/doxygen/html/pcm__adpcm_8c.html from install of alsa-lib-devel-1.0.18-6.rc3.fc10.i386 conflicts with file from package alsa-lib-devel-1.0.18-6.rc3.fc10.x86_64 file /usr/share/doc/alsa-lib-devel-1.0.18/doxygen/html/pcm__alaw_8c.html from install of alsa-lib-devel-1.0.18-6.rc3.fc10.i386 conflicts with file from package alsa-lib-devel-1.0.18-6.rc3.fc10.x86_64 file /usr/share/doc/alsa-lib-devel-1.0.18/doxygen/html/pcm__asym_8c.html from install of alsa-lib-devel-1.0.18-6.rc3.fc10.i386 conflicts with file from package alsa-lib-devel-1.0.18-6.rc3.fc10.x86_64 file /usr/share/doc/alsa-lib-devel-1.0.18/doxygen/html/pcm__copy_8c.html from install of alsa-lib-devel-1.0.18-6.rc3.fc10.i386 conflicts with file from package alsa-lib-devel-1.0.18-6.rc3.fc10.x86_64
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Can confirm the bug for alsa-lib-devel-1.0.18-6.rc3.fc10.$(arch).rpm with arch=('i386', 'x86_64'). Paste: http://paste2.org/p/131316
Appears to still happen with alsa-lib-devel i386 1.0.19-1.fc10 alsa-lib-devel x86_64 1.0.19-1.fc10
alsa-lib 1.0.19-2 packages should fix this issue.
*** Bug 474539 has been marked as a duplicate of this bug. ***
*** Bug 475028 has been marked as a duplicate of this bug. ***
alsa-lib-1.0.19-2.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.