dorsal team mailing list archive

[Benjamin Kehlet <benjamik@xxxxxxxxx>]

2011/10/31 Harish Narayanan <harish@xxxxxxxxx>:
> On 10/31/11 11:55 AM, Fredrik Heffer Valdmanis wrote:
>> 2011/10/31 Harish Narayanan <harish@xxxxxxxxx <mailto:harish@xxxxxxxxx>>
>>
>>     On 10/31/11 11:36 AM, Fredrik Heffer Valdmanis wrote:
>>     > OK, thanks!
>>     >
>>     > Another quick question: For small patches and improvements, should I
>>     > file a bug report, make a merge proposal or just mail the list?
>>     The case
>>     > right now is that the package "ptscotch" must be added to the list of
>>     > packages in petsc.package in order for PETSc to compile on my machine.
>>     > In addition, the old slepc.patch must be remade in a version for SLEPc
>>     > 3.2, in order for repeated builds with Dorsal to succeed.
>>     >
>>     > These are rather small changes, so I figured either a bug report and
>>     > merge proposal was a bit over the top.
>>
>>     cc: The mailing list so that others may chime in.
>>
>>     Do you want me to replace scotch with ptscotch, or add ptscotch to the
>>     list?
>>
>>
>> ptscotch must be added to the list, before scotch. Else, PETSc fails
>> during configure. Am I the only one having this problem? I'm on Ubuntu
>> 11.04.
>>
>>
>>     And I removed the patch for slepc 3.2 because I don't think it is
>>     necessary any more. Also, what platform are you on?
>>
>>
>> SLEPc still complains that files from an existing install is present if
>> you rerun Dorsal on top of a previous install without patching.
>> Shouldn't the patch still be there? I have made a new slepc.patch for
>> 3.2, it is included in the attached patchfile together with the ptscotch
>> fix.
>>
>>
>>     For the future, either of those avenues are useful:
>>
>>      * If you know how to fix the problem, mailing a patch to the list or
>>     merge proposal is the easiest for me to deal with.
>>      * If you don't, file a bug report. As tiny as it may seem, it better
>>     ensures that your problem not to be overlooked.
>>
>>
>> All right :)
>
> I have incorporated your patch. And I still cannot see why your e-mails
> are not making it through to the list. There are no obvious buttons on
> launchpad that I can push. (Perhaps try from a different e-mail address?)

I don't know if this helps, but it may be worth a try. The uio mail
system is very strict about sender adresses and overwrites it to your
official address without noticing you (This applies of course only  if
you're using the SMTP server our webmail at UiO). I had some trouble
with mailing lists a while ago, when then sender address was changed
from (in my case) "benjamik@xxxxxxxxxx" to
"benjamik@xxxxxxxxxxxxxxxxxxxxx". This was pre-Launchpad, but _if_
Launchpad filters out messages from addresses not registered, it may
be solved by registering the xxx@xxxxxxxxxxxxxxxxxxxxx address in
Launchpad.

Benjamin

>
> Thanks,
> Harish
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dorsal
> Post to     : dorsal@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dorsal
> More help   : https://help.launchpad.net/ListHelp
>