Bug 1641214

Summary: rtkit package fails to update due to conflicts with a version to be updated
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal.jnn>
Component: rtkitAssignee: Lennart Poettering <lpoetter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: lpoetter, msekleta, thomas, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-22 20:54:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michal Jaegermann 2018-10-19 23:53:16 UTC
Description of problem:

An attempt to update rtkit ends up with:

Error: Transaction check error:
  file /usr/libexec/rtkit-daemon from install of rtkit-0.11-20.fc30.x86_64 conflicts with file from package rtkit-0.11-19.fc29.x86_64
  file /usr/sbin/rtkitctl from install of rtkit-0.11-20.fc30.x86_64 conflicts with file from package rtkit-0.11-19.fc29.x86_64

and an update transaction fails.

Actually one ends up with both rtkit-0.11-19.fc29 and rtkit-0.11-19.fc29 installad but an attempt to remove duplicates also fails as above.

Version-Release number of selected component (if applicable):
rtkit-0.11-20.fc30

How reproducible:
every time I tried

Additional info:
Trying 'dnf remove rtkit-0.11-19.fc29.x86_64' results in

/var/tmp/rpm-tmp.GijVJX: line 1: fg: no job control
error: %preun(rtkit-0.11-19.fc29.x86_64) scriptlet failed, exit status 1

and transaction fails.  Only 'rpm -e --noscripts rtkit-0.11-19' rectifies the issue.

Comment 1 Zbigniew Jędrzejewski-Szmek 2018-10-22 20:54:08 UTC
See https://fedoraproject.org/wiki/Common_F29_bugs#rtkit-update.

*** This bug has been marked as a duplicate of bug 1637496 ***