Title: RE: [Oscar-devel] SuSE support is in trunk now
Hi Thomas:
 
Actually even though it built, when I tried to install, it did have some problems...

warning: group pvm does not exist - using root
chown: `pvm:pvm': invalid group
error: %post(pvm-3.4.5+6-1) scriptlet failed, exit status 1

I think it did install to completion though.  Looks like the command to create the user is not portable to SUSE - we need to make sure that the "pvm" group is created as well.  Maybe you can take a look at what the command is like from the official SUSE PVM RPM.
 
Cheers,
 
Bernard


From: Thomas Naughton [mailto:[EMAIL PROTECTED]
Sent: Fri 02/06/2006 22:16
To: Bernard Li
Cc: Thomas Naughton; Erich Focht; [email protected]
Subject: RE: [Oscar-devel] SuSE support is in trunk now

Cool, thanks.
--tjn

   _________________________________________________________________________
    Thomas Naughton                                      [EMAIL PROTECTED]
    Research Associate                                   (865) 576-4184


On Fri, 2 Jun 2006, Bernard Li wrote:

> Hi Thomas:
>
> I don't think there's a problem - I was able to rebuild the version before the latest - I'll rebuild the latest tonight and check it in.
>
> Cheers,
>
> Bernard
>
> ________________________________
>
> From: [EMAIL PROTECTED] on behalf of Thomas Naughton
> Sent: Fri 02/06/2006 18:54
> To: Erich Focht
> Cc: [email protected]
> Subject: Re: [Oscar-devel] SuSE support is in trunk now
>
>
>
>
> On Wed, 31 May 2006, Erich Focht wrote:
>
>> as experimental. The PVM package is missing so far, lam, mpich are in.
>> OpenMPI  is being built, if it finishes without failure, I'll check it
>> in, too.
>
> Erich, is there a problem with the PVM package on SuSE or is it simply a
> time issue?
>
> --tjn
>
>  _________________________________________________________________________
>   Thomas Naughton                                      [EMAIL PROTECTED]
>   Research Associate                                   (865) 576-4184
>
>
> On Wed, 31 May 2006, Erich Focht wrote:
>
>> Hi,
>>
>> as questions on SUSE kept popping up, I focused a few hours on this and, well,
>> looks like the new infrastructure really makes it easy to port to new
>> distros. And I didn't think it's a good idea to continue with the suse-seneca
>> repository, that one is based on an old version of the infrastructure.
>>
>> SUSE support is now in trunk. It is maybe not perfect and should be regarded
>> as experimental. The PVM package is missing so far, lam, mpich are in. OpenMPI
>> is being built, if it finishes without failure, I'll check it in, too.
>>
>> I took Bernard's rpmlist file and stripped it a bit, also I took atftp-server
>> from the suse-seneca repository. A big help was that the OS_Detect stuff was
>> correct now. Many of the prereqs RPMs are provided by SUSE, so there was no
>> need to rebuild them. A few of the RPMs needed to be changed slightly to build
>> on SUSE. For perl-Qt and bittorrent I added compatibility RPMs (with only
>> depends and provides, almost no content), such that we can use the RPMs
>> provided by SUSE, again. Ganglia needed some heavy changes in the install and
>> init.d scripts, but works fine now.
>>
>> I didn't test the deployment and systemconfigurator call. Expect to find
>> problems in that area...
>>
>> Sorry if this comes a bit unexpected and unplanned, for me suse support means
>> that I can do a lot more development on my laptop than before. I think this
>> can well remain experimental for OSCAR 5.0, but its presence in trunk should
>> ease the development a lot.
>>
>> Regards,
>> Erich
>>
>>
>>
>> _______________________________________________
>> Oscar-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/oscar-devel
>>
>
>
> _______________________________________________
> Oscar-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oscar-devel
>
>
>

_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to