Bug #2166
paraview and vtk conflicting files
0%
Description
Hello,
First of all, I really appreciate the effort put into compiling any package. I am curently trying to install paraview, but it conflicts with many vtk files.
pacman -S paraview
error: failed to commit transaction (conflicting files) ...[ very long list of files ]...
My system:
OpenRC, linux-libre Linux 4.20.0-gnu-1 #1 SMP PREEMPT Sun Jan 6 20:50:27 UTC 2019 x86_64 GNU/Linux
vtk 8.2.0-1, trying to install paraview-5.6.0-2
Files
History
Updated by bill-auger about 5 years ago
- File paraview-vtk-conflicts paraview-vtk-conflicts added
there are no such conflicts unless the 'vtk' package is already installed
the conflicting files are predominantly in /usr/lib/python3.7/site-packages/vtkmodules - presumably where the 'vtk' package puts it's files
the entire list of conflicting files is attached
$ grep -c '(owned by vtk)' ~/paraview-vtk-conflicts 548 $ grep -cv '(owned by vtk)' ~/paraview-vtk-conflicts 0
off-hand i would say that 'paraview' appears to be providing its own copy of 'vtk'
and in typical myopic "pipish" style, doing so by blindly clobbering what is (or should be) owned by another package - fortunately, sane package managers such as pacman do not allow that to happen
in any case these are both arch packages so we need to first see if this is reported in arch
Updated by bill-auger about 5 years ago
- Status changed from open to forwarded upstream
arch ticket https://bugs.archlinux.org/task/61594
upstream ticket https://gitlab.kitware.com/paraview/paraview/issues/18751
Updated by nona almost 4 years ago
Oh! Thanks! Because of this, I was able to find paraview-opt in the AUR repositories, which basically installs paraview in /opt. Now I have both vtk and paraview. Thanks!
Updated by Zuss almost 2 years ago
Looks like this was just fixed recently. I can install paraview v5.10.1 and vtk v9.1.0 together without any errors.
Related PR on the Arch package: https://github.com/archlinux/svntogit-community/commit/a780185671fe116a9e5afdb0df6f52a732af0439
Updated by Zuss almost 2 years ago
- Status changed from forwarded upstream to not-a-bug
Closed as the conflict issues are fixed