Bug 447283

Summary:	rpm --root does not behave as expected
Product:	[Fedora] Fedora	Reporter:	Rob Lazzurs <rob>
Component:	rpm	Assignee:	Panu Matilainen <pmatilai>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	7	CC:	jnovy, pnasrat
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-06-17 03:08:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Rob Lazzurs 2008-05-19 10:15:40 UTC

Description of problem:

Today when running rpm --root on an chroot environment we keep we had the
unexpected behavior of the rpm db having references outside it's directory
structure. eg running the command below outside of the chroot produced the
output below once chroot'ed into the environment.

rpm --force  --root /homes/sys/adm/masterOS/dist/FC/7_x86_64/desktop/ -ivh
/homes/bah/tools/rpm/jdk-6u1-linux-amd64.rpm

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

RPM version 4.4.2.2

How reproducible:

Everytime

Steps to Reproduce:
1. Run the above rpm command on a chroot F7 environment from an F7 environment
2. Chroot into the F7 environment
3. run rpmquery
  
Actual results:

rpmdb: /homes/sys/adm/masterOS/dist/FC/7_x86_64/desktop/var/lib/rpm/Filemd5s: No
such file or directory

Expected results:


Additional info:

Comment 1 Bug Zapper 2008-06-17 03:08:12 UTC

Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 is no longer maintained, which means that it will not 
receive any further security or bug fix updates. As a result we 
are closing this bug. 

If you can reproduce this bug against a currently maintained version 
of Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.