RE: RedHat 6.X build environment on pinstripe machine?

[Gregory Leblanc <GLeblanc cu-portland edu>]

> -----Original Message-----
> From: Jeff Johnson [mailto:jbj@JBJ.ORG]
> > > 
> > > You can do it by running rpm-3.0.[56] on pinstripe. You'll 
> > > need to convert
> > > to a db1 format database, and then install rpm-3.0.6. There's 
> > > one gotcha
> > > that I'm aware of, building rpm-3.0.6 on a pinstripe box, 
> see bugzilla
> > > #16972 for needed patch and details. Installing rpm-3.0.6 
> > > built on a Red Hat
> > > 6.2 box works fine AFAIK (I've done it), the problem is an 
> > > incompatible
> > > change to the libio interface in glibc-2.1.93 that I've 
> not backported
> > > to rpm-3.0.6.
> > 
> > Should I be able to do the database conversion following 
> the instructions
> > that you sent out 8/26/2000 that cover 4 different RPM 3/4 
> interaction
> > scenarios?  I just tried to do that, but it doesn't seem to 
> create the db v1
> > files, and just moves the db v3 files into another 
> directory.  The only
> > error message that I get when running 'rpm --rebuilddb --dbapi 3
> > --rebuilddbapi 1' is that it cannot remove 
> /var/lib/rpmrebuild.processnumber
> > (or some similar filename).  Is there an easy way to figure 
> out what's going
> > wrong here?  I can capture verbose output, if that will 
> help (let me know
> > how many v's to use).
> 
> Yes, conversion can be done doing a --rebuilddb with 
> appropriate values
> for --dbapi and --rebuilddbapi for before and after db flavors.
> 
> You can try verbose mode (-vv is the maximum verbosity). 
> However, simply
> doing
> 	cd /var/lib
> 	ls -al rpm*
> will usually tell you what the problem is, usually files left in some
> directory or other. The only files that are important are 
> Packages (for db3)
> and packages.rpm (for db1), the other files will be regenerated by a
> --rebuilddb.

I never get a packages.rpm generated from running the command above.  It
moves /var/lib/rpm to /var/lib/rpmrebuilddb.psnumber, but fails to actually
do anything.  Hmm, strange, it looks like it's not generating a v1 dbapi
database, for some reason.  

D: rebuilding database /var/lib/rpm into /var/lib/rpmrebuilddb.6767
D: creating directory /var/lib/rpmrebuilddb.6767
D: opening old database with dbapi 3
D: opening db index       /var/lib/rpm/Packages rdonly mode=0x0
D: locked  db index       /var/lib/rpm/Packages
D: opening new database with dbapi 1
D: opening db index       /var/lib/rpmrebuilddb.6767/Packages create
mode=0x42
D: locked  db index       /var/lib/rpmrebuilddb.6767/Packages

Any thoughts on why it's doing that?

> > On a similar note (now that I've thought about a better way 
> to phrase my
> > original question), will the packages built on Pinstripe 
> with RPM v3.0.6
> > work on my stock RH 6.x boxes?
> 
> Depends on what "work" and "stock RH 6.x" mean. The only 
> change in rpm-3.0.5
> and later is the addition of rpmlib feature dependencies to explicitly
> track incompatibilities introduced in rpm-3.0.4 and earlier.

ok, so that wasn't clear.  They're RH 6.x machines, with the latest updates
installed.  My recent build machine is RH 6.2, and I've been building all of
the packages from there.  "Work" would be that the binary RPMs install, and
actually work.  Thanks again,
	Greg