From: David N. Lombard [mailto:[EMAIL PROTECTED]
Sent: Sat 19/02/2005 6:55 AM
To: Bernard Li
Cc: Oscar-devel List
Subject: Re: [Oscar-devel] SIS config.xml
Bernard Li wrote:
> Hi Dave:
>
> Did you get
my last email? The updated oscarinstall.log has the
> following
line:
>
> Copying
/opt/oscar/packages/sis/RPMS/perl-AppConfig-1.52-4.noarch.rpm to
>
/tftpboot/rpm
Bernard,
I've seen enough bits of your installations
to be satisfied that the
*original* config.xml was correct.
If you
recall, we had some extensive discussions about <rpmlist>, and
how it
should *only* be used to specify RPMs that are a part of the
opkg, or are
needed to satisfy *unspecified* dependencies.
The very error message you
posted proved the dependency was known--I'm
guessing perl-AppConfig was not
in /tftpboot/rpm when you ran that test.
Q: Why don't I want config.xml
to contain perl-AppConfig?
A: Because perl-AppConfig is specified as a
dependency by the
appropriate SIS RPMs, therefore, update-rpms should use it
to resolve
the those dependencies iff perl-AppConfig is in /tftpboot/rpm and
no
other issues block installing the RPM. If update-rpms doesn't
properly
resolve the dependency, *that* error--the real underlying problem
on
fc2--needs to be addressed.
Fair enough?
So, please
do this:
1) Get your system to a clean starting state--I'm guessing this
is
driving your recent kickstart urge.
2) Make sure perl-AppConfig is
*not* in config.xml, i.e., remove your
change.
3) Start the script
command
4) export DEBUG_OSCAR_WIZARD=y
5) ./install_cluster
<dev>
6) Watch the image build work. If it doesn't, send me
the typescript
file, as it will show:
a) that config.xml did not contain
perl-AppConfig
b) that perl-AppConfig was copied to /tftpboot/rpm, since it's
in
packages/sis/RPMS
c) why the image-build failed.
--
David
N. Lombard
Rossmoor, Orange County, CA
http://www.fourmilab.ch/cgi-bin/uncgi/Earth?imgsize=320&opt=-z&lat=33.8&ns=North&lon=118.08&ew=West&alt=7&img=learth.evif
