Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Nix deps to incorporate latest Python packages #352

Merged
merged 1 commit into from
Feb 15, 2021

Conversation

rolfschr
Copy link
Contributor

As described in the readme section "Keeping the Nix setup in sync", this PR updates the pypi index reference in order to accommodate for the recent updates of Python deps, mainly pygit2==1.5.0 which got released 2021-01-23.

Currently, the github workflow fails but this seems to be unrelated to Nix (alpine import error)

Signed-off-by: Rolf Schröder <rolf.schr@gmail.com>
@sbs2001 sbs2001 merged commit 7f5ebf2 into nexB:main Feb 15, 2021
@rolfschr rolfschr deleted the update-nix-deps branch February 15, 2021 19:34
@InLaw
Copy link
Contributor

InLaw commented Mar 8, 2021

e.g. black>19.3b0

but even with that version vulnerablecode will fail

error: --- Error --- nix
error: --- Error --- nix-daemon
builder for '/nix/store/hp49hf2d77xy30lg39klrxk5hslsjzvp-vulnerablecode-20.10-test.drv' failed with exit code 1; last 10 log lines:
      self.warn("could not create cache path {path}", path=path)
  
  /nix/store/c2yp70x0x41myhcqrzwfpc7x0q20c1rb-python3-3.8.5-env/lib/python3.8/site-packages/_pytest/cacheprovider.py:137
    /nix/store/c2yp70x0x41myhcqrzwfpc7x0q20c1rb-python3-3.8.5-env/lib/python3.8/site-packages/_pytest/cacheprovider.py:137: PytestCacheWarning: could not create cache path /nix/store/qlmcrzajxhskbcc3i2k81nyvxdbas18j-vulnerablecode-20.10/.pytest_cache/v/cache/lastfailed
      self.warn("could not create cache path {path}", path=path)

why do you cache in nix/store instead of e.g. /tmp?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants