Description of problem:Old package of acpid-2.0.19-5.fc19.x86_64 still exists with new version Version-Release number of selected component (if applicable): How reproducible:always Steps to Reproduce: 1. run yum check 2. acpid-2.0.20-2.fc20.x86_64 is a duplicate with acpid-2.0.19-5.fc19.x86_64 3. Actual results: yum remove acpid-2.0.19-5.fc19.x86_64 Loaded plugins: aliases, auto-update-debuginfo, changelog, fastestmirror, filter- : data, fs-snapshot, keys, list-data, merge-conf, post-transaction- : actions, priorities, protectbase, ps, refresh-packagekit, remove- : with-leaves, rpm-warm-cache, tmprepo, tsflags, upgrade-helper, : verify, versionlock Resolving Dependencies --> Running transaction check ---> Package acpid.x86_64 0:2.0.19-5.fc19 will be erased --> Finished Dependency Resolution Dependencies Resolved =================================================================================== Package Arch Version Repository Size =================================================================================== Removing: acpid x86_64 2.0.19-5.fc19 @updates/19 145 k Transaction Summary =================================================================================== Remove 1 Package Installed size: 145 k Is this ok [y/N]: y Downloading packages: Running transaction check Running transaction test Transaction test succeeded Running transaction /var/tmp/rpm-tmp.2hvSb0: line 1: fg: no job control error: %preun(acpid-2.0.19-5.fc19.x86_64) scriptlet failed, exit status 1 Error in PREUN scriptlet in rpm package acpid-2.0.19-5.fc19.x86_64 Verifying : acpid-2.0.19-5.fc19.x86_64 1/1 Failed: acpid.x86_64 0:2.0.19-5.fc19 Complete! Expected results: obviously it should have been removed before new was installed. Additional info:
Thanks for the report, but unfortunately this is something that cannot be fixed by the update. The manual workaround is needed: # rpm -e --noscripts acpid-2.0.19-5 Sorry for inconvenience. For details please follow the original bugzilla report. *** This bug has been marked as a duplicate of bug 995158 ***
Maybe you can explain why it cannot be automated.
(In reply to KitchM from comment #2) > Maybe you can explain why it cannot be automated. The bug is in the acpid-2.0.19-5 %postun, which is something you cannot modify by the update, because it is already installed. You also cannot run the above mentioned command in the e.g. %pre of the update. There may be some dirty hacks how to force the RPM to ignore the script, but it is better to avoid. There were more packages affected by this issue and so far (IIRC) no good automatic workaround exists.
Your implication appears to be that the script cannot first remove the old version. I find that hard to believe.