Meaning of the yum error "Package tuple (...) could not be found in rpmdb"

7,217

Solution 1

Sounds like corrupt data. Do: yum clean all followed by yum update and then try the installation again.

Solution 2

You could try rebuilding the rpmdb

rpmdb --rebuilddb

This fixed a similar problem for me.

Solution 3

To solve that problem I had to do both:

yum clean all 
rpm --rebuilddb
Share:
7,217

Related videos on Youtube

Juned
Author by

Juned

android application Developer, with a keen interest in all things code. Particular areas: C C++ ASP.NET PHP core JAVA Oracle MySQl MS SQL Server 2005/2008 Linux Android

Updated on September 18, 2022

Comments

  • Juned
    Juned over 1 year

    I just want to install two packages in my Fedora 15 but I am getting some weird error.

    Command:
    yum install @development-tools

    Error:

    Loaded plugins: langpacks, presto, refresh-packagekit Setting up Install Process Package flex-2.5.35-13.fc15.x86_64 already installed and latest version Error: Package tuple ('gcc', 'x86_64', '0', '4.6.0', '6.fc15') could not be found in rpmdb

    Command:
    yum install fedora-packager

    Error:

    Loaded plugins: langpacks, presto, refresh-packagekit Setting up Install Process Error: Package tuple ('fedora-packager', 'noarch', '0', '0.5.9.0', '1.fc15') could not be found in rpmdb

    On first command it says package already installed and latest version but why I got that error line.How to fix this errors?

  • Juned
    Juned over 11 years
    does this commands affect my existing system?
  • Faruk Mambi
    Faruk Mambi over 11 years
    It's the Yum equivalent of using apt-get update so all affects are positive.
  • Juned
    Juned over 11 years
    only yum clean all solved my issue. Thanks :)
  • vonbrand
    vonbrand over 11 years
    Perhaps you need to do a rpm --rebuilddb and check that no strange files are left in /var/lib/rpm. If there are __db.xxx files around, db_recover might be called for.
  • Admin
    Admin over 10 years
    In my case a 'yum clean all' did the trick. The message I got was after using the 'fedup' program to update me from F17 to F19.
  • jammypeach
    jammypeach about 9 years
    +1 - this sorted the issue for me, when yum clean all didn't.