Control: retitle -1 Paraview should use system VTK libraries
Unfortunately, upstream comented on this that it would be difficult to
use a seperate version of VTK because their development process just
doesn't take care of this. See, e.g. this recent thread:
severity 654839 wishlist
thanks
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I have fixed paraview-python and python-vtk conflict in paraview_3.12.0-3.
If there are no other comments related to the topic of the bug, I am
going to reduce the severity.
Thank you.
Anton
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
reasons to keep the bug as Serious,
Comments are welcome.
Please leave this bug as serious. You did not address my concern from:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654839#50
This package as-is should not go to wheezy.
Thanks,
--
Mathieu
--
To UNSUBSCRIBE, email to debian-bugs
I'm going to reduce the severity of the bug to the Wishlist.
When (if?) upstream will provide USE_SYSTEM_VTK option, then
we will definitely switch the paraview to the packaged version of VTK.
I do not see any reasons to keep the bug as Serious,
Comments are welcome.
Anton
--
To UNSUBSCRIBE,
On Sun, Jan 15, 2012 at 8:21 PM, Steve M. Robbins st...@sumost.ca wrote:
On Sun, Jan 15, 2012 at 11:22:33AM +0100, Mathieu Malaterre wrote:
Forwarding upstream comments.
I think now we have two options:
- Start working on PV 3.12 and getting rid of convenient copy of VTK.
I do not think it
Forwarding upstream comments.
I think now we have two options:
- Start working on PV 3.12 and getting rid of convenient copy of VTK.
I do not think it will be too difficult since VTK 5.8.0 was released
not too long ago
- Mark that PV 3.12 is shipped with convenient copy of VTK, and only
upload
On Sun, Jan 15, 2012 at 11:22:33AM +0100, Mathieu Malaterre wrote:
Forwarding upstream comments.
I think now we have two options:
- Start working on PV 3.12 and getting rid of convenient copy of VTK.
I do not think it will be too difficult since VTK 5.8.0 was released
not too long ago
-
Forwared upstream:
http://www.paraview.org/pipermail/paraview/2012-January/023675.html
--
Mathieu
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Sat, Jan 7, 2012 at 10:22 AM, Mathieu Malaterre
mathieu.malate...@gmail.com wrote: ...
This was my point when I requested to move VTK to deb-sci umbrella, I
believe those two packages needs the same team of maintainer, and a very
close communication
I think it is a good idea to
Hi,
On Fri, Jan 6, 2012 at 8:39 PM, Anton Gladky gladky.an...@gmail.com wrote:
We already discussed it some months ago. From my point of view, it is
not so simple...
Agreed
At least the list of compiled vtk-libraries in vtk and paraview
packages is not the same [1] and [2].
That's a
On Sat, Jan 07, 2012 at 10:22:36AM +0100, Mathieu Malaterre wrote:
Really it boils down to two things:
- What is upstream position on this ? If upstream really do want to
release paraview on fixed schedule, with backward compatible code so
that people can build paraview with the latest
On Sat, Jan 7, 2012 at 2:08 PM, Steve M. Robbins st...@sumost.ca wrote:
On Sat, Jan 07, 2012 at 10:22:36AM +0100, Mathieu Malaterre wrote:
Really it boils down to two things:
- What is upstream position on this ? If upstream really do want to
release paraview on fixed schedule, with backward
Hi Dominique,
We already discussed it some months ago. From my point of view, it is
not so simple...
At least the list of compiled vtk-libraries in vtk and paraview
packages is not the same [1] and [2].
Also VTK and Paraview are not usually releasing at the same time (I
think, Mathieu noticed it
Package: paraview
Severity: serious
Please remove Paraview's VTK directory and link instead against
Debian's vtk libraries.
Thanks
-Dominique
15 matches
Mail list logo
