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
Upgrade MPFR, MPC and MPFI #24353
Comments
Branch: u/jdemeyer/upgrade_to_mpfr_4_0_0 |
comment:3
As reported on the MPFR mailing list by other people, this breaks MPC:
New commits:
|
Commit: |
This comment has been minimized.
This comment has been minimized.
Author: Jeroen Demeyer |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Upstream: Reported upstream. No feedback yet. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:9
Fabrice Rouillier tells me he is preparing the release of MPFI 1.5.2. Stay tuned! |
comment:10
Replying to @zimmermann6:
Is this personal communication or is this on some public channel? In the latter case, do you have a link? |
comment:11
it is personal communication. If/when I have some information about a release candidate, |
comment:12
MPFI 1.5.2 is available from https://gforge.inria.fr/frs/?group_id=157 |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:16
There are a few obvious doctest failures in |
comment:17
I am curious to know which failures you get. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:19
I added a few fixes in the last commit. With this, all tests pass. So, this ticket is technically needs_review, modulo the fact that there is no MPC release yet... |
comment:20
in the last commit:
"not supported for every operation" is not correct: it is supported, but not guaranteed correct for every operation. Apart from that, I am ok with this commit. We expect to release MPC 1.1 this week or next week. |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Reviewer: Paul Zimmermann |
comment:22
Replying to @zimmermann6:
Fixed.
OK, I'm adding you as reviewer. |
comment:23
MPC 1.1.0 is now available from https://ftp.gnu.org/gnu/mpc |
This comment has been minimized.
This comment has been minimized.
comment:27
all tests pass on quasar (ubuntu x86_64) |
Changed upstream from Reported upstream. No feedback yet. to none |
comment:29
I did:
and got an error:
|
comment:30
You need to manually download the 3 tarballs mentioned on this ticket and put them in the |
comment:31
modulo the fact that the patchbot is happy, I give a positive review. |
Changed branch from u/jdemeyer/upgrade_to_mpfr_4_0_0 to |
Tarballs:
CC: @zimmermann6 @kiwifb
Component: packages: standard
Author: Jeroen Demeyer
Branch/Commit:
3c089ff
Reviewer: Paul Zimmermann
Issue created by migration from https://trac.sagemath.org/ticket/24353
The text was updated successfully, but these errors were encountered: