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
mpfr: 3.1.6 -> 4.0.1 #36620
mpfr: 3.1.6 -> 4.0.1 #36620
Conversation
Success on x86_64-darwin (full log) Partial log (click to expand)
|
Failure on x86_64-linux (full log) Partial log (click to expand)
|
Stdenv change. Definitely should go into staging. Not sure if it should be an upgrade or an addition of |
Success on aarch64-linux (full log) Partial log (click to expand)
|
Semi-automatic update. These checks were done: - built on NixOS - Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.) - found 4.0.1 with grep in /nix/store/gpsg0bpw02hpc8hddjnirpnvsp7n4ak8-mpfr-4.0.1 - found 4.0.1 in filename of file in /nix/store/gpsg0bpw02hpc8hddjnirpnvsp7n4ak8-mpfr-4.0.1
Failure on x86_64-darwin (full log) Partial log (click to expand)
|
Failure on x86_64-linux (full log) Partial log (click to expand)
|
Build failure is just a timeout. |
Success on aarch64-linux (full log) Partial log (click to expand)
|
Should we maybe create a hydra jobset to test this upgrade? The major version changelog is here. Skimming it, this seems to be potentially interesting:
|
One datapoint: arch only packages mpfr 4.0.1, so it should not be very problematic. |
While rebuilding sage with this update applied, I noticed that |
This can be closed (#39578). |
Semi-automatic update. These checks were done: