[Debian-med-packaging] Bug#1094896: ants: FTBFS with ITK 5.4 - new upstream ?

[Steve M. Robbins]

Source: ants
Severity: normal
Tags: ftbfs

ITK upstream has released v5.4 and I'd like to upload to Debian soon.
At present, ITK 5.4 is available in experimental.

I have done a test-rebuild locally of ANTS, which failed:

In file included from /usr/include/ITK-5.4/itkLightObject.h:21,
                 from /usr/include/ITK-5.4/itkObject.h:31,
                 from /usr/include/ITK-5.4/itkDataObject.h:31,
                 from /home/steve/Packages/insighttoolkit/transition-
rebuilds/ants-2.4.3+dfsg/Utilities/antsCommandLineOption.h:17,
                 from /home/steve/Packages/insighttoolkit/transition-
rebuilds/ants-2.4.3+dfsg/Utilities/antsCommandLineOption.cxx:14:
/home/steve/Packages/insighttoolkit/transition-
rebuilds/ants-2.4.3+dfsg/Utilities/antsCommandLineOption.h: In member function
‘virtual const char* itk::ants::OptionFunction::GetNameOfClass() const’:
/home/steve/Packages/insighttoolkit/transition-
rebuilds/ants-2.4.3+dfsg/Utilities/antsCommandLineOption.h:62:16: error:
‘Option’ was not declared in this scope
   62 |   itkTypeMacro(Option, DataObject);
      |                ^~~~~~
/home/steve/Packages/insighttoolkit/transition-
rebuilds/ants-2.4.3+dfsg/Utilities/antsCommandLineOption.h:62:3: error:
template argument 1 is invalid


I noticed that there is a new upstream version, so I cloned the github and was
able to successfully build.
Perhaps it's possible to update the ANTS package before ITK is uploaded to
unstable?

Best,
-Steve



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (700, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.10.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled