RPM database problems.

RPM database problems.

Post by James Kufrovi » Thu, 31 Jan 2002 04:33:12



Hi.

        My system is running Mandrake 8.0, with RPM 4.0.  I don't know how
this thing got messed up, but my RPM database got horked somehow.  
Apparently, it thinks there are less packages installed than are actually
installed, compared to a backup of the system I made a month ago, even
after doing an 'rpm --rebuilddb'.  I get the following using the default
database:
-----------------

total 2729
-rw-------    1 root     root       663552 Jan 29 13:30 Basenames
-rw-------    1 root     root        12288 Jan 29 13:30 Conflictname
-rw-------    1 root     root        12288 Jan 29 13:30 Group
-rw-------    1 root     root        12288 Jan 29 13:30 Name
-rw-------    1 root     root      2121728 Jan 29 13:30 Packages
-rw-------    1 root     root        24576 Jan 29 13:30 Providename
-rw-------    1 root     root        45056 Jan 29 13:30 Requirename
-rw-------    1 root     root        12288 Jan 29 13:30 Triggername
drwxr-xr-x    2 root     root         1024 Jan  3 17:10 alternatives/

    103
---------------------------

        After extracting /var/lib/rpm from a month-old backup and using
that, I get:
-------------------

total 13664
-rw-r--r--    1 root     root      2715648 Dec 31 13:27 Basenames
-rw-r--r--    1 root     root        12288 Dec 30 16:13 Conflictname
-rw-r--r--    1 root     root        12288 Dec 31 13:27 Group
-rw-r--r--    1 root     root        24576 Dec 31 13:27 Name
-rw-r--r--    1 root     root     10895360 Dec 31 13:27 Packages
-rw-r--r--    1 root     root        86016 Dec 31 13:27 Providename
-rw-r--r--    1 root     root       200704 Dec 31 13:27 Requirename
-rw-r--r--    1 root     root        12288 Oct 24 22:36 Triggername
drwxr-xr-x    2 root     root         4096 Oct 24 23:05 alternatives/

    524

------------------------------------

        See?  The backed up database files are larger, and using the
backed-up version shows more packages.

        There are a few packages I installed since that backup was made,
but they can be reinstalled, though.  

        Is fixing the problem as simple as restoring the backed-up
/var/lib/rpm directory. or does RPM use more than just that?

        Thanks for any help.

Jamie Kufrovich

--
Egg, eggie (at) sunlink (dot) net

*Code:                      | Perl Geek Code, version .01:
FMSp3am/MSp3am A- C+ D H+ M+    | P+>+++ P6- R M>+ O->++ MA+
P+++ R+ T W Z+ Sp#/p++ RL->CT        | PU- BD C X? n o G Ee Ev- uL++
a+ cl++ d? e++ f h* i+ j p+ sm+ |

 
 
 

1. Mandrake 6.0 -- rpm database problem

How can one repair a corrupt rpm database ? Problem is if I use, e.g,
"rpm -q foo"
I got a "segmentation fault" as answer. This for all installed rpm's.
The same occurs for other rpm options like -e -v . Installing of new rpm
is also no longer possible. I've tried to reinstall (upgrade) the whole
mandrake 6.0 but the install program exit at "scanning packages" point
with a error 11. Under KDE the "package manager" simply exit if I ask to
install or delete a *.rpm file.

Thanks for any help

Eugene

2. stunnel to get nntp thru firewall?

3. rpm database problem

4. IP-Masquerading

5. Heaps of Linux Music Software to download...

6. RPM Database problem

7. How to skip blank lines when reading a text file?

8. rpm database problems solved

9. Recovering the /var/lib/rpm RPM database?

10. Incorporating RPM into RPM "database (depot?)"

11. RPM-database & non-rpm packages

12. Redhat 5.0 Upgrade Problem: No RPM database exists!