Bug#1027215: Bug#1026539: How much do we lose if we remove theano (+keras, deepnano, invesalius)?

[Andreas Tille]

Hi Rebecca,

Am Wed, Mar 01, 2023 at 10:41:23PM +0000 schrieb Rebecca N. Palmer:
> I agree that switching to Aesara is probably the only reasonable option
> other than removal.  (I'd given up on trying to fix 1.0, and was intending
> to let removal happen.)
> 
> However, it's a much bigger change than is normally allowed in bookworm at
> this point.  (1.1 includes multiple breaking changes, which is why it's in
> experimental, but a quick codesearch suggests these parts *may* not be used
> in keras/deepnano. https://github.com/aesara-devs/aesara/releases?page=8 )

I admit I do not see any good reason to stick to the old version if we
decided before that keras/deepnano are no real blockers to even drop
theano.  Thus I was considering it more promising to spent my time on
the latest version.
 
> Do you want to ask release team for permission to do this?

If it would have build smoothly on all architectures, yes.  But we have
the first trouble on arm64[1]

> Or do you want
> to try the same patches on 1.0?  (I suspect that that won't work, but I
> haven't actually tried it.)
> 
> (Also, you might not want numpy1p24_compat.patch - the v1p0 branch is
> currently in whatever state it was in when I gave up on it, and my vague
> memory is that this was a failed experiment, though I don't know if that
> meant "actively bad" or just "not a (full) solution".)

I've found some patches inside numpy1p24_compat.patch that were also
in Aesara.  Since the package did not fully build with this patch
alone I've added a separate patch with the only goal to build and pass
the test suite.

Kind regards
    Andreas.

[1] https://buildd.debian.org/status/fetch.php?pkg=theano&arch=amd64&ver=1.1.2%2Bdfsg-4&stamp=1677751828&raw=0

-- 
http://fam-tille.de