According to @zimbatm, he got the SHA256 hashes via nix-prefetch-git.
However, fetchFromGitHub doesn't use Git to fetch the sources but uses
fetchzip under the hood, so we get plain source directories in the Nix
store, which in turn are hashed.
Tested by:
nix-build --no-out-link -E 'map (x:
(builtins.getAttr x (import ./. {})).src
) [ "ruby_1_9_3" "ruby_2_0_0" "ruby_2_1_0" "ruby_2_1_1" "ruby_2_1_2"
"ruby_2_1_3" "ruby_2_1_6" "ruby_2_1_7" "ruby_2_2_0" "ruby_2_2_2"
"ruby_2_2_3"
]'
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This update was generated by hackage2nix v20150922-46-gf1bbc76 using the following inputs:
- Nixpkgs: 4619baf1f6
- Hackage: 4269955365
- LTS Haskell: 57dab1c997
- Stackage Nightly: 87110f79ed
(And while at it, gst-vaapi 0.6.0 -> 0.6.1.)
* gst-editing-services grew additional build time dependencies, flex and
perl.
* gst-libav switched from libav to ffmpeg as "libav" provider, see
http://gstreamer.freedesktop.org/releases/1.6/.
Without using ffmpeg, one may hit issues such as this (which I
initially did):
(gst-plugin-scanner:19751): GStreamer-WARNING **: Failed to load plugin '/nix/store/0wgpq2yx9wrkp2mh4rn1c7zbiq2bqa2l-gst-libav-1.6.1/lib/gstreamer-1.0/libgstlibav.so':
/nix/store/0wgpq2yx9wrkp2mh4rn1c7zbiq2bqa2l-gst-libav-1.6.1/lib/gstreamer-1.0/libgstlibav.so: undefined symbol: av_frame_get_sample_rate
This update was generated by hackage2nix v20150922-46-gf1bbc76 using the following inputs:
- Nixpkgs: 02a00be50f
- Hackage: 2c186df615
- LTS Haskell: 57dab1c997
- Stackage Nightly: c3ba1c0c15
I've removed the trivial command in 4e72b61de.
I think `install -Dt "$out/bin"` is a better replacement anyway,
as it can be easily used to other directories than $out/bin.
/cc @ehmry who seems to maintain many packages with this usage.
(BTW, it would be better to have maintainer attribute same as github
username, as it makes pinging maintainers much easier.)
This update was generated by hackage2nix v20150922-46-gf1bbc76 using the following inputs:
- Nixpkgs: 7c559e1c0f
- Hackage: 49a7fb0a6f
- LTS Haskell: 57dab1c997
- Stackage Nightly: ecefc78ca3
This update was generated by hackage2nix v20150922-46-gf1bbc76 using the following inputs:
- Nixpkgs: f9c10dd1aa
- Hackage: fda7f3f477
- LTS Haskell: 57dab1c997
- Stackage Nightly: a30c2abd60
pylint (using Python 2.7) got propagated into python3Packages.spyder
so Python 2.7 setup-hook was used instead of python34.
Now that pylint is part of pythonPackages attribute set, pylint is
used with python3.4 as a base.
This was preventing the Nixpkgs channel from updating, since the
program indexer barfed on:
error: anonymous function at /nix/store/wdnwbh3kmf68nhqqp0khcyxbdbp43vg5-nixos-14.12.626.b0d594c/nixos/nixpkgs/pkgs/top-level/node-packages.nix:1:1 called without required argument ‘neededNatives’, at /data/releases/nixos/unstable-small/.tmp-nixos-16.03pre72946.c50d013-787/unpack/nixos-16.03pre72946.c50d013/lib/customisation.nix:56:12
because Nixpkgs 16.03 was importing files from Nixpkgs 14.12.
Also added some half-assed checks to detect this issue in the future.
Without this, if compiled with clang, all static functions do not end
up in the resultant shared library due to clang defaulting to c99.
The simple fix is to adjust CFLAGS, otherwise one needs to patch
a lot of inline's away needlessly.
Currently, when constructing a buildEnv and adding packages via
extraLibs, then binaries in extraLibs cannot access the other Python
modules. An example is having ipython/jupyter in extraLibs; in that case
ipython cannot import any other modules.
This update was generated by hackage2nix v20150922-46-gf1bbc76 using the following inputs:
- Nixpkgs: 7b12664abe
- Hackage: 624aeb0d41
- LTS Haskell: 57dab1c997
- Stackage Nightly: dc4725639c
libevhtp: 1.2.10 -> 1.2.11
Package for certificate-transparency
This adds openssl support to libevent. Libevent can be compiled without
openssl, in which case it just doesn't build the libevent_openssl
library. However it seems simpler just to default to including openssl
support.
This bumps evhtp's version because 1.2.11 provides pkg-config
information which makes building certificate-transparency easier.
This has been tested with `doCheck = true;`.
Signed-off-by: Edward Tjörnhammar <ed@cflags.cc>
