Description of problem: I found the following error message when I installed clamav-data. ... Running scriptlet: clamav-data-1.0.5-1.el9.noarch 1/1 /var/tmp/rpm-tmp.We4WX5: line 5: [: too many arguments ... It seems that this is the same problem to Bug 2253914. Version-Release number of selected component (if applicable): clamav-data-1.0.5-1.el9.noarch.rpm How reproducible: Everytime on installation Steps to Reproduce: 1. Download clamav-data-1.0.5-1.el9.noarch.rpm 2. Install clamav-data-1.0.5-1.el9.noarch.rpm like below. # cat /etc/redhat-release Red Hat Enterprise Linux release 9.2 (Plow) # yum localinstall -y clamav-data-1.0.5-1.el9.noarch.rpm Updating Subscription Management repositories. Unable to read consumer identity This system is not registered with an entitlement server. You can use subscription-manager to register. Last metadata expiration check: 2:48:51 ago on Thu Feb 22 11:34:54 2024. Dependencies resolved. =================================================================== Package Arch Version Repository Size =================================================================== Installing: clamav-data noarch 1.0.5-1.el9 @commandline 222 M Transaction Summary =================================================================== Install 1 Package Total size: 222 M Installed size: 223 M Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : clamav-data-1.0.5-1.el9.noarch 1/1 Running scriptlet: clamav-data-1.0.5-1.el9.noarch 1/1 /var/tmp/rpm-tmp.We4WX5: line 5: [: too many arguments Verifying : clamav-data-1.0.5-1.el9.noarch 1/1 Installed products updated. Installed: clamav-data-1.0.5-1.el9.noarch Complete! 3. Only /var/tmp/rpm-tmp.We4WX5 is defferent on each installation. Actual results: Message of "/var/tmp/rpm-tmp.We4WX5 ..." shows. Expected results: No message of "/var/tmp/rpm-tmp.We4WX5 ..." should show. Additional info: As I said already, this might be the same problem to Bug 2253914.
*** This bug has been marked as a duplicate of bug 2253914 ***