Re: Salvaging keras - unpushed commits?
- To: debian-science@lists.debian.org
- Subject: Re: Salvaging keras - unpushed commits?
- From: Andrius Merkys <merkys@debian.org>
- Date: Tue, 3 May 2022 08:54:37 +0300
- Message-id: <[🔎] 756dc865-5284-01a3-841e-7ade8f6e9be3@debian.org>
- In-reply-to: <CADopUHaOr_2x8WfKhbeDo3Cy0wTqDyxtutCEpMrHPr+2ZZQ3Lw@mail.gmail.com>
- References: <fbd918c6-fdba-920b-b4e0-1bfbb9408155@debian.org> <YmlJvYXz+VR1neNH@an3as.eu> <CAEZpsw0eA9=pu_q=HjnOrA_sn_7t3JwqdkpTo2TF8cmR-boDUg@mail.gmail.com> <CADopUHaOr_2x8WfKhbeDo3Cy0wTqDyxtutCEpMrHPr+2ZZQ3Lw@mail.gmail.com>
Hi,
On 2022-04-28 13:12, Stephen Sinclair wrote:
> The last time I looked at Keras, there were some hard to fix issues
> and since it is my understanding that keras as a package outside of
> Tensorflow has reached end of life, it does not seem useful to try to
> maintain it.
At first glance issues with Keras in Debian seemed simple to me: just
incompatibilities with newer Python versions, but I admit patching them
is slow converging process. TensorFlow is needed for Keras 2.4.0 or
later and that seems stuck. I would prefer bookworm having Keras 2.3.1
than not having Keras at all.
Anyway, I have solved the issue with unpushed commits and tag. Will see
if I can get it further.
Best,
Andrius
Reply to: