ParaView conflicts with python-vtk, python-viper,...

[Miha Marolt]

When I tried to install ParaView,

sudo apt-get install paraview,

I got informed that 4 other packages have to be removed,

The following packages will be REMOVED:
  mayavi2 python-dolfin python-viper python-vtk

Are you aware of this conflict? Can it be fixed?

I'm using up to date Ubuntu 12.04.

[Anton Gladky (gladky-anton)]

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

[Anton Gladky (gladky-anton)]

I meant debian/3.12.0-4, sorry.

[Stefano Rivera (stefanor)]

paraview has no reverse dependencies, although a few reverse-recommends, and isn't seeded. So I'm certaintly open to granting a feature freeze exception for 3.14.

I'd like to see that it builds and works on precise, though.
https://wiki.ubuntu.com/FreezeExceptionProcess

Bonus points for checking if it works with the packages that recommend it.

[Miha Marolt (tloramus)]

ParaView 3.14.0-1 from Debian [1] can't be installed because it has a dependency libhdf5-7 that is not available in Precise.

Anton, if I understood you correctly, you suggested me to get source package snapshot debian/3.12.0-4 from Debian git repository [2] and build a binary .deb package following for example instructions [3]. After I got .deb I could install it with dpkg. Is that correct?

[1] http://packages.debian.org/wheezy/paraview
[2] http://anonscm.debian.org/gitweb/?p=debian-science/packages/paraview.git;a=shortlog
[3] http://www.debian.org/doc/manuals/maint-guide/

[Anton Gladky (gladky-anton)]

I have a PPA, where 3.14 version is built and I am using it personally
on Precise [1].

> Anton, if I understood you correctly, you suggested me to get source
> package snapshot debian/3.12.0-4 from Debian git repository [2] and
> build a binary .deb package following for example instructions [3].
> After I got .deb I could install it with dpkg. Is that correct?

Yes, you can try to do that. But I would prefer, if it is fixed
globally in Precise.
You are also welcome to use PPA [1], if you are happy with 3.14 version.

[1] https://launchpad.net/~gladky-anton/+archive/paraview/+packages

Anton

[Miha Marolt (tloramus)]

ParaView 3.14 from your PPA seems to be working fine, thanks!

[Stefano Rivera (stefanor)]

Looks reasonable to me. FFe granted.

I don't like the way paraview is sticking non-python-module shared libraries into /usr/lib/python2.7/dist-packages/, but that doesn't seem to actually be problematic.

[Anton Gladky (gladky-anton)]

I uploaded yesterday the version 3.14.1 into Debian Unstable [1]. It
is a bugfix
release from 2012/04/06 [2].

Please, consider the syncing of this version.

Thanks

[1] http://packages.qa.debian.org/p/paraview.html
[2] http://www.paraview.org/pipermail/paraview/2012-April/024578.html

Anton

[Stefano Rivera (stefanor)]

As with 3.14.0, it can't be synced, as it has a versioned Build-Depends on libhdf5-dev, which is a virtual package in precise. Please provide a patch for a sponsor to apply on the Debian version.

But aside from that, I'm quite happy to extend the FFe to cover 3.14.1 too.

[Anton Gladky (gladky-anton)]

Please, see attached diff.
Thanks.

Anton

[Anton Gladky (gladky-anton)]

If there is a decision to sync a paraview from Debian Unstable, I
think it is better to do it earlier to have an opportunity to test it
before Precise-release.

Anton

[Anton Gladky (gladky-anton)]

I have uploaded a new version on PPA [1].
Please, consider a syncing from there.

Thanks

Anton

[1] https://launchpad.net/~gladky-anton/+archive/paraview

[Barry Warsaw (barry)]

Anton, when I build the sid version (3.14.1) + your backport.diff from comment #10, I get a FTBFS. Was there some other changes you needed to make that perhaps weren't included in your diff? (Also, could you use a unified or context diff next time so patch can consume it?).

See attached build log.

[Barry Warsaw (barry)]

Ah, I see from your PPA you made this change:

diff -Nru paraview-3.14.0/debian/patches/fix_hdf5_mpi.patch paraview-3.14.1/debian/patches/fix_hdf5_mpi.patch
--- paraview-3.14.0/debian/patches/fix_hdf5_mpi.patch 1970-01-01 00:00:00.000000000 +0000
+++ paraview-3.14.1/debian/patches/fix_hdf5_mpi.patch 2012-04-16 18:46:05.000000000 +0000
@@ -0,0 +1,14 @@
+Description: Fix FTBFS due to missing include path "mpi"
+Author: Anton Gladky <email address hidden>
+Last-Update: 2012-04-16
+
+--- a/VTK/Utilities/vtknetcdf/CMakeLists.txt
++++ b/VTK/Utilities/vtknetcdf/CMakeLists.txt
+@@ -302,6 +302,7 @@
+ ${CMAKE_CURRENT_SOURCE_DIR}/libsrc4
+ ${CMAKE_CURRENT_BINARY_DIR}
+ ${VTK_HDF5_INCLUDE_DIR}
++ "/usr/include/mpi"
+ )
+
+ set(netcdf_liblib_SOURCES "" CACHE INTERNAL "" FORCE)

[Barry Warsaw (barry)]

With these changes, the package builds and installs on Precise afaict. I also installed the Recommends and saw no problems. I was able to `python -c "import paraview"` so given Stefano's comments above, I'll upload the new package. Thanks!

[Launchpad Janitor (janitor)]

This bug was fixed in the package paraview - 3.14.1-1ubuntu1

---------------
paraview (3.14.1-1ubuntu1) precise; urgency=low

  * Merge from Debian. Remaining changes:
    - debian/control: Adjust Build-Depends on libboost and libhdf5 for
      more Ubuntu-appropriate packages.
    - debian/patches/mpi-include.patch: Add /usr/include/mpi explicitly to
      the CMakeLists.txt file for VTK.
    Given by Anton Gladky. LP: #975417
 -- Barry Warsaw <email address hidden> Tue, 17 Apr 2012 16:44:17 -0400