Bug#637609: closed by Anton Gladky <gladky.anton at gmail.com> (Bug#637397: fixed in paraview 3.10.1-2)

[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
/usr/lib/paraview/CMake/ParaViewBrandingCPack.cmake
/usr/lib/paraview/CMake/ParaViewCPackOptions.cmake.in
/usr/lib/paraview/CMake/ParaViewMacros.cmake
/usr/lib/paraview/CMake/ParaViewPlugins.cmake
/usr/lib/paraview/CMake/ParaViewTargets-release.cmake
/usr/lib/paraview/CMake/ParaViewTargets.cmake
/usr/lib/paraview/CMake/ParaViewUse.cmake
/usr/lib/paraview/CMake/VTKVersionMacros.cmake
/usr/lib/paraview/CMake/branded_paraview_initializer.cxx.in
/usr/lib/paraview/CMake/branded_paraview_initializer.h.in
/usr/lib/paraview/CMake/branded_paraview_main.cxx.in
/usr/lib/paraview/CMake/branded_splash.png
/usr/lib/paraview/CMake/pq3DWidgetImplementation.cxx.in
/usr/lib/paraview/CMake/pq3DWidgetImplementation.h.in
/usr/lib/paraview/CMake/pqActionGroupImplementation.cxx.in
/usr/lib/paraview/CMake/pqActionGroupImplementation.h.in
/usr/lib/paraview/CMake/pqAutoStartImplementation.cxx.in
/usr/lib/paraview/CMake/pqAutoStartImplementation.h.in
/usr/lib/paraview/CMake/pqDisplayPanelDecoratorImplementation.cxx.in
/usr/lib/paraview/CMake/pqDisplayPanelDecoratorImplementation.h.in
/usr/lib/paraview/CMake/pqDisplayPanelImplementation.cxx.in
/usr/lib/paraview/CMake/pqDisplayPanelImplementation.h.in
/usr/lib/paraview/CMake/pqDockWindowImplementation.cxx.in
/usr/lib/paraview/CMake/pqDockWindowImplementation.h.in
/usr/lib/paraview/CMake/pqGraphLayoutStrategyImplementation.cxx.in
/usr/lib/paraview/CMake/pqGraphLayoutStrategyImplementation.h.in
/usr/lib/paraview/CMake/pqObjectPanelImplementation.cxx.in
/usr/lib/paraview/CMake/pqObjectPanelImplementation.h.in
/usr/lib/paraview/CMake/pqParaViewPlugin.cxx.in
/usr/lib/paraview/CMake/pqParaViewPlugin.h.in
/usr/lib/paraview/CMake/pqTreeLayoutStrategyImplementation.cxx.in
/usr/lib/paraview/CMake/pqTreeLayoutStrategyImplementation.h.in
/usr/lib/paraview/CMake/pqViewFrameActionGroupImplementation.cxx.in
/usr/lib/paraview/CMake/pqViewFrameActionGroupImplementation.h.in
/usr/lib/paraview/CMake/pqViewModuleImplementation.cxx.in
/usr/lib/paraview/CMake/pqViewModuleImplementation.h.in
/usr/lib/paraview/CMake/pqViewOptionsImplementation.cxx.in
/usr/lib/paraview/CMake/pqViewOptionsImplementation.h.in
/usr/lib/paraview/CMake/pv-forward.c.in
/usr/lib/paraview/CMake/vtkClientServer.cmake
/usr/lib/paraview/CMake/vtkExportKit.cmake
/usr/lib/paraview/CMake/vtkKit.cmake.in
/usr/lib/paraview/CMake/vtkMakeInstantiator.cmake
/usr/lib/paraview/CMake/vtkMakeInstantiator.cxx.in
/usr/lib/paraview/CMake/vtkMakeInstantiator.h.in
/usr/lib/paraview/CMake/vtkTclTkMacros.cmake
/usr/lib/paraview/CMake/vtkWrapClientServer.cmake
/usr/lib/paraview/CMake/vtkWrapClientServer.cxx.in
/usr/lib/paraview/CMake/vtkWrapJava.cmake
/usr/lib/paraview/CMake/vtkWrapPython.cmake
/usr/lib/paraview/CMake/vtkWrapTcl.cmake
/usr/lib/paraview/CMake/vtkWrapperInit.data.in
/usr/lib/paraview/ICETBuildSettings.cmake
/usr/lib/paraview/ICETLibraryDepends.cmake
/usr/lib/paraview/IceTConfig.cmake
/usr/lib/paraview/KWCommonBuildSettings.cmake
/usr/lib/paraview/KWCommonConfig.cmake
/usr/lib/paraview/KWCommonLibraryDepends.cmake

Thanks

On Thu, Aug 18, 2011 at 10:38 AM, Mathieu Malaterre
<mathieu.malaterre at gmail.com> wrote:
> [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 prefer if vtkWrap* were not installed within paraview* pacakge.
>
> 2cts
>
> On Thu, Aug 18, 2011 at 8:11 AM, Anton Gladky <gladky.anton at gmail.com> wrote:
>> 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 <steve at sumost.ca> wrote:
>>> On Wed, Aug 17, 2011 at 07:09:09PM +0000, 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 paraview-python.
>>>>                (Closes: #637397)
>>>
>>> How does splitting the package fix the undeclared conflict?
>>>
>>> Thanks,
>>> -Steve
>>>
>>>
>>
>>
>> --
>>
>> Anton
>>
>>
>>
>> --
>> debian-science-maintainers mailing list
>> debian-science-maintainers at lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
>>
>
>
>
> --
> Mathieu
>



-- 
Mathieu