Bug#982601: python3-paraview Conflicts: python3-vtk9
Drew Parsons
dparsons at debian.org
Fri Feb 12 10:42:57 GMT 2021
Package: python3-paraview
Version: 5.9.0-2
Severity: normal
python3-paraview has just been given Conflicts: python3-vtk9, which is
a little confusing. Does it mean python3-paraview replaces
python3-vtk9? Or should not python3-paraview not be used at all?
(obviously there are other packages which use vtk via python).
I think more documentation or explanation is needed. What's going on here?
Alternatively, does it just mean python3-paraview should add
Provides: python3-vtk9
?
python3-vedo, for instance, needs python3-vtk9 and is therefore
affected by this change.
Is python3-paraview intended as a drop-in replacement for python3-vtk9 ?
Drew
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-paraview depends on:
ii libc6 2.31-9
ii libgcc-s1 10.2.1-6
ii libpython3.9 3.9.1-4
ii libstdc++6 10.2.1-6
ii paraview 5.9.0-2
ii python3 3.9.1-1
python3-paraview recommends no packages.
python3-paraview suggests no packages.
-- no debconf information
More information about the debian-science-maintainers
mailing list