On Thu, 2010-09-30 at 17:41 +0200, Alain Leufroy wrote:
> > Hi Adam,
> >
> > I've worked a little bit on this problem with André.
> >
> > We see that the problem is about the fact that the Salome python modules
> > site in the ``salome/`` directory whereas it is not interpreted as a
> > package by
> Hi Adam,
>
> I've worked a little bit on this problem with André.
>
> We see that the problem is about the fact that the Salome python modules
> site in the ``salome/`` directory whereas it is not interpreted as a
> package by python (``salome/__init__.py`` is missing) and all python code
> impo
tags 597739 pending
thanks
I've fixed this problem by creating a salomeloader script which sets
PYTHONPATH and then calls the old salomeloader python file under a new
name. The fix is in the alioth git repository.
This does not fix your other problem with runSalome, which is now bug
597885.
Tha
On Sat, 2010-09-25 at 14:58 -0500, M. wrote:
> Hello again,
>
> ~$ dpkg -S /usr/bin/salomeloader
> salome: /usr/bin/salomeloader
Ah yes, you're right, I moved that into /usr/bin for -10, and back
to /usr/lib/salome/bin for -11.
I have a solution, and should be able to push it to the alioth git
r
On Wed, 2010-09-29 at 12:41 -0400, Adam C Powell IV wrote:
> Dear Alain,
>
> Thanks very much for the information on this bug.
>
> I think that since salomeloader is a script,
I'm wrong, it's not really a script...
> maybe we can patch that
> script to set the PYTHONPATH variable. That way we
Dear Alain,
Thanks very much for the information on this bug.
I think that since salomeloader is a script, maybe we can patch that
script to set the PYTHONPATH variable. That way we don't htave to have
too many files in dist-packages, and a non-expert user can run it.
What do you think?
-Adam
Hi Adam,
I've worked a little bit on this problem with André.
We see that the problem is about the fact that the Salome python modules site in
the ``salome/`` directory whereas it is not interpreted as a package by python
(``salome/__init__.py`` is missing) and all python code import these modul
Hello again,
~$ dpkg -S /usr/bin/salomeloader
salome: /usr/bin/salomeloader
And that's it. Is there anything else that I can do to help?
Thank you
2010/9/23 Adam C Powell IV
> clone 597739 -1
> title -1 runSalome failed to narrow the root naming context
> thanks
>
> Hello,
>
> It sounds like
retitle 597885 runSalome "failed to narrow the root naming context"
thanks
Sorry, error in the command name.
-Adam
On Thu, 2010-09-23 at 16:07 -0400, Adam C Powell IV wrote:
> clone 597739 -1
> title -1 runSalome failed to narrow the root naming context
> thanks
>
> Hello,
>
> It sounds like y
clone 597739 -1
title -1 runSalome failed to narrow the root naming context
thanks
Hello,
It sounds like you've found another bug. I'm afraid I don't know
Salomé's CORBA system well enough to recognize it right away, but can
confirm that the package starts correctly on my system. Perhaps it is
2010/9/22 Adam C Powell IV
> severity 597739 normal
> thanks
>
> Thank you for your report. The program should be started with the
> command runSalome not salomeloader, so the package is usable.
>
>
Ok, thank you. When I tried to run using runSalome I hit this error:
:~$ runSal
severity 597739 normal
thanks
Thank you for your report. The program should be started with the
command runSalome not salomeloader, so the package is usable.
Also, 5.1.3-9 and newer versions should not have /usr/bin/salomeloader
but /usr/lib/salome/bin/salomeloader. Please check the location of
Package: salome
Version: 5.1.3-10
Severity: grave
Justification: renders package unusable
When trying to start the program with the command
salomeloader
The following error is returned:
:~$ salomeloader
Traceback (most recent call last):
File "/usr/bin/salomeloader", line 20, in
impor
13 matches
Mail list logo
