Bug#637397: VTK 5.8 in experimental [was: Re: Bug#637397: Possible solutions]
On Fri, Sep 2, 2011 at 7:42 PM, Mathieu Malaterre mathieu.malate...@gmail.com wrote: vtk 5.8 has been uploaded to my public space on vasks: https://alioth.debian.org/~malat-guest/vtk/ I could not push to mentors for some reason. This is a /minimal/ package, I did not turn any new option on, this should only serve for migration testing. As a side note, I noticed today that the /files directory now contains the VTK 5.8.0 release ... since Sept 1st :) $ wget http://www.vtk.org/files/release/5.8/vtk-5.8.0.tar.gz $ md5sum vtk-5.8.0.tar.gz 37b7297d02d647cc6ca95b38174cb41f vtk-5.8.0.tar.gz There has not been any notice on the vtk-* mailing list, AFAIK -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637397: VTK 5.8 in experimental [was: Re: Bug#637397: Possible solutions]
On Thu, Sep 1, 2011 at 10:58 AM, Mathieu Malaterre mathieu.malate...@gmail.com wrote: On Mon, Aug 29, 2011 at 2:43 PM, Sylvestre Ledru sylves...@debian.org wrote: Le lundi 29 août 2011 à 13:31 +0100, Alastair McKinstry a écrit : On 2011-08-29 07:14, Mathieu Malaterre wrote: On Mon, Aug 29, 2011 at 4:35 AM, Steve M. Robbinsst...@sumost.ca wrote: I think the rest of this thread got off onto a tangent. In my mind, the germane question is not why Paraview embeds a patched VTK source tree but, rather: why is the paraview binary package now installing the VTK tools like vtkWrapPython? Indeed, that's the actual issue. Thanks Steve. Why does a running paraview binary need vtkWrapPython? That was also my initial question. Can it be stuck into /usr/lib/paraview to avoid the conflict? I believe the only outstanding issue is that VTK 5.8 is not released yet. Therefore vtkWrapPython* tools from ParaView 3.10 are much more advanced (more options) than that of VTK 5.6. I am also awaiting VTK 5.8 for VisIt packaging. Perhaps we should consider doing an vtk5.8 package in experimental, to discover issues and report them ahead of time to VTK / VisIT / Paraview developers ? Good idea. Are you volunteering for it? :) I'll do it. Meanwhile could someone please NMU vtk-5.6 with the proper fix and fix for lintian. vtk 5.8 has been uploaded to my public space on vasks: https://alioth.debian.org/~malat-guest/vtk/ I could not push to mentors for some reason. This is a /minimal/ package, I did not turn any new option on, this should only serve for migration testing. Enjoy -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637397: VTK 5.8 in experimental [was: Re: Bug#637397: Possible solutions]
On Mon, Aug 29, 2011 at 2:43 PM, Sylvestre Ledru sylves...@debian.org wrote: Le lundi 29 août 2011 à 13:31 +0100, Alastair McKinstry a écrit : On 2011-08-29 07:14, Mathieu Malaterre wrote: On Mon, Aug 29, 2011 at 4:35 AM, Steve M. Robbinsst...@sumost.ca wrote: I think the rest of this thread got off onto a tangent. In my mind, the germane question is not why Paraview embeds a patched VTK source tree but, rather: why is the paraview binary package now installing the VTK tools like vtkWrapPython? Indeed, that's the actual issue. Thanks Steve. Why does a running paraview binary need vtkWrapPython? That was also my initial question. Can it be stuck into /usr/lib/paraview to avoid the conflict? I believe the only outstanding issue is that VTK 5.8 is not released yet. Therefore vtkWrapPython* tools from ParaView 3.10 are much more advanced (more options) than that of VTK 5.6. I am also awaiting VTK 5.8 for VisIt packaging. Perhaps we should consider doing an vtk5.8 package in experimental, to discover issues and report them ahead of time to VTK / VisIT / Paraview developers ? Good idea. Are you volunteering for it? :) I'll do it. Meanwhile could someone please NMU vtk-5.6 with the proper fix and fix for lintian. Thanks, -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637397: VTK 5.8 in experimental [was: Re: Bug#637397: Possible solutions]
On Thu, Sep 01, 2011 at 10:58:33AM +0200, Mathieu Malaterre wrote: Meanwhile could someone please NMU vtk-5.6 with the proper fix and fix for lintian. I will do an NMU that overrides the lintian errors, which will unblock VTK and give us time to properly deal with the embedded libraries. -Steve signature.asc Description: Digital signature
Bug#637397: VTK 5.8 in experimental [was: Re: Bug#637397: Possible solutions]
Le lundi 29 août 2011 à 13:31 +0100, Alastair McKinstry a écrit : On 2011-08-29 07:14, Mathieu Malaterre wrote: On Mon, Aug 29, 2011 at 4:35 AM, Steve M. Robbinsst...@sumost.ca wrote: I think the rest of this thread got off onto a tangent. In my mind, the germane question is not why Paraview embeds a patched VTK source tree but, rather: why is the paraview binary package now installing the VTK tools like vtkWrapPython? Indeed, that's the actual issue. Thanks Steve. Why does a running paraview binary need vtkWrapPython? That was also my initial question. Can it be stuck into /usr/lib/paraview to avoid the conflict? I believe the only outstanding issue is that VTK 5.8 is not released yet. Therefore vtkWrapPython* tools from ParaView 3.10 are much more advanced (more options) than that of VTK 5.6. I am also awaiting VTK 5.8 for VisIt packaging. Perhaps we should consider doing an vtk5.8 package in experimental, to discover issues and report them ahead of time to VTK / VisIT / Paraview developers ? Good idea. Are you volunteering for it? :) Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
