* 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.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/umockdev/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-run -h’ got 0 exit code
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-run --help’ got 0 exit code
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-run --version’ and found version 0.11.3
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-record -h’ got 0 exit code
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-record --help’ got 0 exit code
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-record --version’ and found version 0.11.3
- found 0.11.3 with grep in /nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3
- directory tree listing: https://gist.github.com/3dcf7f53d51ca4a9c739e567456cb16f
For details on the patches applied, see:
https://sources.debian.org/patches/ltrace/0.7.3-6/
Disabling '-Werror' may be a problem in the future again,
but for now keep things simple now that they're fixed.
"platforms.gnu" has been linux-only since at least 17.03:
$ nix eval -f channel:nixos-17.03 lib.platforms.gnu
[ "i686-linux" "x86_64-linux" "armv5tel-linux" "armv6l-linux" "armv7l-linux" "aarch64-linux" "mips64el-linux" ]
Unlike platforms.linux, platforms.gnu indicates "must use glibc"
which for the most part is not intended.
Replacing platforms.gnu with platforms.linux would be the same "today"
but let's err on preserving existing behavior and be optimistic
about platforms these packages work on.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/kotlin/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/5byxycv5j3gvwvr87qpv08a7347fxv9q-kotlin-1.2.41/bin/kotlin -h’ got 0 exit code
- ran ‘/nix/store/5byxycv5j3gvwvr87qpv08a7347fxv9q-kotlin-1.2.41/bin/.kotlin-wrapped -h’ got 0 exit code
- found 1.2.41 with grep in /nix/store/5byxycv5j3gvwvr87qpv08a7347fxv9q-kotlin-1.2.41
- directory tree listing: https://gist.github.com/927e0c1e045ca7c165603ae8b1961beb
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/spidermonkey/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/47rbdzbgccrrdc63fnsnwklria9clmms-spidermonkey-52.7.4/bin/js52 -h’ got 0 exit code
- ran ‘/nix/store/47rbdzbgccrrdc63fnsnwklria9clmms-spidermonkey-52.7.4/bin/js52 --help’ got 0 exit code
- ran ‘/nix/store/47rbdzbgccrrdc63fnsnwklria9clmms-spidermonkey-52.7.4/bin/js52 -v’ and found version 52.7.4
- ran ‘/nix/store/47rbdzbgccrrdc63fnsnwklria9clmms-spidermonkey-52.7.4/bin/js52 --version’ and found version 52.7.4
- ran ‘/nix/store/47rbdzbgccrrdc63fnsnwklria9clmms-spidermonkey-52.7.4/bin/js52-config --version’ and found version 52.7.4
- found 52.7.4 with grep in /nix/store/47rbdzbgccrrdc63fnsnwklria9clmms-spidermonkey-52.7.4
- directory tree listing: https://gist.github.com/7e5182415a0a1bce8071576312c08a3a
I still feel weird about doing this because it seems a little hacky
but this was requested by @Mic92 and seems understandable to not want
to mix up libressl outputs with netcat stuff.
@7c6f434c wrote in [1]:
Maybe copy-paste the upstream "Alkimia is the infrastructure for
common storage and business logic that will be used by all financial
applications in KDE. The target is to share financial related
information over application bounderies." as longDescription for
Alkimia? The current description makes me want to look up the
homepage to find out what it actually is (then I do, and despair).
[1]: https://github.com/NixOS/nixpkgs/pull/39647#issuecomment-385169261
Signed-off-by: aszlig <aszlig@nix.build>
This is used by KMyMoney and also the reason why I needed to add C++
support to MPIR in the parent commit.
The reason why I didn't add myself as a maintainer is because I'm not
personally using KMyMoney and thus Alkimia.
Signed-off-by: aszlig <aszlig@nix.build>
This is one of the requirements of KMyMoney and packaging is quite
straightforward with no unexpected traps.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @ttuegel
This is needed by Alkimia which I'm going to package soon as part of
KMyMoney.
I enabled this by default, because it doesn't increase the closure size
a whole lot (only around 150 KiB):
$ nix-store -q --size /nix/store/...old...-mpir-3.0.0
1223248
$ nix-store -q --size /nix/store/...new...-mpir-3.0.0
1377136
Introducing an option for enabling/disabling this is not worth it,
because it doesn't conflict with anything and the size increase is the
only drawback and we can still make it configurable if we want someday.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @7c6f434c
Apparently, without this patch `NT_PRSTATUS` is not found. So the patch
adds the include apparently necessary. `NT_PRSTATUS` is also defined in
`<linux/ptrace.h>`, which would likely have been a better name, were it
not in the `linux/` directory, which is a priori not stable.
The need to do that is kind of weird (the change was introduced in [1],
and fedora apparently didn't need this additional import), but I'll try
to upstream it.
[1] https://github.com/SimonKagstrom/kcov/pull/239
Unfortunately I haven't found a way for nose to disable doctests and the
-e/--exclude flag only works on unit tests.
So I'm using sed in postPatch to remove the doctests without mangling
the whole docstring.
I've built weboob and it now succeeds.
Signed-off-by: aszlig <aszlig@nix.build>
