Bug#1027215: How much do we lose if we remove theano (+keras, deepnano, invesalius)?
Hi Thiago, Am Mon, Jan 16, 2023 at 11:08:35AM -0300 schrieb Thiago Franco Moraes: > Done! I removed both python3-theano and python3-keras. Thanks for the quick response. Autopkgtest currently fails due to Bug #1027851 pytorch FTBFS with Python 3.11 as default version I think, I'll wait a bit until this is clarified. Kind regards Andreas. -- http://fam-tille.de
Bug#1027215: How much do we lose if we remove theano (+keras, deepnano, invesalius)?
Hi Andreas, Done! I removed both python3-theano and python3-keras. Best regards. Em seg., 16 de jan. de 2023 às 09:54, Andreas Tille escreveu: > Hi Thiago, > > Am Sat, Jan 14, 2023 at 07:50:27PM -0300 schrieb Thiago Franco Moraes: > > Hi Rebecca, > > > > InVesalius can work without Theano (and Keras). It will use Pytorch. > > Would you mind updating the packaging without Theano? Currently its in > its Build-Depends. Would it be sufficient to drop this Build-Depends? > If yes, I would upload a fixed package. > > Kind regards >Andreas. > > -- > http://fam-tille.de >
Bug#1027215: How much do we lose if we remove theano (+keras, deepnano, invesalius)?
Hi Thiago, Am Sat, Jan 14, 2023 at 07:50:27PM -0300 schrieb Thiago Franco Moraes: > Hi Rebecca, > > InVesalius can work without Theano (and Keras). It will use Pytorch. Would you mind updating the packaging without Theano? Currently its in its Build-Depends. Would it be sufficient to drop this Build-Depends? If yes, I would upload a fixed package. Kind regards Andreas. -- http://fam-tille.de
Bug#1027215: How much do we lose if we remove theano (+keras, deepnano, invesalius)?
Hello, On 2023-01-14 13:12, Rebecca N. Palmer wrote: theano has been mostly abandoned upstream since 2018. (The Aesara fork is not abandoned, but includes interface changes including the import name, so would break reverse dependencies not specifically altered for it.) Its reverse dependencies are keras, deepnano and invesalius. It is currently broken, probably by numpy 1.24 (#1027215), and the immediately obvious fixes weren't enough (https://salsa.debian.org/science-team/theano/-/pipelines). Is this worth spending more effort on fixing, or should we just remove it? keras is needed to train evaluation models for qmean [1] which I intend [2] to package eventually. qmean is a quite popular protein model evaluation tool, personally I use it a lot and I believe it would be useful to have it in Debian. That said, it is OK to omit keras in bookworm if need be, but I would like to see it back for trixie. [1] https://git.scicore.unibas.ch/search?search=keras_source=navbar_id=69_id=25_code=true_ref=master [2] https://bugs.debian.org/976981 Best, Andrius
Bug#1027215: How much do we lose if we remove theano (+keras, deepnano, invesalius)?
Hi Rebecca, InVesalius can work without Theano (and Keras). It will use Pytorch. Best regards. Em sáb., 14 de jan. de 2023 às 08:12, Rebecca N. Palmer < rebecca_pal...@zoho.com> escreveu: > theano has been mostly abandoned upstream since 2018. (The Aesara fork > is not abandoned, but includes interface changes including the import > name, so would break reverse dependencies not specifically altered for it.) > > Its reverse dependencies are keras, deepnano and invesalius. > > It is currently broken, probably by numpy 1.24 (#1027215), and the > immediately obvious fixes weren't enough > (https://salsa.debian.org/science-team/theano/-/pipelines). > > Is this worth spending more effort on fixing, or should we just remove it? > > >
Bug#1027215: How much do we lose if we remove theano (+keras, deepnano, invesalius)?
Currently, I'd say PyTorch and TensorFlow are the two most popular libraries. And I even worry google is trying to write something new like Jax to replace TensorFlow in some aspects. On Sat, 2023-01-14 at 11:12 +, Rebecca N. Palmer wrote: > theano has been mostly abandoned upstream since 2018. (The Aesara fork > is not abandoned, but includes interface changes including the import > name, so would break reverse dependencies not specifically altered for it.) > > Its reverse dependencies are keras, deepnano and invesalius. > > It is currently broken, probably by numpy 1.24 (#1027215), and the > immediately obvious fixes weren't enough > (https://salsa.debian.org/science-team/theano/-/pipelines). > > Is this worth spending more effort on fixing, or should we just remove it? >
Bug#1027215: How much do we lose if we remove theano (+keras, deepnano, invesalius)?
On Sat, Jan 14, 2023 at 11:12:07AM +, Rebecca N. Palmer wrote: > theano has been mostly abandoned upstream since 2018. (The Aesara fork is > not abandoned, but includes interface changes including the import name, so > would break reverse dependencies not specifically altered for it.) > > Its reverse dependencies are keras, deepnano and invesalius. keras is already orphaned, it needs to be updated either now or later. And it depends heavily on tensorflow, python bindigs of which are still not in yet. deepnano is also kind of abandoned. Last commit is from 2017. On grepping the code for invesalius, I see that it only uses theano as an option for backend. There are three backends as far as I can see, torch, plaidml (not in debian) and theano. So as long as torch works, this _probably_ should do fine here. In any case, the upstream for this package is active and we can ask them. -- Best, Nilesh signature.asc Description: PGP signature
Bug#1027215: How much do we lose if we remove theano (+keras, deepnano, invesalius)?
theano has been mostly abandoned upstream since 2018. (The Aesara fork is not abandoned, but includes interface changes including the import name, so would break reverse dependencies not specifically altered for it.) Its reverse dependencies are keras, deepnano and invesalius. It is currently broken, probably by numpy 1.24 (#1027215), and the immediately obvious fixes weren't enough (https://salsa.debian.org/science-team/theano/-/pipelines). Is this worth spending more effort on fixing, or should we just remove it?
