When building the client image, we get two lists of RPMs: the "oscarsample" RPM list for the distro and the list of RPMs from the packages. Previously, we just used all those RPMs to build the image, and that was that.
Recally, however, that per the Tuesday phone call, I've removed "libaio" from LAM's RPM list. So now the install-both-RPM-lists mechanism no longer works -- because the LAM RPM dependencies fail because libaio is missing.
But wait -- DepMan should have caught this, right?
Yikes! This is a place where DepMan integration was skipped. So I added it. Buuutttt... not really. Here's the problem:
update-rpms checks against both the cache and the installed system to come up with a list of RPMs that need to be installed. Hence, you get a list of RPMs suitable passing to "rpm -ivh ...".
But that's no good because we're checking against the root filesystem, and therefore we don't get a "pure" list of RPMs to install into an image (i.e., there's lots of RPMs missing in the output because they're already installed on the server).
There's a chroot() function for DepMan so that you can check against images. But there's no image yet, so this is useless. :-\
Anyone got any ideas here?
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
