-
-
Notifications
You must be signed in to change notification settings - Fork 15.5k
python37Packages.cypari2: 2.1.1 -> 2.1.2 #103810
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
Conversation
CC @omasanori |
@timokau maybe make a sage team? |
Are maintainer teams a thing now? |
Thank you for notification! |
Regarding cypari2, by the way, I would wait for the resolution of the upstream ticket #30801 (Upgrade: pari 2.13, cypari2 2.1.2) – Sage. |
Neat! Created the maintainers team in #104083. |
Maintaining all the packages whose updates might break some aspect of sage. For reference: NixOS#103810 (comment)
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python37Packages.cypari2 is: "Cython bindings for PARI"
meta.homepage for python37Packages.cypari2 is: "https://github.com/defeo/cypari2"
meta.changelog for python37Packages.cypari2 is: ""
Updates performed
To inspect upstream changes
Impact
Checks done (click to expand)
built on NixOS
Warning: a test defined in
passthru.tests
did not pass0 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 2.1.2 with grep in /nix/store/b4c90k1wvb0ks5arwsc4bzqaxgmakkv4-python3.7-cypari2-2.1.2
directory tree listing: https://gist.github.com/a25d11ec31c953c154f2d0bfa930bbb0
du listing: https://gist.github.com/cba62abf3c60b0d16650be66c38a37aa
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.
nixpkgs-review took longer than 45m and timed out
Maintainer pings
cc @timokau for testing.