The upstream must have changed the default backend which is not surprising, it should be fixable with a patch. I can look into it in a few days when I am back from vacation and in front of a computer again. The autotestpkg tests set KERAS_BACKEND=theano which is why this was missed. In the meantime users can set this environment variable similarly as a work-around. I don't really like changing upstream default behaviour but perhaps in this case it is warranted as an interim solution.
Regarding Tensorflow packaging I do not know, someone on debian-science mentioned difficulties with its build system. I do hope these are resolvable but it seems to be a big issue. On Mon, May 21, 2018, 1:16 AM Andreas Tille <ti...@debian.org> wrote: > Hi, > > the description says: > > ... Alternatively, Keras could run on Google's > TensorFlow (not yet available in Debian, but coming up). > > Is there some estimated time frame to package TensorFlow? > > If not please try to deactivate this alternative since the package does > not work as this bug report explains. > > Kind regards > > Andreas. > > -- > http://fam-tille.de >
