DavHau / mach-nix

Create highly reproducible python environments
MIT License
858 stars 105 forks source link

(Question) What to do if a packages requirements are not quite known (yet) - to answer myself #57

Open 573 opened 4 years ago

573 commented 4 years ago

Let's say I have a list of requirements in a mach-nix.mkPython block and the build complains along the lines of

ERROR: Could not find a version that satisfies the requirement packaging (from Sphinx==2.3.1) (from versions: none) ERROR: No matching distribution found for packaging (from Sphinx==2.3.1) builder for '/nix/store/y8y8x98zyyczp66gcy2pv7ds3bxadl8b-python3.7-sphinx-2.3.1.drv' failed with exit code 1

I already have providers = { sphinx = "nixpkgs"; };.

573 commented 4 years ago

See log.

Just add Sphinx as in

requirements  = ''
  Sphinx
'';
DavHau commented 4 years ago

That's strange. It means that there is some requirement specification of a package which is not recognized by nix, but by the python installation procedure. This needs more investigation.

573 commented 4 years ago

I cannot say which other package on my list introduced the sphinx requirement. When getting the error (log above) I searched the internet for requirements sphinx had found no requirements.txt and then more or less copied what was listed here

DavHau commented 4 years ago

Could you provide the original list of requirements that caused the error from the first post?

573 commented 4 years ago

By the end of the week.

573 commented 4 years ago

The list of requirements is as in this file. The rest of my config as mentioned in this issue comment (#58).