The SRPM (lam-oscar-7.1.2-5.src.rpm) is the latest one which I checked
in last night.  Unfortunately I did not have the time to test it prior
to checking in (I did test 7.1.2-4 but found another bug, which I have
subsequently fixed and checked in as 7.1.2-5).

Anyways, if you are having problems with LAM/MPI, just do not install it
for now - I will sanity check it tonight and report back.

I did build the LAM/MPI RPMs in distro/rhel4-i386 on RHEL4u3, I'm not
sure if that will work on RHEL4 (gold) - perhaps what you can try is
rebuild the source RPM and use that instead of the one from the
repository and see if it goes.

Cheers,

Bernard 

> -----Original Message-----
> From: Erich Focht [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, April 05, 2006 13:31
> To: [EMAIL PROTECTED]
> Cc: Bernard Li; [email protected]
> Subject: Re: [Oscar-devel] Test for trunk on RHEL AS4 X86
> 
> Hi DongInn,
> 
> in CentOS I have libaio and libaio-devel in my repository. In 
> your log I can
> see that libaio and libaio-devel were selected for 
> installation. Why it
> doesn't install I cannot tell you.
> 
> There are two problematic parts in your setup: you are using original
> RHEL4-AS, unpatched. I started playing with RHEL4 after U1, 
> didn't dare
> before. Really, what you use is old and might have bugs and problems.
> The other thing is that there was quite some change in lam 
> with the update to
> 7.1.2 I see a wild mix of revisions, that's not nice, as 
> we'll have to rebuild
> with the latest revision anyway. Bernard can maybe rebuild the latest
> one... But I see nothing special in the "requires".
> 
> Anyway: RHEL4U2 has libaio-0.3.103 instead of 0.3.102 which I 
> see in your
> logs. So there was some reason to update that package...
> 
> Yume is installed for you right now, right? Then try please:
> 
> yume -v --prepare
> (this will recreate your pool metadata)
> and
> yume -v -y install lam-oscar libaio
> 
> If it doesn't work, try installing only libaio.
> 
> Also try checking the --requires from lam-oscar and the 
> --provides from
> libaio. Last resort: check the XML data in the distro 
> repository in the file
> repodata/primary.xml.gz . Do you find for libaio the provide 
> "libaio.so.1"?
> You should...
> 
> Regards,
> Erich
> 
> On Wednesday 05 April 2006 20:09, [EMAIL PROTECTED] wrote:
> > Hi,
> > 
> > I have tested r4510 and got the same error for systemimager-server.
> > As Bernard suggested, I tried to run "createrepo
> > /tftpboot/oscar/rhel-4-i386" and it seemed to work fine 
> until oscar_wizard
> > shows up.
> > I tried to test the step 3 "Install OSCAR Server 
> Packages..." and got a
> > dependency error and it failed.
> > 
> > --> Running transaction check
> > --> Processing Dependency: libaio.so.1 for package: lam-oscar
> > --> Processing Dependency: tk for package: torque-gui
> > --> Restarting Dependency Resolution with new changes.
> > --> Populating transaction set with selected packages. Please wait.
> > ---> Downloading header for tk to pack into transaction set.
> > tk-8.4.7-2.i386.rpm       100% |=========================|  
> 25 kB    00:00
> > ---> Package tk.i386 0:8.4.7-2 set to be updated
> > --> Running transaction check
> > --> Processing Dependency: libaio.so.1 for package: lam-oscar
> > --> Finished Dependency Resolution
> > Error: Missing Dependency: libaio.so.1 is needed by package 
> lam-oscar
> > --> Step 3: Failed to properly install OSCAR server; please 
> check the logs
> > --> Update Wizard Env (as needed)
> > 
> > I think lam package needed to libaio-devel installed 
> before. I think it is
> > not installed. Is that because somehow libaio-devel was not 
> installed?
> > [EMAIL PROTECTED] scripts]# rpm -qa | grep libaio
> > 
> > 
> > I also tried to re-run the only step 3 with 
> "OSCAR_VERBOSE=5" and then got
> > its typescript. I attached it.
> > 
> > -- DongInn
> > 
> > > Hi Erich:
> > >
> > > I was just testing r4506 and the cache was indeed not 
> generated correctly
> > > for /tftpboot/oscar/rhel-4-i386, after I ran "createrepo
> > > /tftpboot/oscar/rhel-4-i386", SystemImager and all other RPMs were
> > > installed properly (this was a fresh installation, BTW).
> > >
> > > We _really_ need to investigate how we can get error code 
> from yum - if an
> > > installation does not succeed, it should stop right at 
> its tracks and
> > > bail, instead of continuing on.
> > >
> > > Thanks,
> > >
> > > Bernard
> > >
> > > ________________________________
> > >
> > > From: [EMAIL PROTECTED] on behalf 
> of Erich Focht
> > > Sent: Tue 04/04/2006 14:18
> > > To: [EMAIL PROTECTED]
> > > Cc: [email protected]
> > > Subject: Re: [Oscar-devel] Test for trunk on RHEL AS4 X86
> > >
> > >
> > >
> > >> Anyway the string
> > >> Compatlist: rhel4-1 rhel4 rhel-1 rhel
> > >> worries me. This should actually look differently, more 
> like rhel4-i386
> > >> rhel4,
> > >> etc... I'll have a look into generic-setup, it is now called with
> > >> different
> > >> arguments than before. I'll report back.
> > >
> > > There was a bug in generic-setup, the --arch argument 
> wasn't processed
> > > correctly. I fixed it in trunk. Please try again.
> > >
> > > Thanks,
> > > Erich
> 
> 
> 


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to