[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: error: unrecognized db option: "db3" ignored.



On Wed, Jan 09, 2002 at 05:01:35PM +0000, John P. Looney wrote:
> On Wed, Jan 09, 2002 at 11:34:20AM -0500, Jeff Johnson mentioned:
> > On Wed, Jan 09, 2002 at 04:29:01PM +0000, John P. Looney wrote:
> > >  This has been done, and that's how I was able to do the install of
> > > various packages, RPM included. However, once all the packages are
> > > installed, rpm doesn't work inside the chrooted environment, as it doesn't
> > > seem to understand the RPM db3 formatted database.
> > What does rpm --showrc say when run in the chroot?
> 
>  Rather less than when run in the full OS...
> 
> > You're gonna need /usr/lib/rpm/macros and other configuration in the chroot.
> 
>  I had a quick look, and it seemed that the chroot rpm installation was
> considerably smaller than I thought. Macros and rpmrc were not there. A
> reinstall fixed it.
> 
>  Yeah! Thanks for pointing me in the right direction.
> 
> > You might also look at /usr/lib/rpm/trpm. I run that script daily while
> > testing rpm installs into a chroot.
> 
>  How does one use this ? "trpm -Uvh package.rpm --root /tmp/chroot" ?

-2) Make a top level directory someplace, to play in, and copy trpm into
that directory.

-1) Make sure that you have sudo access.

0) Mount a pile of rpms somewhere. I conventionally use /X.Y/RPMS, where
X.Y candidates are (Red Hat) 5.2 6.2 7.0 7.1 ...

1) Eyeball the package glob expression precursors that look like
	min0glob="
	basesystem-
	bash-[12]
	filesystem-
	glibc-common-
	glibc-2
	ldconfig-
	libtermcap-2
	mktemp-
	setup-
	termcap-
	"
These are handcrafted to Do The Right Thing when presented with 5.2/6.2/7.0/...
package piles. Feel free to change to whatever, 'tain't hard.

2) Generate package manifests and rpm configuration, something like
	./trpm 7.2 config manifest
Examine the generated package manifests, they look like foo-X.Y-arch.
Ditto rpm configuration, rpmrc-X.Y. Feel free to change to whatever,
'tain't hard.

3) Install in a local ./X.Y chroot
	./trpm 7.2 min0 --initdb -Uvv

4) Test the chroot install
	./trpm 7.2 min0 chroot

5) Try a bigger test:
	sudo rm -rf 7.2
	./trpm 7.2 build --initdb -Uvv
	./trpm 7.2 chroot
	(you should be able to compile and debug a C program here)

6) Diddle the toy trpm script to taste and be happy.

73 de Jeff

-- 
Jeff Johnson	ARS N3NPQ
jbj@jbj.org	(jbj@redhat.com)
Chapel Hill, NC





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index] []