Arch Linux User Repository

Well, the arch wiki is pretty clear that the packages should track stable releases unless there are security issues or breakage that cannot easily be backported. Not sure why the arch tensorflow package tracks the release candidates. As it stands, I would rather track the stable releases and let those interested in the most recent features upgrade on their own, but I'm not opposed to upgrading to the tfp-rc if any breakage is found since it is tested against the tf-rc.

Wasn't sure wether to flag the package out of date. Technically the package is not out-of-date, but since Arch has updated now python-tensorflow to 2.3rc2, you'll need version 0.11rc1 of this package in order to run.

I've installed:
https://github.com/tensorflow/probability/archive/v0.11.0-rc1.tar.gz
sha256sum: 24ceceffc3d1380d8aef16e7632f2ef856f94a480ac33a6fd670a91e6fec5d34

Also, now there is also a dependence on dm-tree.

Bazel requires OpenJDK 11, so the installation would fail on systems that had a different java environment set as default. I've updated the PKGBUILD to point to the specific version of java.

Bazel is unfortunately required, as it generates a bunch of python files before packaging with setuptools

I get the error:

==> Starting build()...
WARNING: The following rc files are no longer being read, please transfer their contents or import their path into one of the standard rc files:
/home/will/.cache/yay/python-tensorflow-probability/src/probability-0.9.0/tools/bazel.rc
Extracting Bazel installation...
FATAL: Could not find system javabase. Ensure JAVA_HOME is set, or javac is on your PATH.

I get the following error:

==> Starting build()...
WARNING: The following rc files are no longer being read, please transfer their contents or import their path into one of the standard rc files:
/home/trougnouf/.cache/pacaur/python-tensorflow-probability/src/probability-0.9.0/tools/bazel.rc
INFO: Analyzed target //:pip_pkg (55 packages loaded, 2023 targets configured).
INFO: Found 1 target...
ERROR: /home/trougnouf/.cache/pacaur/python-tensorflow-probability/src/probability-0.9.0/tensorflow_probability/python/internal/backend/numpy/BUILD:402:2: Executing genrule //tensorflow_probability/python/internal/backend/numpy:rewrite_linear_operator_zeros failed (Exit 1) bash failed: error executing command /bin/bash -c ... (remaining 1 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox
2020-02-06 13:37:01.168467: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.2
[benoit-intoPIXPC:00011] PMIX ERROR: ERROR in file dstore_segment.c at line 201
[benoit-intoPIXPC:00011] PMIX ERROR: OUT-OF-RESOURCE in file dstore_base.c at line 693
[benoit-intoPIXPC:00011] PMIX ERROR: OUT-OF-RESOURCE in file dstore_base.c at line 1833
[benoit-intoPIXPC:00011] PMIX ERROR: OUT-OF-RESOURCE in file dstore_base.c at line 2761
[benoit-intoPIXPC:00011] PMIX ERROR: OUT-OF-RESOURCE in file dstore_base.c at line 2809
[benoit-intoPIXPC:00011] PMIX ERROR: OUT-OF-RESOURCE in file server/pmix_server.c at line 3334
[benoit-intoPIXPC:00003] PMIX ERROR: OUT-OF-RESOURCE in file client/pmix_client.c at line 227
[benoit-intoPIXPC:00003] OPAL ERROR: Error in file pmix3x_client.c at line 112
*** An error occurred in MPI_Init_thread
*** on a NULL communicator
*** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
***    and potentially your MPI job)
[benoit-intoPIXPC:00003] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed!
Target //:pip_pkg failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 4.634s, Critical Path: 2.66s
INFO: 0 processes.
FAILED: Build did NOT complete successfully
==> ERROR: A failure occurred in build().
    Aborting...
:: failed to build python-tensorflow-probability package(s)