Mailinglist Archive: zypp-devel (58 mails)

[Michael Matz <matz@xxxxxxx>]

Hi,

On Tue, 2 Jun 2009, Bernhard Rosenkränzer wrote:

> # rpmdb2solv -o test.solv ; echo $?
> 0
> # rpmdb2solv -o test1.solv test.solv; echo $?
> db->get: No such file or directory
> corrupt rpm database
> 1
>
> Any idea why rpmdb2solv could be failing when trying to update an older
> file, while it works when building from the same rpmdb from scratch?

Look at the source :)  rpmdb2solv cleverly reads in some parts of the old 
database when it's presented with an old solv file.  It reads in the 
database IDs for each package (from /var/lib/rpm/Name, which is quick), 
and compares them with the ones in the old .solv file.  Only packages 
which meanwhile have a different or new ID (those got 
updated/reinstalled/changed by rpm) are reparsed from the full rpm 
database and merged into the old .solv file to produce the new one.

My guess is, that this database ("Name") has a different format or name in 
rpm5.


Ciao,
Michael.