In addition, using the –nodeps flag may cause other programs on the system to stop working. –test – checks if the uninstall would succeed or fail without actually performing actions.–notriggers – similar to –noscripts, stops the command from triggering scripts.–noscripts – blocks the command from executing scriptlets around the package processing.

–allmatches – removes all versions of packages that match the PACKAGE_NAME.PACKAGE_NAME – the name of the package to work with.Here are the roles of the flags in the command: To do so, we include some options in the rpm command: $ sudo rpm -e -allmatches -nodeps -noscripts -notriggers -test PACKAGE_NAME Indeed, we can force rpm to remove a package that gives us a Failed dependencies error. If the process is successful, rpm prints no output. The –test flag with -e checks if the erase command would succeed or fail without actually doing the uninstall. usr/bin/xz is needed by (installed) file-roller-3.28.86_64 Xz is needed by (installed) sysstat-11.7.86_64 Xz is needed by (installed) rpm-build-4.14.86_64 Xz is needed by (installed) libreport-2.9.86_64 Xz is needed by (installed) gettext-devel-0.19.8.86_64 installing a package when the system needs initial software to run the packageįor example, we can see the Failed dependencies error in the following command output: $ sudo rpm -test -e xz.removing a package that another package depends on.

Rhel rpm