On Mon, Aug 24, 2020 at 4:51 PM Olek Wojnar <[email protected]> wrote:

> Hi Mo,
>
> Sorry about the slow reply, I've been a bit buried with emails and I'm not
> answering them as well as I would like. :(
>
> On Wed, Aug 19, 2020 at 12:40 AM Mo Zhou <[email protected]> wrote:
>
>> Hi Olek,
>>
>> What a good news! Your hardword is much appreciated.
>>
>
> Thanks! I'm really looking forward to this making life easier for people
> who want to package software that uses Bazel to build.
>
> There are some preliminary packaging changes (using bazel) for
>> tensorflow. Is it in shape so that I can build TF from the git repo?
>> Or what remains to be done?
>>
>
> I'm not sure, Michael (copied above) took the lead on the TensorFlow
> packaging. Michael, could you please provide an update? Are you running
> into any specific issues that you could use help with?
>

Hey Mo, we have some unpackaged dependencies. Currently TensorFlow can be
built using code copies, but obviously that isn't a great plan. Here are
the current code copies:
https://github.com/meteorcloudy/tensorflow/tree/r2.2-debian/debian/dist

If you want to help out you can use the bazel-bootstrap and
libcheck-framework-java binary packages from
https://people.debian.org/~olek/packages/


>
> Our primary contact on the upstream Bazel team (who also does some work
> with upstream TensorFlow) verified that the latest Debian Bazel
> (bazel-bootstrap) package *does* successfully build TensorFlow but I
> believe there may have been some TensorFlow dependencies that were still
> missing in Debian?
>

I've added our upstream contact Yun Peng to this thread.


>
> -Olek
>

Reply via email to