Description of Problem: When installing the rpm from rawhide, I get:: [root@localhost i386]# rpm -Fvh rpm* Preparing... ########################################### [100%] groupadd: group rpm exists useradd: user rpm exists 1:rpm ########################################### [ 25%] error: cannot get exclusive lock on /var/lib/rpm/Packages error: cannot open Packages index using db3 - Operation not permitted (1) 2:rpm-build ########################################### [ 50%] 3:rpm-devel ########################################### [ 75%] 4:rpm-python ########################################### [100%] [root@localhost i386]# rpm -q db3 db3-3.1.17-7 [root@localhost i386]# rpm -q rpm rpm-4.0.3-0.26 As you can see, it seems to install OK. It seems an odd warning. Nothing else was running at the time. How Reproducible: Steps to Reproduce: 1. 2. 3. Actual Results: Expected Results: Additional Information:
Not just you, happpens to me too. Repeatable by repeating the install using rpm -Uvh --force, too. [root@fraser RPMS]# rpm -Uvh --force rpm-4.0.3-0.26.i386.rpm Preparing... ########################################### [100%] groupadd: group rpm exists useradd: user rpm exists 1:rpm ########################################### [100%] error: cannot get exclusive lock on /var/lib/rpm/Packages error: cannot open Packages index using db3 - Operation not permitted (1)
Yup. The %post in rpm is running "rpm --initdb" even when /var/lib/rpm/Packages exists. FIxed in next CVS checkin, should be in rpm-4.0.3-0.29.