In reply to @rolandco:matrix.org
I'm working on a script to fix the overrides for some common problems. I created a recent PR for fixing a package called twisted. Three questions:
1) Would that be useful? So far I have identified thousands of commonly downloaded packages failing.
2) is the use of from and until in the build systems json preferred to list of dependencies?
3) I see some checks failing, unrelated to the package I'm fixing. Should I fix those?

1. Absolutely. There are far too many packages for any individual to keep track of all the non-Python dependencies and missing dependencies.
2. Generally, yes, but if that's too much work simply having the dependencies at all is better than not having them.
3. If you can, that would be great. Splitting your work into multiple PRs would be appreciated, though, since the difficulty of reviewing scales by something like O(N²) for N lines.

In reply to @nirudium:matrix.org
Are there any examples of mkPoetryScriptsPackage I could use because I'm trying to set up a single python script and installing it via a flake but I haven't figured that out yet haha