* pytorch-0.3 with optional cuda and cudnn
* pytorch tests reenabled if compiling without cuda
* pytorch: Conditionalize cudnn dependency on cudaSupport
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
* pytorch: Compile with the same GCC version used by CUDA if cudaSupport
Fixes this error:
In file included from /nix/store/gv7w3c71jg627cpcff04yi6kwzpzjyap-cudatoolkit-9.1.85.1/include/host_config.h:50:0,
from /nix/store/gv7w3c71jg627cpcff04yi6kwzpzjyap-cudatoolkit-9.1.85.1/include/cuda_runtime.h:78,
from <command-line>:0:
/nix/store/gv7w3c71jg627cpcff04yi6kwzpzjyap-cudatoolkit-9.1.85.1/include/crt/host_config.h:121:2: error: #error -- unsupported GNU version! gcc versions later than 6 are not supported!
#error -- unsupported GNU version! gcc versions later than 6 are not supported!
^~~~~
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
* pytorch: Build with joined cudatoolkit
Similar to #30058 for TensorFlow.
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
* pytorch: 0.3.0 -> 0.3.1
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
* pytorch: Patch for “refcounted file mapping not supported” failure
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
* pytorch: Skip distributed tests
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
* pytorch: Use the stub libcuda.so from cudatoolkit for running tests
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
The latest update of `yowsup` (https://github.com/tgalal/yowsup/releases/tag/v2.5.7)
contains the following fixes:
* Updated tokens
* Fixedtgalal/yowsup#1842: Bug in protocol_groups RemoveGroupsNotificationProtocolEntity
* Other minor bug fixes
The `argparse-dependency.patch` required a rebase onto the latest
version of `setup.py` and ensures that `argparse` won't be needed as
extra dependency as our `python3` package ships `argparse` by default.
A short note to Python 2 support:
the actual issue related to Python 2.x support has been resolved
(https://github.com/tgalal/yowsup/issues/2325#issuecomment-354533727),
however this relies on `six==1.10` which isn't support by `nixpkgs` as
`six` has been bumped to `1.11`. When trying to inject a patched version
of our `six` package based on `six==1.10` you'll run into issues with
duplicated libraries in your closure as further build dependencies
(`pytest` in this case) use the latest `six` version. As Python 2.7 will
die in 2020 (https://pythonclock.org/) and patching around in the
dependencies of `pytest` to get `yowsup` running isn't worth the effort
in my opinion I decided to keep the Python 2.x build disabled for now.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/apktool/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/x2im0ff8abgj4zp2al9v7339b4lqm7y2-apktool-2.3.3/bin/apktool -h’ got 0 exit code
- ran ‘/nix/store/x2im0ff8abgj4zp2al9v7339b4lqm7y2-apktool-2.3.3/bin/apktool --help’ got 0 exit code
- ran ‘/nix/store/x2im0ff8abgj4zp2al9v7339b4lqm7y2-apktool-2.3.3/bin/apktool help’ got 0 exit code
- ran ‘/nix/store/x2im0ff8abgj4zp2al9v7339b4lqm7y2-apktool-2.3.3/bin/apktool --version’ and found version 2.3.3
- found 2.3.3 with grep in /nix/store/x2im0ff8abgj4zp2al9v7339b4lqm7y2-apktool-2.3.3
- directory tree listing: https://gist.github.com/442f8aae9c8a9a0f7594fc049c97fe51
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/opendht/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtnode -h’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtnode --help’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtnode help’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtchat -h’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtchat --help’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtchat help’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtscanner -h’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtscanner --help’ got 0 exit code
- found 1.7.1 with grep in /nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1
- directory tree listing: https://gist.github.com/a3f2bc9f76c4720e3fec78139e60c160
To mitigate Spectre Variant 2, GCC needs to have retpoline
support (-mindirect-branch and -mfunction-return arguments on amd64
and i386).
Patches were pulled from H.J. Lu's backport branch to
4.9 (hjl/indirect/gcc-4_9-branch), available at
https://github.com/hjl-tools/gcc/tree/hjl/indirect/gcc-4_9-branch/master. Upstream
GCC does not apply patches to anything older than the
gcc-6-branch. H.J. Lu is the author of the upstream retpoline commits
as well.
Several Linux distributions already backported these patches to GCC 4
branches and some old kernels (3.13 for instance) have been recompiled
with these GCC patches. These kernels only allow to load kernel
modules that are compiled with the retpoline support.
References:
- Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1749261
- Ubuntu package: https://launchpad.net/ubuntu/+source/gcc-4.8/4.8.4-2ubuntu1~14.04.4Fixes#38394
blank-canvas-0.6.3 depends on base-compat-batteries-0.10, which
depends on base-compat-0.10. This conflicts with the rest of the LTS
set, which uses base-compat-0.9. No base-compat-batteries-0.9 exists.
blank-canvas-0.6.2 only depends on base-compat >= 0.8 && < 0.10.