Bug 2284009

Summary: Error when upgrading, can't find /usr/sbin/rm
Product: [Fedora] Fedora Reporter: Robert Hinson <robert.hinson>
Component: swtpmAssignee: Stefan Berger <stefanb>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 40CC: davide, marcandre.lureau, stefanb
Target Milestone: ---Keywords: Upgrades
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-30 17:57:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Robert Hinson 2024-05-30 16:22:12 UTC 
I get this error.

  Upgrading        : swtpm-0.8.1-11.fc40.x86_64                          18/312
  Upgrading        : swtpm-selinux-0.8.1-11.fc40.noarch                  19/312
  Running scriptlet: swtpm-selinux-0.8.1-11.fc40.noarch                  19/312
/var/tmp/rpm-tmp.EtHRxH: line 13: /usr/sbin/rm: No such file or directory
/var/tmp/rpm-tmp.EtHRxH: line 13: /usr/sbin/rm: No such file or directory
/var/tmp/rpm-tmp.EtHRxH: line 13: /usr/sbin/rm: No such file or directory

Did rm get moved from /usr/sbin/rm to /usr/bin/rm?

It happened in another package that got updated.

Reproducible: Always

Steps to Reproduce:
1. When upgrading swtpm-selinux package.
2. I get this error: /var/tmp/rpm-tmp.EtHRxH: line 13: /usr/sbin/rm: No such file or directory
3. I guess the rpm scripts need to be updated.
Comment 1 Stefan Berger 2024-05-30 17:57:34 UTC 
This has already been discussed and resolved here: https://bugzilla.redhat.com/show_bug.cgi?id=2283639#c1
Comment 2 Stefan Berger 2024-05-30 17:57:55 UTC 

*** This bug has been marked as a duplicate of bug 228363 ***
Comment 3 Stefan Berger 2024-05-30 17:58:15 UTC 

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