Bug 129463

Description of problem:

I face a problem with rpm 4.3.x in that the transaction locking does
try to lock the file /var/lock/rpm/transaction regardless of the
dbpath or any prefix. In fact rpmlock_new() from rpm/lib/rpmlock.c
takes a "rootdir" as an argument, however RPMLOCK_FILE is not
relocated to it.

I guess the transaction file should relocate to the rpm database
directory, otherwise you could still face race conditions on, for
example, a diskless client, when installing rpms from the server and
from the client at the same time. 
Version-Release number of selected component (if applicable):


How reproducible:

use rpm without root priviliges and relocate to a directory where you
have write permissions

Steps to Reproduce:
1.
2.
3.
  
Actual results:

fails to get a lock on /var/lock/rpm/transaction


Expected results:

the file transaction should be relocated to where the rpm database is
relocated to.

Additional info:

please let me know if you need more info