It is very much possible that every time you try to remove or uninstall a rpm, you get "error: failed dependencies". Now here you have two choice with you.
This choice completely depends on the type of rpm and list of dependency rpms. For most rpms like the one I have shown in my example, I see few rpms as dependency so I can choose to ignore the dependencies and just proceed with the offline removal of pykickstart rpm as I know the dependency rpms are required and will not impact my running system.
So the rpm is removed while the dependencies are still present on my Linux node, as you can see below:. Now you must be wondering, why yum shows a larger list of dependency rpms compared to STDERR while doing rpm -e pykickstart? Now before attempting to remove rpm, yum will locate the dependency list of the dependency rpms i.
Hence the entire chain must be removed. Lastly I hope the steps from the article to remove rpm or install rpm along with dependency rpms fixing failed dependencies was helpful. So, let me know your suggestions and feedback using the comment section.
If my articles on GoLinuxCloud has helped you, kindly consider buying me a coffee as a token of appreciation. For any other feedbacks or questions you can either use the comments section or contact me form.
This is my first time I have visited your site. I found a lot of interesting stuff in your blog. Let's take a look the manual about rpm : --force Same as using --replacepkgs, --replacefiles, and --oldpackage. Vadim Kotov 7, 8 8 gold badges 45 45 silver badges 61 61 bronze badges. James James 2 2 bronze badges. That didn't answer my question. Not replace it with the old one Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.
Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Because RPM performs intelligent upgrading of packages with configuration files, you may see the following message:.
This message means that the changes you made to the configuration file may not be forward-compatible with the new configuration file in the package, so RPM saved your original file and installed a new one. You should investigate the differences between the two configuration files and resolve them as soon as possible to ensure that your system continues to function properly.
You should still resolve any conflicts between your modified configuration file and the new one, usually by merging changes from the old one to the new one, for example using the diff program.
Uninstalling a package is just as simple as installing one. Type the following command at a shell prompt as root :. Note that the command expects only the package name , not the name of the original package file. If you attempt to uninstall a package using the rpm -e command and provide the original full file name, you receive a package-name error.
You can encounter dependency errors when uninstalling a package if another installed package depends on the one you are trying to remove. For example:. Although you can force rpm to uninstall a package that has unresolved dependencies using the --nodeps option , this is not recommended.
Removing packages with --nodeps can cause applications from the packages whose dependencies are removed to misbehave or terminate unexpectedly. For these reasons, heed the warnings about failed dependencies.
Freshening is similar to upgrading, except that only installed packages are upgraded. The -F or --freshen option compares the versions of the packages specified on the command line with the versions of packages that are already installed on the system. When a newer version of an already-installed package is processed by the --freshen option, it is upgraded to the newer version.
However, the --freshen option does not install a package if no previously-installed package of the same name exists. This differs from regular upgrading, as an upgrade installs all specified packages regardless of whether or not older versions of the packages are already installed. Freshening works for single packages or package groups. For example, freshening can help if you download a large number of different packages, and you only want to upgrade those packages that are already installed on the system.
RPM then automatically upgrades only those packages that are already installed. To query this database, use the rpm command with the -q or --query option:. See the Package Selection Options subheading in the rpm 8 manual page for a list of options that can be used to further refine or qualify your query. Use options listed below the Package Query Options subheading to specify what information to display about the queried packages. Verifying a package is comparing information about files on the system installed from a package with the same information from the original package.
Among other parameters, verifying compares the file size, MD5 sum, permissions, type, owner, and the group of each file. Use the rpm command with the -V or --verify option to verify packages. Use options listed below the Verify Options subheading to specify what characteristics to verify in the queried packages.
If everything verifies properly, there is no output. If there are any discrepancies, they are displayed. The output consists of lines similar to these:. The format of the output is a string of nine characters followed by an optional attribute marker and the name of the processed file. The first nine characters are the results of tests performed on the file. Each test is the comparison of one attribute of the file to the value of that attribute as recorded in the RPM database.
A single period. The following table lists symbols that denote specific discrepancies:. The attribute marker, if present, describes the purpose of the given file. The following table lists the available attribute markers:. If you see any output, use your best judgment to determine if you should remove the package, reinstall it, or fix the problem in another way.
Improve this answer. Michael Hampton Michael Hampton k 39 39 gold badges silver badges bronze badges. I have tried -Uvh but when an already installed version of an rpm dependency exists it does not progress to install the new rpms. Haros Why are you trying to install older versions of packages you already have installed? Just skip them. Of course I can delete them and rerun the command but I was hoping that rpm was smart enough to avoid this. RPM has very little dependency solving capability; this is generally handled at a higher level by a front end such as yum.
If you're using rpm itself, you get to handle this yourself. If this is the case, follow the instructions in the FAQ to: download all the dependencies use gettext I indeed use Perzl's binaries. I did what he proposes in his faq with gettext but still when I use -Uvh it stops when it detects that there is an already installed version of an rpm or a newer version isntalled and it does not progress to install the new ones see my edit.
Add the --force flag — dawud. Why would you ever want to install an older version at all? That's what I am saying. With --force if any old rpms exist in the directory it will isntall them and I don't want to do that.
Show 1 more comment.
0コメント