Bug 119783 - rpm --test returns "error: can't create transaction lock" when run without root privs
rpm --test returns "error: can't create transaction lock" when run without ro...
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Jeff Johnson
Mike McLean
: 120496 (view as bug list)
Depends On:
Blocks: FC2Target
  Show dependency treegraph
Reported: 2004-04-02 00:59 EST by Gregory Leblanc
Modified: 2007-11-30 17:10 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-04-07 19:49:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gregory Leblanc 2004-04-02 00:59:47 EST
Description of problem:
Running 'rpm --test -Uvh somepackage.rpm' as a non-root user now
returns "error: can't create transaction lock".  Prior versions did
not return an error.

Version-Release number of selected component (if applicable):

How reproducible:
Comment 1 Bill Nottingham 2004-04-05 23:38:16 EDT
Any SELinux error messages?
Comment 2 Gregory Leblanc 2004-04-06 01:35:09 EDT
In the logs, or on the console?  The console reports only the
transaction lock error.

From chatting with Jeff about this a bit, it seems that --test does
what it has always done, and it "works" doing that, despite this
error.  I haven't verified that personally, though it's on my list. 
If I understood correctly, he also said this was due to some internal
changes in RPM and not due to something else (though I did not ask
about SELinux).  
Comment 3 Miloslav Trmac 2004-04-06 13:05:22 EDT
This happens even with SELinux completely disabled 
(In particular, I have tried rpm -ev --test boost).
Comment 4 Jeff Johnson 2004-04-07 19:49:52 EDT
Fixed in rpm-4.3.1-0.2 when built.
Comment 5 Jeff Johnson 2004-04-09 10:01:11 EDT
*** Bug 120496 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.