The hash used for fetchFromGitHub was on the archive itself, however
fetchFromGitHub is actually a wrapper of fetchzip:
hash mismatch in fixed-output derivation '...-source':
wanted: sha256:1zqx3p9l22njni44ads3fyw3xh6807wmb5k1x2glg61z81cwc6sf
got: sha256:08lnq5wmspfqdjmqm15gizcq0xr7mg4h62qhvwj63v0sd6ks1cal
When using nix-prefetch-url without the --unpack argument, I get:
1zqx3p9l22njni44ads3fyw3xh6807wmb5k1x2glg61z81cwc6sf
And with the --unpack argument:
08lnq5wmspfqdjmqm15gizcq0xr7mg4h62qhvwj63v0sd6ks1cal
Just to be 100% sure the contents are the same, I also diffed the
contents of the former tarball with the outputs of the unpacked dir and
they're the same.
I didn't actually test the package (which doesn't build right now
anyway), but now at least the source checksum is fixed :-)
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @matthiasbeyer
* python3Packages.papis: provides as a library too
The project is turning into a dependency for several scripts and possibly UIs
(see the different repositories at https://github.com/papis/) so it makes sense
to have it as a library.
* moved papis to python-modules
* add myself as maintainer
pipenv nix wrapper contains a PYTHONPATH which has some dependencies
for pipenv installed. pipenv by default uses site-packages when
resolving packages, which means that any package that is included in
the nix wrapper is satisfied when running `pipenv install`.
But when the actual virtualenv created by pipenv is activated, it
doesn't contain those packages anymore and fails to import them.
pipenv has a flag PIP_IGNORE_INSTALLED which can be used to ignore
site-packages. Which fixes the problem of having different resolved
packages when running pipenv and when running the virtualenv.
