Bug#637609: closed by Anton Gladky gladky.an...@gmail.com (Bug#637397: fixed in paraview 3.10.1-2)

2011-08-21 Thread Mathieu Malaterre
I would like to add that the CMake/* files belongs to the paraview-dev package now: /usr/lib/paraview/CMake/FindMySQL.cmake /usr/lib/paraview/CMake/FindPythonLibs.cmake /usr/lib/paraview/CMake/FindTCL.cmake /usr/lib/paraview/CMake/ParaViewBranding.cmake

Bug#637609: closed by Anton Gladky gladky.an...@gmail.com (Bug#637397: fixed in paraview 3.10.1-2)

2011-08-18 Thread Anton Gladky
Python stuff of Paraview has been moved to paraview-python binary. And this binary is conflicting with python-vtk. On 8/18/11, Steve M. Robbins st...@sumost.ca wrote: On Wed, Aug 17, 2011 at 07:09:09PM +, Debian Bug Tracking System wrote: This is an automatic notification regarding your

Bug#637609: closed by Anton Gladky gladky.an...@gmail.com (Bug#637397: fixed in paraview 3.10.1-2)

2011-08-18 Thread Mathieu Malaterre
[Top posting] I believe that this will bites us later on. gdcm can build paraview plugins (therefore needs paraview-dev), and at the same time can build gdcm-vtk-python plugins (therefore need vtk-python). Ideally paraview* packages should not install none of the vtk related stuff. I would really

Bug#637609: closed by Anton Gladky gladky.an...@gmail.com (Bug#637397: fixed in paraview 3.10.1-2)

2011-08-17 Thread Steve M. Robbins
On Wed, Aug 17, 2011 at 07:09:09PM +, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the python-vtk,paraview package: #637397: Undeclared conflict with python-vtk * [27f6ded] Split paraview into paraview and