-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Old Package Versions Causing Build Failures on NixOS #2458
Comments
👋 @CountingBeeps |
Thanks for reporting, Looks like a couple of them were unnecessarily pinned. Updated that in 555b663 bcrypt is a special case, We do not need it directly, but used by mitmproxy and it throws an error on newer versions.
Also as a heads up, there are few other dependencies that needs to be available in the host OS if you are not using the docker container. |
Thanks for the quick response. That change should address all of the issues I was facing. Good to know about bcrypt, and thanks for the heads up. |
Fixed in v4.2.5 |
ENVIRONMENT
EXPLANATION OF THE ISSUE
First, apologies if this does not quite qualify as a bug, it is an edge case in my view. I was trying to package this for NixOS, as the docker is not ideal for the way nix is setup. In the pyproject.toml while most of the packages are set to a range, a few of the packages are pinned to specific versions that are causing issues.
Specifically:
and to a much lesser extent
For openstep-parser, this is a really old version of this package, and there does no appear to be any api changes, so I can't tell if there is a real reason it is pinned to this. It is old enough that it uses some dependencies that are past the depreciation period, and therefore will no longer build at all on nix.
And for a reason I can't determine, packaging version 21.3 will not build either.
If there is a reason bcrypt is pinned, unlike the other two I can work around it, so it is not a major issue. More of a minor inconvenience than anything else.
I was wondering if these could be updated to a newer version (every version after those builds still), or have their version ranges opened up by >= to allow for the packaging build issues to be resolved.
The text was updated successfully, but these errors were encountered: