* slurm: 17.11.5 -> 17.11.7, pyslurm: 20180427 -> 20180604
This commit also swaps to use the official repository's github release tags
instead of their download site, which only keeps the most recent version with no
historical archives.
* Document why we don't run tests
* Remove dead testing code
Bazel is a build tool, much like Make and many others. Like Make, it
should be agnostic to the compiler toolchains the user brings into
scope. Bazel has special rules that encode domain specific knowledge
for how to compile a C++ program, or indeed a Java program and a few
others. But that's not to say that at runtime Bazel should assume
a specific C++ compiler or Java compiler anymore than Make does.
The main impact of this change is that packages that build with Bazel
will have to list the compilers they want in their `buildInputs` or
similar, rather than relying on the `bazel` package pulling them in
transitively.
* rpcs3: 0.0.4-8032 -> 0.0.5-6884
* rpcs3: update hash
* rpcs3: 0.0.5-6884 -> 0.0.5-6925
* rpcs3: 0.0.5-6925 -> 0.0.5-6938
* rpcs3: 0.0.5-6938 -> 0.0.5-6980
Manually write version header instead of generating it with git, which required leaveDotGit to be enabled.
This caused some hash mismatches (see #8567) has thus been disabled.
This reverts commit 2624f9079617df6b1fffda8c10f6a7a35068ecdc, reversing
changes made to 37aab4cbb5552bf021b20cf05d64e8ded6f3538a.
See:
https://github.com/NixOS/nixpkgs/pull/42376#issuecomment-399789096
Basically this breaks at least some users of fetchgit,
so let's revert this until this is sorted out.
gopass tries to write a version number to it's configuaration, even when
just generating the shell completion scripts. This fails, as
/homeless-shelter is read-only inside the sandbox.
As error messages are printed to stdout instead of stderr
(see https://github.com/gopasspw/gopass/issues/877), the error message
lands inside the completion script, thus breaking it.
Workaround that by setting GOPASS_CONFIG to `/dev/null`
