Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.

  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-python@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects <bug number of blocking py2removal bug> + src:vmtk

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-python@lists.debian.org mailing list.

Hi,

vmtk is using Python3 in Git[1], but there are build issues with vtk7:

...
cd /build/vmtk-1.4.0+dfsg/obj-x86_64-linux-gnu/vtkVmtk/ComputationalGeometry && /usr/bin/c++ -DITK_IO_FACTORY_REGISTER_MANAGER -DvtkvmtkComputationalGeometry_EXPORTS -I/build/vmtk-1.4.0+   dfsg/obj-x86_64-linux-gnu/ITKFactoryRegistration -I/usr/include/hdf5/serial -I/usr/include/nifti -I/usr/include/gdcm-3.0 -I/usr/include/ITK-4.13 -I/build/vmtk-1.4.0+dfsg/vtkVmtk -I/build/  vmtk-1.4.0+dfsg/vtkVmtk/Common -I/build/vmtk-1.4.0+dfsg/vtkVmtk/ComputationalGeometry -I/build/vmtk-1.4.0+dfsg/vtkVmtk/DifferentialGeometry -I/build/vmtk-1.4.0+dfsg/vtkVmtk/IO -I/build/    vmtk-1.4.0+dfsg/vtkVmtk/Misc -I/build/vmtk-1.4.0+dfsg/vtkVmtk/Segmentation -I/build/vmtk-1.4.0+dfsg/vtkVmtk/Contrib -I/build/vmtk-1.4.0+dfsg/vtkVmtk/Utilities/vtkvmtkITK -I/build/vmtk-1.4. 0+dfsg/obj-x86_64-linux-gnu/vtkVmtk -I/usr/include/vtk-7.1 -I/usr/include/python3.9 -g -O2 -fdebug-prefix-map=/build/vmtk-1.4.0+dfsg=. -fstack-protector-strong -Wformat -Werror=format-     security -Wdate-time -D_FORTIFY_SOURCE=2   -O2 -g -DNDEBUG -fPIC -fPIC -o CMakeFiles/vtkvmtkComputationalGeometry.dir/vtkvmtkCenterlineBranchExtractor.cxx.o -c /build/vmtk-1.4.0+dfsg/      vtkVmtk/ComputationalGeometry/vtkvmtkCenterlineBranchExtractor.cxx
In file included from /build/vmtk-1.4.0+dfsg/vtkVmtk/ComputationalGeometry/vtkvmtkCenterlineBranchExtractor.cxx:24:
/build/vmtk-1.4.0+dfsg/vtkVmtk/ComputationalGeometry/vtkvmtkPolyBallLine.h:45:10: error: 'double vtkvmtkPolyBallLine::EvaluateFunction(double, double, double)' marked 'override', but does  not override
   45 |   double EvaluateFunction(double x, double y, double z) VTK_OVERRIDE
      |          ^~~~~~~~~~~~~~~~
[  4%] Building CXX object vtkVmtk/IO/CMakeFiles/vtkvmtkIO.dir/vtkvmtkXdaReader.cxx.o


Any help is welcome.

Kind regards

       Andreas.

[1] https://salsa.debian.org/science-team/vmtk

First thing to try would be building against vtk9, which Anton recently
released for us.

Upstream authors in other packages have commented that vtk7 is quite
old. Builds might be more reliable with vtk9, although it does have
issues with the 32-bit systems.

Drew

Hi,

Thanks for the hint but switching to vtk9 leads to cmake errors:

Hi,
maybe rebuilding vtk9 with gdcm support will fix this?

By the way, I've noticed that vtk9 is built with gl2ps support
whereas paraview is not. Not sure but this may lead to some troubles.
Would be great to rebuild paraview with gl2ps also.

Best
C

Christophe TROPHIME
Research Engineer

CNRS - LNCMI
25, rue des Martyrs
BP 166
38042 GRENOBLE Cedex 9
FRANCE

Tel : +33 (0)4 76 88 90 02
Fax : +33 (0) 4 76 88 10 01
Office U 19
M@il : christophe.trophime@lncmi.cnrs.fr

----- Original Message -----

Dear submitter,

as the package vmtk has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1008792

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)