I am trying to install grive in my CentOS server. The rpm available is:


The problem is that the rpm seems to be tied to json-c version 0.11 but the one I really need is json-c 0.10.

In short: when yum displays the message:

"Dependencies resolved - The following two packages will be installed: grive and json-c 0.11"

is there any way to reply:

"Go ahead and install grive but DO NOT install (i.e. upgrade) json-c 0.11"


enter image description here

  • 1
    You realize that it is marked as a dependency because it won't work without it? – psusi Apr 6 '15 at 22:56
  • Gilles: In an ideal world, your comment would be correct. Many versions can fulfill the dependency. I have tried with json-c 0.11 and it does not work. Now I am going to try with json-c 0.10, because I happen to know that it is the same version used by a working application. – Travis Banger Apr 7 '15 at 2:11

Yum doesn't have a way to do this. It would counter the purpose of the package manager. Moreover, it will usually render a package dysfunctional. Package maintainer's put effort into ensuring dependencies are properly defined and not overly restrictive.

That said, you can install the rpm with the rpm utility using the --nodeps flag. As a result, it becomes your responsibility to manually manage the package's life cycle. Although this is generally unwise, you may find it useful to experiment with this option. The syntax is:

rpm -i --nodeps [package].rpm

Yum statement on the matter: http://yum.baseurl.org/wiki/NoDeps.html.

| improve this answer | |
  • 1
    "Package maintainer's put effort into ensuring dependencies are properly defined and not overly restrictive." Sure, in an ideal world, where there are no bugs! – Travis Banger Apr 7 '15 at 2:12

Like shibley said, this would defeat the purpose of the package manager. It would be wiser to download the source and compile it with the version of the dependency you need. Hopefully, for you, the version you want will work without any source mods.

| improve this answer | |
  • "...download the source and compile it..." - That would defeat the purpose of a package manager. – Steve Aug 22 '18 at 20:46
  • actually rpm is a package manager, yum is more of a repo manager/fetcher which can easily be replaced with curl/wget and rpm. So yum simply provides silly excuses for itself not having such a basic functionality. – Victor Polevoy Jan 17 at 10:53

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.