How to fix yum update failure blaming “qpid-cpp”

I’ve just tried to update one of my CentOS 6.2 servers that was built from an older AMI, only to find that the yum update command stopped unexpectedly with several dependency errors. They all pointed to something called “qpid”, and I must admit that I’ve never heard of it – nor did I know that it was installed.

The long list ended with the following suggestion:

And why not indeed, since yum is so nice to give us suggestions. I’ve tired running “yum update –skip-broken” and got the following message:

Looks like this didn’t quite work either.

The Solution

Turns out this is actually a bug in yum, and it’s been fixed in newer versions of CentOS. All I had to do to make it work is first uninstall both culprit packages, and then re-install them just in case they are needed.

Let’s uninstall them:

and

Culprits removed. Now bring them back with

and we’re done. Now yum update works fine again without any error messages.

About Jay Versluis

Jay is a medical miracle known as a Super Survivor. He runs two YouTube channels, five websites and several podcast feeds. To see what else he's up to, and to support him on his mission to make the world a better place, check out his Patreon Campaign.

13 thoughts on “How to fix yum update failure blaming “qpid-cpp”

  1. Someone can help me please? I’ve updated bash yesterday with (yum update bash) to prevent shellshock’s attack, the update was successful (no error message) but it seems it’s not been intalled in my redhat 6. The test was failed. Can you help me please?

    1. Tricky one, and slightly off topic here. I’ve updated all my systems to the latest version of BASH under CentOS and they all passed the following test:

      However, one of my instances running on Parallels Desktop has been updated but is failing the test. The only difference I could find was the failed system shows it’s running bash-4.1.2-15.el6_4.x86_64, whereas all working (passed) systems are running 4.1.2-15.el6_5.2. What’s your system, a dedicated server or a VM?

  2. Thanks! 😀
    The –skip-broken switch worked for me in terms of allowing me to update everything else, but the dependency problems/components were resolved with your steps.

Add your voice!