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
google-cloud-sdk: 281.0.0 -> 286.0.0 #83509
Conversation
Every upgrade makes me quite uncomfortable because the python code is shelling out to other programs and I don't have a high confidence that it will keep working as before. Does anyone have an idea on how the situation could be improved? |
Can we map out the places where those outwards calls happen? Do we have any examples? |
It's in many different places, but I don't really see a way for us to keep track of all these on every bump:
If there was a central place about what binaries google-cloud-sdk shells out, it'd be a different story, but for now I'd say we do some minimal testing, then merge bumps and fix eventual breakages once they're reported. We can't test everything, and fixing up things once they are reported is probably better than staying with an old version, just because we feel comfortable with it. |
If the package was compiled from source then we could run the tests and hopefully detect more failures upfront? |
Motivation for this change
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)