Bug#637397: VTK 5.8 in experimental [was: Re: Bug#637397: Possible solutions]

2011-09-03 Thread Mathieu Malaterre
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,

Bug#637397: VTK 5.8 in experimental [was: Re: Bug#637397: Possible solutions]

2011-09-02 Thread Mathieu Malaterre
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,

Bug#637397: VTK 5.8 in experimental [was: Re: Bug#637397: Possible solutions]

2011-09-01 Thread Mathieu Malaterre
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

Bug#637397: VTK 5.8 in experimental [was: Re: Bug#637397: Possible solutions]

2011-09-01 Thread Steve M. Robbins
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.

Bug#637397: Possible solutions

2011-08-29 Thread Mathieu Malaterre
On Mon, Aug 29, 2011 at 4:35 AM, Steve M. Robbins st...@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

Bug#637397: Possible solutions

2011-08-29 Thread Alastair McKinstry
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

Bug#637397: VTK 5.8 in experimental [was: Re: Bug#637397: Possible solutions]

2011-08-29 Thread Sylvestre Ledru
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

Bug#637397: Fwd: Re: Bug#637397: Possible solutions

2011-08-29 Thread Alastair McKinstry
Hi, I see that as maintainer of VTK you were not on the CC: list, so I'm forwarding this email to you directly: do you think it would be much work to build an experimental vtk5.8 package? regards Alastair McKinstry Original Message Subject:Re: Bug#637397: Possible

Bug#637397: Possible solutions

2011-08-28 Thread Mathieu Malaterre
On Sat, Aug 27, 2011 at 12:35 PM, Sylvestre Ledru sylves...@debian.org wrote: Le samedi 27 août 2011 à 13:31 +0300, Anton Gladky a écrit : I see only 2 opportunities to fix it:   1) Disable python-support in paraview;   2) Claim, that paraview conflicts with python-vtk; 3) get in touch with

Bug#637397: Possible solutions

2011-08-28 Thread Sylvestre Ledru
Le dimanche 28 août 2011 à 17:30 +0200, Mathieu Malaterre a écrit : On Sat, Aug 27, 2011 at 12:35 PM, Sylvestre Ledru sylves...@debian.org wrote: Le samedi 27 août 2011 à 13:31 +0300, Anton Gladky a écrit : I see only 2 opportunities to fix it: 1) Disable python-support in paraview;

Bug#637397: Possible solutions

2011-08-28 Thread Alastair McKinstry
On 2011-08-28 16:47, Sylvestre Ledru wrote: Le dimanche 28 août 2011 à 17:30 +0200, Mathieu Malaterre a écrit : On Sat, Aug 27, 2011 at 12:35 PM, Sylvestre Ledrusylves...@debian.org wrote: Le samedi 27 août 2011 à 13:31 +0300, Anton Gladky a écrit : I see only 2 opportunities to fix it:

Bug#637397: Possible solutions

2011-08-28 Thread Anton Gladky
Paraview is really not an easy source to package. Now the debian-directory is rewritten almost completely to make the packaging as simple as possible. I prefer to escape overpatching, because it complicates a maintainance. I am afraid, that replacing the vtk is not an easy work. It can produce

Bug#637397: Paraview without embedded VTK [was: Re: Bug#637397: Possible solutions]

2011-08-28 Thread Sylvestre Ledru
Le dimanche 28 août 2011 à 21:23 +0300, Anton Gladky a écrit : Paraview is really not an easy source to package. Now the debian-directory is rewritten almost completely to make the packaging as simple as possible. I prefer to escape overpatching, because it complicates a maintainance. Well,

Bug#637397: Possible solutions

2011-08-28 Thread Julien Cristau
On Sun, Aug 28, 2011 at 21:23:56 +0300, Anton Gladky wrote: I prefer to escape overpatching, because it complicates a maintainance. So does having to fix bugs 50 times instead of one because a library is copied all over the place. Cheers, Julien -- To UNSUBSCRIBE, email to

Bug#637397: Possible solutions

2011-08-28 Thread Steve M. Robbins
On Sun, Aug 28, 2011 at 05:47:50PM +0200, Sylvestre Ledru wrote: It was tolerated that paraview be build with the convenient VTK library, but now the package are now installing vtk related tools (tools that are already installed by VTK-* package), eg: I think the rest of this thread got

Bug#637397: Paraview without embedded VTK [was: Re: Bug#637397: Possible solutions]

2011-08-28 Thread Steve M. Robbins
On Sun, Aug 28, 2011 at 08:30:50PM +0200, Sylvestre Ledru wrote: Le dimanche 28 août 2011 à 21:23 +0300, Anton Gladky a écrit : Paraview is really not an easy source to package. Now the debian-directory is rewritten almost completely to make the packaging as simple as possible. I prefer

Bug#637397: Possible solutions

2011-08-27 Thread Anton Gladky
I see only 2 opportunities to fix it: 1) Disable python-support in paraview; 2) Claim, that paraview conflicts with python-vtk; Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#637397: Possible solutions

2011-08-27 Thread Sylvestre Ledru
Le samedi 27 août 2011 à 13:31 +0300, Anton Gladky a écrit : I see only 2 opportunities to fix it: 1) Disable python-support in paraview; 2) Claim, that paraview conflicts with python-vtk; 3) get in touch with upstream and ask them to consider changing the name of the binary. ;) Sylvestre