No, I did not. The way I read the docs, install root specifies an alternative root to which packages are installed. The RPM database is not mentioned. Does changing the installroot change where the rpm database is expected? Thanks > -----Original Message----- > From: yum-bounces@xxxxxxxxxxxxxxxxxxxx > [mailto:yum-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of seth vidal > Sent: Monday, July 23, 2007 7:40 PM > To: Yellowdog Updater, Modified > Subject: Re: old code questions > > On Mon, 2007-07-23 at 17:14 -0700, Gallie, Keith wrote: > > I've been hacking on yum 2.0.8 and rpm for an internal > enterprise wide > > solution. I've got just about everything figured out except > how to get > > yum to look at an RPM database other than the default /var/lib/rpm. > > I've spent most of the day on the debugger and haven't > quite got there. > > > > Trying to figure it out I get > > > > Downloading Packages > > Getting try_4-3.0-9.x86_64.rpm > > Getting try_3-3.0-1.x86_64.rpm > > Getting try_1-4.2-1.x86_64.rpm > > Running test transaction: > > error: cannot open Basenames index using db3 - No such file or > > directory > > (2) > > Segmentation fault > > > > This could be due to our screwy python install as the segv > seem to be > > during the return from a callback class RPMInstallCallback > after a pass. > > did you try with --installroot=/some/path in 2.0.8? > > -sv > > > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxxxxx > https://lists.dulug.duke.edu/mailman/listinfo/yum > > > _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxxxxx https://lists.dulug.duke.edu/mailman/listinfo/yum
