Change:
Steps to reproduce the behavior: trueseeing dependency check fails due to missing termcolor. Full logs : <summary<details<preSourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts- Sourcing python-remove-bin-bytecode- Sourcing pypa-build-hook Using pypaBuildPhase Sourcing python-runtime-deps-check-hook Using pythonRuntimeDepsCheckHook Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check- Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts- { "action": "setPhase", "phase": "unpackPhase" } Running phase: unpackPhase unpacking source archive /nix/store/p05bg72wb6ihkj9jjmdgzsnjifd0m0ar-source source root is source setting SOURCEDATEEPOCH to timestamp of file { "action": "setPhase", "phase": "patchPhase" } Running phase: patchPhase { "action": "setPhase", "phase": "updateAutotoolsGnuConfigScriptsPhase" } Running phase: updateAutotoolsGnuConfigScriptsPhase { "action": "setPhase", "phase": "configurePhase" } Running phase: configurePhase no configure script, doing nothing { "action": "setPhase", "phase": "buildPhase" } Running phase: buildPhase Executing pypaBuildPhase Creating a wheel... Getting build dependencies for wheel... Building wheel... Successfully built trueseeing-2.1.9-py3-none- Finished creating a wheel... Finished executing pypaBuildPhase { "action": "setPhase", "phase": "pythonRuntimeDepsCheckHook" } Running phase: pythonRuntimeDepsCheckHook Executing pythonRuntimeDepsCheck Checking runtime dependencies for trueseeing-2.1.9-py3-none- termcolor not installed </pre</details</summaryAdd any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs: I believe trueseeing is missing the termcolor dependency hence the failure happening during the build. I can try and PR a fix but I did not try and reproduce the bug under NixOS. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Seems a lot of other packages have broken in similar ways, mitmproxy, ioccheck, theharvester but they all fail due to missing runtime dependencies or version of modules that are not meeting constraints.
I had the same issue with mitmproxy and found this issue because you've mentioned it here. ~git bisect for mitmproxy pointed to this commit for me: ~ Edit: apologies, I used git bisect wrongly. The first bad commit seems to be .
This seems relevant:
That shouldn't change whether or not a package builds.
Yeah, my nightly session of bisecting for pointed to , which is from . I guess affected packages do have to be fixed one-by-one manually.

Discussion:
hash = "sha256-g5OqdnPtGGV4wBwPRAjH3lweguwlfVcgpNLlq54OHKA="; }; <del> postPatch = '' substituteInPlace pyproject.toml  --replace "attrs~=21.4" "attrs>=21.4" ''; </del> nativeBuildInputs = with python3.pkgs; [ flit-core <ins> pythonRelaxDepsHook </ins> ]; <ins> pythonRelaxDeps = true; </ins> propagatedBuildInputs = with python3.pkgs; [ attrs <del> ipython </del> jinja2 lxml pypubsub pyyaml <ins> termcolor </ins> ]; # Project has no tests