Hmm. I can't quite wrap my head around this -- the upgrade fails because
the lam-with-gm RPM's say they require lam-oscar. Hmm.
What does lam-* expand to on your machine?
If you don't have Myrinet hardware, you can simply "rpm -e
lam-with-gm-oscar lam-with-gm-oscar-module" and avoid the issue.
Also, unless you've done the things to make your new image "correct" (see
previous posts on this list), I wouldn't push that image out again.
Instead, you can:
cp lam-* /home/someuser
cexec rpm -Uvh /home/someuser/lam-*
On Wed, 24 Sep 2003, Mark Leverentz wrote:
> Okay, so I got it to build the RPMS, and I got them installed on the head
> node. How do I get them installed on the client nodes (and do I even need to
> install them on the client nodes)? I though I could do something like this:
>
> chroot /var/lib/systemimager/... /bin/bash
> rpm -Uvh lam-*
> cpushimage ...
>
> but rpm is giving me these failed dependancies on the client image:
>
> error: failed dependencies:
> lam-oscar is needed by lam-with-gm-oscar-module-7.0-2
> lam-oscar is needed by lam-with-gm-oscar-7.0-2
>
> I assume the problem has to do with the fact that my previous lam
> installation was just built from source and installed in the /home/ tree
> on the head node where all the slaves could see it. It seems strange
> that these packages would depend on what would appear to be
> themselves...Do you know what the problem is here?
>
>
> On Wednesday September 24 2003 10:09 am, Jeff Squyres wrote:
> [snipped]
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Oscar-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-users
