On Tue, 2006-09-05 at 15:43 +0200, David Hrbáč wrote:
Konstantin Klimchev napsal(a):
I dare to assume - there can be it consequences of correction RedHat #151255 ?
If to execute a command: # yum --installroot /var/lib/mock/centos-4-i386-core/root install filesystem
Well, probably something different. I took old virtual machine in VMWare, running 2.6.9-34EL.
- installed mock-0.6.4-1
- run mock pam...src.rpm - OK
- yum update rpm - updated to 4.3.3-18
- run mock pam...src.rpm - OK
- yum update yum - updated to 2.4.3-1
- run mock pam...src.rpm - OK
- yum update sqlite - updated to 3.3.3-1.2
- run mock pam...src.rpm - not working anymore, because yum is not working
- rpm -Uhv python-sqlite-1.1.7-1.2
- run mock pam...src.rpm - OK
- yum -y update, no reboot to stay on older kernel
- run mock pam...src.rpm - not working - "can't create transaction
lock on /var/lib/mock/centos-4-i386/root/var/lock/rpm/transaction" and "Could not find useradd in chroot, maybe the install failed?" 13. reboot, run mock - the very same
So I dare to say it has nothing to do with mock/rpm/yum/sqlite/python-sqlite...
http://rhn.redhat.com/errata/RHBA-2006-0440.html
The fix is to define _rpmlock_path inside the chroot as the user who is installing the software (per the above link).