Keep getting same 2 problems during “zypper dup”. I do use paraview quite frequently that is quite tricky to use and I am reluctant to delete anything associated with it. For problem 1, I have been selecting Solution 1 but same problem comes back each day. For problem 2, I have been taking Solution 2 but that also comes back each day.
Any advice appreciated. thanks, tom kosvic
tom@mydesktop: ~ $ sudo zypper dup
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
2 Problems:
Problem: 1: problem with the installed libcerf2-2.4-38.78.x86_64
Problem: 2: the installed paraview-plugins-6.1.0-150.3.x86_64 requires 'libvtkfmt.so.1()(64bit)', but this requirement cannot be provided
deleted providers: libvtk1-openmpi4-9.6.1-2.3.x86_64
Problem: 1: problem with the installed libcerf2-2.4-38.78.x86_64
Solution 1: install libcerf2-2.4-3.9.x86_64 from vendor openSUSE
replacing libcerf2-2.4-38.78.x86_64 from vendor obs://build.opensuse.org/science
Solution 2: keep obsolete libcerf2-2.4-38.78.x86_64
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): 1
Problem: 2: the installed paraview-plugins-6.1.0-150.3.x86_64 requires 'libvtkfmt.so.1()(64bit)', but this requirement cannot be provided
deleted providers: libvtk1-openmpi4-9.6.1-2.3.x86_64
Solution 1: Following actions will be done:
deinstallation of paraview-plugins-6.1.0-150.3.x86_64
deinstallation of libparaview6_1-6.1.0-150.3.x86_64
Solution 2: keep obsolete libvtk1-openmpi4-9.6.1-2.3.x86_64
Solution 3: break paraview-plugins-6.1.0-150.3.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c):
Just to confirm, for now on OpenSUSE the only way to use paraview is to build it from sources together with vtk. Binary packages are not an option now.
Paraview sources come packaged with openfoam cfd app, third-party packages. That’s where I use it most often. I’ve been using the “system” paraview instead of that “user” one. I haven’t compiled that version but I guess I will. Guess I’ll have to change to "user"paraview.
Just for info. paraview 6.1.1 compiled successfully using the openfoam scripts and the build/make scripts compiled both paraview and vtk. Compilation was done w/o mpi as was the current paraview in opensuse science repo.
From openfoam.
====
Installation complete for paraview-6.1.1 with qt-5.15.19
ParaView_DIR=/home/tom/Cfd/openfoam/ThirdParty-v2606/platforms/linux64Gcc/ParaView-6.1.1
You may need to update the OpenFOAM environment by running:
wmRefresh
====
Perhaps the build/make scripts from openfoam could be of assistance to the paraview science maintainer. I could forward these to whomever that might be.
openfoam has an additional paraview make script that includes mpi and other options but I haven’t tried it. I don’t think I would ever need a plot/display program with parallel computing.
Just for info of any interested person needing latest paraview.
I do see that the paraview from opensuse science repo and also the version from opensuse repo throw seg faults upon start. The version compiled from openfoam starts fine and looks to be operational. I haven’t loaded an output file into it yet.
This thread went off on a tangent. My apologies. Just for info again to those using paraview.