[WBEL-devel] Re: WBEL at breakage

[Paul Iadonisi]

On Tue, 2003-12-30 at 19:24, John Morris wrote:
> On Tue, 30 Dec 2003, Paul Iadonisi wrote:

[snip]

> > For some strange reason, I can't rebuild the at rpm, now.  Getting a
> > failure on 4 of the tests on both my custom build and on RHEL3.  But the
> > atd binary is built by that point and it does reference
> > /usr/sbin/sendmail, so I think putting /usr/sbin does fix the above
> > stated problem.
> 
> Seems to depend on the version of glibc whether you get that error.  Try 
> upgrading your build machine to the same version as WBEL3/RHEL3 and it 
> should build correctly.

  Nope, and I'm stumped.  Here's what I've done (going back many weeks)
and why the fact that it doesn't work now makes little sense.

1) Installed a Taroon Beta system
2) Went through all the gyrations to build a complete set of rpms,
upgrading and rebuilding rpms on my build system as required.  These
rpms were all built as the root user.
3) With the help of some docs on whiteboxlinux.org, built some
installable isos with my binary rpms.
4) Ran through a successful anaconda install of my fresh isos
5) Copied my newly installed system to an lvm volume (to be used as a
chrooted system).
6) Installed the official RHEL3 for comparison purposes
7) Chrooted into my custom built system
8) Rebuilt all rpms as a non-root user with a small number of failures
in my chrooted system
9) Fixed the build of all failed rpms, mostly due to /usr/kerberos/bin
not being in my path.  mod_perl apparently won't rebuild with the
version of the apache package shipped with RHEL3 -- you need the one
that came with the beta.

  Now, you'll note that I didn't install any of the above resulting
binary rpms, yet.  I have a log and a binary rpm that proves to me that
the at rpm built successfully in this environment.  But now, that very
same src rpm just won't build.  I've tried it on RHEL3 (original glibc
shipped), WBEL3 (original glibc), WBEL3 (updated glibc), and my own
custom build.  No dice.  The only thing I haven't tried is building it
on taroon beta again, but I don't have a spare system to try this on at
the moment.

  I'm not really in *great* need of fixing this, as it can always be
built with the '--without check' option, but it just bugs me that this
worked before and it doesn't now.

  My biggest gripe about this whole thing is how utterly useless the
test results are.  It seems impossible to get any useful information
about which 4 tests are failing out of the 3000+, what the input was,
what the output was, etc.
-- 
-Paul Iadonisi
 Senior System Administrator
 Red Hat Certified Engineer / Local Linux Lobbyist
 Ever see a penguin fly?  --  Try Linux.
 GPL all the way: Sell services, don't lease secrets