RPM Community Forums

Mailing List Message of <rpm-users>

Re: rpmdb not updated with installed packages

From: Jeffrey Johnson <n3npq@me.com>
Date: Thu 12 Dec 2013 - 19:10:27 CET
Message-id: <EA8D54DA-40F2-4BD9-9BB1-906499E0ACFF@me.com>

On Dec 12, 2013, at 12:34 PM, bishwajit goswami wrote:

> Hi,
> 
> I have a partition up and running with a set of RPMs. Now I want to prepare a backup partition with the same set of rpms. The installation goes through properly and the corresponding files are available on the alternate partition.
> The problem comes when querying the rpmdb of the created partition. The rpmdb do not seem to be updated with all the packages which were installed. A sample snapshot is below:
> [sysadmin-vm:0_RP0:/mnt/rpm/calvados]$ rpm -ivh --nodeps --root /partprep ncs6k-sysadmin-boot.*
> Preparing...                ##################################################
> ncs6k-sysadmin-boot.sc      ##################################################
> ncs6k-sysadmin-boot.all     ##################################################
> ncs6k-sysadmin-boot.lc      ##################################################
> ncs6k-sysadmin-boot.rp      ##################################################
> [sysadmin-vm:0_RP0:/mnt/rpm/calvados]$ rpm -qa --root /partprep
> ncs6k-sysadmin-boot.rp-5.2.0.01I-Default.x86_64
> ncs6k-sysadmin-boot.lc-5.2.0.01I-Default.x86_64
> [sysadmin-vm:0_RP0:/mnt/rpm/calvados]$
> 
> When I check the double verbose output, I simply see that a few packages got remove from addition to corresponding rpmdb files.
> D: removing "ncs6k-sysadmin-boot.sc" from Name index.
> D: removing 19 entries from Basenames index.
> D: removing "Calvados/ncs6k-sysadmin-boot/ncs6k-sysadmin/sc/Default/mandatory/PII
> 
> Any suggestion would be helpful in this regard. If needed, I could attach the verbose output.
> Also, the rpmdb do not seem to be corrupt since rpm verification runs smoothly.
> 

If you actually used -i (rather than -U), then rpm should _NOT_ have
removed anything.

The likeliest explanation is that there is an Obsoletes: in some package
that is causing a package to be removed.

Examine the -vv output ... everything that rpm does is logged in -vv output
(but there isn't enough information to guess the cause from what you provided).

73 de Jeff

> 
> -- 
> Bishwajit Goswami
> 
Received on Thu Dec 12 19:10:42 2013
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.