Skip to content

Conversation

orlitzky
Copy link
Contributor

@orlitzky orlitzky commented Nov 18, 2023

We currently check for either pari-2.5.14, or an unofficial (patched) version of pari-2.5.13 that is missing two bugs present in the upstream release. However, one of those bug-checks fails on macOS, making it impossible to use the system pari there.

pari-2.5.14 has been out for a few months. Any distro fast enough to have backported patches to pari-2.5.13 will likely have pari-2.5.14 by now. On that assumption, we simply require pari-2.5.14 to fix the macOS issue, and hope it does not affect anyone still using a patched pari-2.5.13.

We currently check for either pari-2.5.14, or an unofficial (patched)
version of pari-2.5.13 that is missing two bugs present in the
upstream release. However, one of those bug-checks fails on macOS,
making it impossible to use the system pari there.

pari-2.5.14 has been out for a few months. Any distro fast enough to
have backported patches to pari-2.5.13 will likely have pari-2.5.14 by
now. On that assumption, we simply require pari-2.5.14 to fix the
macOS issue, and hope it does not affect anyone still using a patched
pari-2.5.13.
Copy link

Documentation preview for this PR (built with commit d76d272; changes) is ready! 🎉

@jhpalmieri
Copy link
Member

It looks great to me, but I really only use OS X + homebrew. I think we need feedback from people on other platforms about which versions of pari are standard these days.

@orlitzky
Copy link
Contributor Author

You can get some idea here: https://repology.org/project/pari/versions

The only people affected are those with a patched pari-2.15.3. One would have to go digging to find out which patches are applied on the few distros that still have 2.15.3.

I'm a strong proponent of supporting multiple versions of things, but patching them in sage and then requiring everyone else to apply the same patches and checking for them in ./configure isn't the way to go about it. This version has sailed.

@jhpalmieri
Copy link
Member

You can get some idea here: https://repology.org/project/pari/versions

What do the colors mean in that table? In particular, why are some of the 2.15.3 yellow and some red?

@orlitzky
Copy link
Contributor Author

You can get some idea here: https://repology.org/project/pari/versions

What do the colors mean in that table? In particular, why are some of the 2.15.3 yellow and some red?

The red ones are where no newer version is available on that distro. The yellow ones are where an old version exists, but a newer one is available too. (They key is on the repology homepage).

For example, the Fedora 38 release has a yellow v2.15.13 because 2.15.14 is also available via the updates channel.

@jhpalmieri
Copy link
Member

Okay, let's move ahead with this.

@jhpalmieri
Copy link
Member

Note: should fix #36729.

@dimpase
Copy link
Member

dimpase commented Dec 6, 2023

On Homebrew, one just has to install coreutils (as we do on all the Linux systems).
Then timeout is there.

@vbraun vbraun merged commit 80f0ea5 into sagemath:develop Dec 10, 2023
@orlitzky orlitzky deleted the require-pari-2.15.4 branch January 24, 2024 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

OS X: system Pari is rejected because of unknown shell command
5 participants