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
Pari workarond for Perl regex deprecation #18872
Comments
Author: Volker Braun |
This comment has been minimized.
This comment has been minimized.
Changed branch from u/vbraun/pari_workarond_for_perl_regex_deprecation to none |
comment:5
From the |
Commit: |
New commits:
|
Reviewer: Jeroen Demeyer |
This comment has been minimized.
This comment has been minimized.
Upstream: Reported upstream. No feedback yet. |
comment:9
This patch works (although it gives 11152 deprecation warnings when auto-generating the PARI functions), but I'd rather wait a bit to give upstream a chance to fix this in a proper way. However, if you need to release Sage 6.8 very soon, you can merge this right away. |
Changed branch from u/vbraun/pari_workarond_for_perl_regex_deprecation to none |
Changed upstream from Reported upstream. No feedback yet. to Workaround found; Bug reported upstream. |
Changed author from Volker Braun to Volker Braun, Jeroen Demeyer |
Changed commit from |
Changed reviewer from Jeroen Demeyer to none |
comment:12
Applied upstream fix instead. New commits:
|
Commit: |
Reviewer: Volker Braun |
Changed branch from u/jdemeyer/pari_workarond_for_perl_regex_deprecation to |
Perl 5.21.1 throws warnings for unescaped '{', and pari treats warnings as errors by default. Patch taken from
https://projects.archlinux.org/svntogit/community.git/tree/trunk/no_warnings_fatal.patch?h=packages/pari-sage
Upstream report: http://pari.math.u-bordeaux.fr/cgi-bin/bugreport.cgi?bug=1726
Upstream: Workaround found; Bug reported upstream.
CC: @jdemeyer
Component: packages: standard
Author: Volker Braun, Jeroen Demeyer
Branch/Commit:
91665e9
Reviewer: Volker Braun
Issue created by migration from https://trac.sagemath.org/ticket/18872
The text was updated successfully, but these errors were encountered: