It is fixed in Debian already. But there is another newer upstream release 3.14 [1] instead of 3.12 in Precise. I do not know, whether the release team agree to sync newer upstream version during freeze (subscribing them).
Another opportunity is to get 3.12.0-6 debian version from the git-repository [2]. Conflict is also resolved there, but I do not really remember, whether 3.12.0-6 version is reliable. I would recommend 3.14.0 anyway. [1] http://packages.debian.org/wheezy/paraview [2] http://anonscm.debian.org/gitweb/?p=debian-science/packages/paraview.git;a=shortlog;h=refs/tags/debian/3.12.0-4 Anton -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/975417 Title: ParaView conflicts with python-vtk, python-viper,... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/paraview/+bug/975417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
