-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Seth,
This bug occurs on systems that don't have a /var/lib/rpm directory. The failure occurs while installing the chroot. Here's a snippet of a log of the failure:
<snip> Transaction Summary ============================================================================= Install 100 Package(s) Update 0 Package(s) Remove 0 Package(s)
Total download size: 103 M warning: mktemp-1.5-23.2.2: Header V3 DSA signature: NOKEY, key ID 897da07a warning: rpmdevtools-5.3-1.fc6: Header V3 DSA signature: NOKEY, key ID 1ac70ce6 error: can't create transaction lock on /var/lib/rpm/__db.000 <snip>
I'm having trouble seeing where this is a mock versus a yum bug. At the point of the failure, we're running yum and we've passed in - --installroot= on the command line. Not sure what else mock can do.
I did try adding an _rpmlock_path to the macros that are setup by mock, but that was really grasping at straws, since I wasn't convinced that the macros are actually used. In any case adding the _rpmlock_macro to the rpmmacros file didn't effect the bug behavior.
Is there someplace in yum that you're setting up a transaction and are defaulting the installroot to '/'?
Clark
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Clark Williams wrote:
Seth,
This bug occurs on systems that don't have a /var/lib/rpm directory. The failure occurs while installing the chroot. Here's a snippet of a log of the failure:
<snip>
I hate replying to my own email, but...
David Smith just reminded me that there are some rpm issues where rpm cheerfully ignores any --root argument and attempts to grab a lock on /var/lib/rpm/db*. It's entirely possible that this issue is hitting one of those spots.
Clark
On Dec 19, 2006, at 8:59 AM, Clark Williams wrote:
Total download size: 103 M warning: mktemp-1.5-23.2.2: Header V3 DSA signature: NOKEY, key ID 897da07a warning: rpmdevtools-5.3-1.fc6: Header V3 DSA signature: NOKEY, key ID 1ac70ce6 error: can't create transaction lock on /var/lib/rpm/__db.000
<snip>
I'm having trouble seeing where this is a mock versus a yum bug. At the point of the failure, we're running yum and we've passed in
- --installroot= on the command line. Not sure what else mock can do.
Hi Clark, I remember this problem a while back although when it happened for me, the problem was that mock was not creating the /var/ lib/rpm/ directory inside the chroot (actually due to a change in the RPM rpm). This was patched in CVS, although I'm not sure it's been pushed out in any updates. Can you verify that this is trying to create files in /var/lib/rpm and not <chroot>/var/lib/rpm?
-Jeff
buildsys@lists.fedoraproject.org