Red Hat Bugzilla – Bug 1010971
acpica-tools conflicts with iasl
Last modified: 2013-11-10 03:11:56 EST
Description of problem:
Trying to yum update on an F19 machine with pmtools and iasl installed results in acpica-tools correctly replacing pmtools but not iasl This results in conflicts.
Version-Release number of selected component (if applicable):
acpica-tools-20130823-4.fc19.x86_64.rpm (version -2 in stable updates also hits this).
Steps to Reproduce:
1. Have pmtools and iasl installed
2. yum update
3. get conflicts
Package Arch Version Repository Size
acpica-tools x86_64 20130823-4.fc19 updates-testing 680 k
replacing pmtools.x86_64 20100513-4.fc19
Install 1 Package
Total download size: 680 k
Is this ok [y/d/N]: y
acpica-tools-20130823-4.fc19.x86_64.rpm | 680 kB 00:00
Running transaction check
Running transaction test
Transaction check error:
file /usr/bin/iasl from install of acpica-tools-20130823-4.fc19.x86_64 conflicts with file from package iasl-20120913-7.fc19.x86_64
file /usr/share/man/man1/iasl.1.gz from install of acpica-tools-20130823-4.fc19.x86_64 conflicts with file from package iasl-20120913-7.fc19.x86_64
Either replaces both packages or doesn't conflict with iasl.
acpica-tools-20130823-5.fc19 has been submitted as an update for Fedora 19.
This version should replace iasl correctly; the version number in the spec file was off by one.
acpica-tools-20130823-5.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing acpica-tools-20130823-5.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
acpica-tools-20130823-5.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
acpica-tools-20130823-5.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.