Conversation
|
Related: The eclib update patch has stabilized too, even if it hasn't been merged yet. Should we pull that in as well? My main motivation for doing |
5541c06 to
c4cc5a4
Compare
|
Result of 1 package marked as broken and skipped:
3 packages skipped due to time constraints:
16 packages built successfully:
Result of 6 packages skipped due to time constraints:
17 packages built successfully:
7 suggestions:
|
|
Result of 23 packages built:
|
timokau
left a comment
There was a problem hiding this comment.
Thanks for following up on this. I would prefer to delay the pari update until the sage ticket has been reviewed. It looks like this update is likely to cause trouble.
The other changes look good.
Which ticket is that? In general I think it would be better to merge this PR first. The eclib update could still be done as a followup. |
|
That's https://trac.sagemath.org/ticket/31443. I have split the pari update to #122624. |
|
Ah, I forgot about this conversation. That update sounds less risky than the pari update. I think there also isn't much urgency to it though, so I would probably wait a few days for updates on the sage ticket. Whichever way you prefer.
Thank you. Should be good to go now. |
timokau
left a comment
There was a problem hiding this comment.
Looks good, pending ofBorg's approval.
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/brainstorming-for-rfc-pname-and-version/12873/23 |
Motivation for this change
Also updated gap and pari while at it. Pari required an unmerged patch from Sage Trac, but the patch hasn't changed in two weeks so that should be fine. Let me know if I should remove it, though.
Things done
sandboxinnix.confon non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"./result/bin/)nix path-info -Sbefore and after)