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: 5.3.0 -> 6.0.2 #110091
mitmproxy: 5.3.0 -> 6.0.2 #110091
Conversation
Result of 1 package failed to build:
2 packages built:
|
If this update requires more changes you could open a new PR so that you can easily apply those. |
python37Packages.mitmproxy failure is due to dropped support for python <=3.7 |
compiles, starts, seems to work on Gentoo amd64 sandbox=true |
At first glance there are some install requirements are missing at least |
@fabaff Would you mind opening your own PR? |
Closed in favor of #113948. |
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/mitmproxy/versions.
meta.description for mitmproxy is: "Man-in-the-middle proxy"
meta.homepage for mitmproxy is: "https://mitmproxy.org/"
meta.changelog for mitmproxy is: ""
Updates performed
To inspect upstream changes
Impact
Checks done (click to expand)
built on NixOS
The tests defined in
passthru.tests
, if any, passed0 of 0 passed binary check by having a zero exit code.
0 of 0 passed binary check by having the new version present in output.
found 6.0.2 with grep in /nix/store/184y4cvysswzf66nmjrjdn6d621c66bd-python3.8-mitmproxy-6.0.2
directory tree listing: https://gist.github.com/b5545b445c6c3c52c84739406914a19e
du listing: https://gist.github.com/97265047a70f0ab5af146ec2c2c14dcd
Rebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from Cachix:
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-users
list or you can usesudo
since root is effectively trusted.Or, build yourself:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of
nixpkgs-review
run on x86_64-linux 11 package failed to build:
2 packages built:
Maintainer pings
cc @fpletz @kamilchm for testing.