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
mitmproxy: 4.0.4 -> 5.0.1 #78052
mitmproxy: 4.0.4 -> 5.0.1 #78052
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I couldn't build it without additional deps in check phase e9e0db1
6a23266
to
edabea9
Compare
@kamilchm Thanks, I've updated the code. Not sure why my macOS build passed without those dependencies... |
is there still anything to be done by me here? |
Why are you adding the Python dependencies here instead of in python3Packages? |
@alyssais no particular reason, I can move them python3Packages if it's better to have them there |
Artur Cygan <notifications@github.com> writes:
@alyssais no particular reason, I can move them python3Packages if
it's better to have them there
That's certainly what's usually done in Nixpkgs.
|
Looks like it's been already updated in #85458 |
Motivation for this change
New mitmproxy release https://mitmproxy.org/posts/releases/mitmproxy5/.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)