[Pkg-scicomp-devel] paraview status

Ondrej Certik ondrej at certik.cz
Mon Feb 18 11:01:05 UTC 2008


On Feb 18, 2008 7:45 AM, Christophe Prud'homme <prudhomm at debian.org> wrote:
> All,
>
> here is the status of paraview
>
>  o  builds with shared libs support (weights 34M total)
>  o incorporate all libs and bins (perhaps some bins should be removed) now
>  o builds faultlessly on my i386
>
> what remains to be done
>   o manpages for bins (dummy pages could do as a first step except for
> paraview, no ?)
>   o make the python interface work

Excellent work with the shared libraries. It builds both on i386 and
amd64 in pbuilder. However, during install:

$ wajig install paraview_3.2.1-1_amd64.deb
Selecting previously deselected package paraview.
(Reading database ... 181424 files and directories currently installed.)
Unpacking paraview (from paraview_3.2.1-1_amd64.deb) ...
dpkg: error processing paraview_3.2.1-1_amd64.deb (--install):
 trying to overwrite `/usr/bin/vtkWrapPythonInit', which is also in
package python-vtk
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
 paraview_3.2.1-1_amd64.deb


So we should do either of these:

* should not ship /usr/bin/vtkWrapPythonInit
* rename it to something else
* conflict with python-vtk

Otherwise it seems to work fine both on i386 and amd64 except the
python interface. The i386 package is in my repository:

http://debian.certik.cz/

Yes, let's create dummy man pages, that's ok. The python-vtk issue is
also minor - just removing the python-vtk package fixes this. So now
we need to concentrate on the python issue.

One thing that needs  to work is

1) starting paraview
2) Tools -> Python Shell
3) it should print

Python 2.5 (release25-maint, Dec  9 2006, 14:12:17)
[GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)] on linux2
>>>
>>>

but our Debian package prints

Python 2.5.2a0 (r251:54863, Feb 10 2008, 01:49:57)
[GCC 4.2.3 (Debian 4.2.3-1)] on linux2
>>>
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named paraview
>>>


When this works, we are fine. Another way to test it is:

$ bin/pvpython
Python 2.5 (release25-maint, Dec  9 2006, 14:12:17)
[GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import paraview
>>>


vs. our package:

$ pvpython
Python 2.5.2a0 (r251:54863, Feb 10 2008, 01:49:57)
[GCC 4.2.3 (Debian 4.2.3-1)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import paraview
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named paraview
>>>


But we are getting close, even now the package is usable. BTW, did you
try the MPI support? Do you have some easy usecase? Let's write it to
README.Debian? I would like to try it (I mean we should try that it
works), but I didn't yet find time to figure this out how to use it.

Ondrej



More information about the Pkg-scicomp-devel mailing list