Johnny Hughes napsal(a): >> 1. installed mock-0.6.4-1 >> 2. run mock pam...src.rpm - OK >> 3. yum update rpm - updated to 4.3.3-18 >> 4. run mock pam...src.rpm - OK >> 5. yum update yum - updated to 2.4.3-1 >> 6. run mock pam...src.rpm - OK >> 7. yum update sqlite - updated to 3.3.3-1.2 >> 8. run mock pam...src.rpm - not working anymore, because yum is not working >> 9. rpm -Uhv python-sqlite-1.1.7-1.2 >> 10. run mock pam...src.rpm - OK >> 11. yum -y update, no reboot to stay on older kernel >> 12. 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 >> > > 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). > No, I guess, this is not the issue. Setting %_rpmlock_path didn't help. As I have written, upgrading to rpm-4.3.3-18 within CentOS 4.3 doesn't block 'mocking'. David