[Debian-med-packaging] Bug#984063: Closing bug (Was: Bug#984063: itk libtiff test issues (Was: Bug#984063))

Andreas Tille andreas at fam-tille.de
Sun Jan 16 06:13:21 GMT 2022


Am Sun, Jan 16, 2022 at 07:07:01AM +0100 schrieb Sebastiaan Couwenberg:
> On 1/15/22 21:45, Andreas Tille wrote:
> > > There is no RM bug for insighttoolkit4 yet,
> > 
> > Steve simply bumped the version right in d/changelog[1]
> 
> How does the insighttoolkit5 package in unstable cause the removal of
> insighttoolkit4?

It does not.  However, from simply using the same repository you can
draw the conclusion that there is no intention to maintain two different
versions.  Well, for sure we could use another branch - but Steve in
some mail on Debian Med list stated he has no intention to maintain
more than one version.
 
> > IMHO it would be sad to loose OTB.  When I once started looking at the
> > packaging upstream was quite responsive.  Did you discussed the issue?
> 
> I did, see the comments in the MR linked above. OTB 9 should support ITK5,
> but is not expected until the end of the year.

Thanks for the information.  I'm absolutely not in a hurry to file RM
requests for insighttoolkit4 and I think it is not sensible to remove
OTB just to reinject it later and waiting in new for a couple of months.
So we can simply leave the situation as is if you ask me.  In case you
might stumble upon a patch for insighttoolkit4 to build with recent gcc
and there are good reasons to keep this and current otb in testing I'd
volunteer to upload a fix for insighttoolkit4 (which I would not touch
personally otherwise).

Kind regards

       Andreas.

-- 
http://fam-tille.de



More information about the Debian-med-packaging mailing list