Bug 33257 – only root can read rpm database after update to rpm 4.0.2

Bug 33257 - only root can read rpm database after update to rpm 4.0.2

Summary:	only root can read rpm database after update to rpm 4.0.2

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	rpm (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	i386 Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Jeff Johnson
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-03-26 11:05 EST by Bobby de Vos
Modified:	2007-04-18 12:32 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-03-26 11:05:09 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Bobby de Vos 2001-03-26 11:05:06 EST

From Bugzilla Helper:
User-Agent: Mozilla/4.73 [en] (X11; U; Linux 2.2.16-3 i686)


Upgraded to
  rpm-4.0.2-6x
  rpm-build-4.0.2-6x
  rpm-devel-4.0.2-6x
  rpm-python-4.0.2-6x
  db3-3.1.17-4.6x
  popt-1.6.2-6x

As root, I could run
   rpm -q rpm
but not as a user. I fixed the problem by running
    chmod 644  /var/lib/rpm/*


Reproducible: Always
Steps to Reproduce:
1. rpm -ivh db3-3.1.17-4.6x.i386.rpm
2. rpm -Fvh rpm-*4.0.2*
3. rpm -Fvh popt-1.6.2-6x.i386.rpm 
4. rpm --rebuilddb
5. rpm -q rpm # as a user fails
	

Actual Results:  error: cannot open Packages index using db3 - Permission
denied (13)


Expected Results:  rpm-4.0.2-6x

Comment 1 Jeff Johnson 2001-03-26 11:15:00 EST

Check root's umask setting,  rpm does not do anything special with directory or
file permissions, other than to sugeest default values of 755 and 644, but those
values are modified by the umask in operation at the time.

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