[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 <[email protected]> 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 <[email protected]> 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 > [email protected] > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers > -- Mathieu -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
