-
-
Notifications
You must be signed in to change notification settings - Fork 519
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
Update FriCAS to 1.3.6 #27309
Comments
comment:1
Ticket retargeted after milestone closed (if you don't believe this ticket is appropriate for the Sage 8.8 release please retarget manually) |
comment:2
As the Sage-8.8 release milestone is pending, we should delete the sage-8.8 milestone for tickets that are not actively being worked on or that still require significant work to move forward. If you feel that this ticket should be included in the next Sage release at the soonest please set its milestone to the next release milestone (sage-8.9). |
comment:3
Fricas 1.3.6 was released. Release announcement: |
This comment has been minimized.
This comment has been minimized.
comment:4
In case you have time, could you check whether #27310 works? |
This comment has been minimized.
This comment has been minimized.
Commit: |
New commits:
|
Branch: u/chapoton/27309 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:9
Passes all doctests. This seems to be good to go. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:11
In -tarball=fricas-VERSION-full.tar.bz2
+tarball=fricas-VERSION.tar.gz |
comment:12
why ? |
comment:13
I see:
I don't think this the URL of a release tarball. This is just the automatic git archive corresponding to the tag. Upstream seems to continue using sourceforge for distributing release tarballs. |
comment:15
In that case do we need in
Or are these Sourceforge download urls problematic? |
This comment has been minimized.
This comment has been minimized.
comment:17
Ideally, rebase on Sage 9.2.beta9. |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:19
better like that ? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Changed author from Martin Rubey to Frédéric Chapoton |
Reviewer: Matthias Koeppe |
comment:23
Works for me on macOS. |
Changed reviewer from Matthias Koeppe to Matthias Koeppe, Samuel Lelièvre |
comment:24
Success on Debian too:
|
Changed branch from u/chapoton/27309 to |
Changed commit from |
comment:26
I now have problems with "sage -i fricas", which does not seem to be able to find the tarball in the mirrors.. |
This ticket is to upgrade to FriCAS 1.3.6 and track dependencies.
Tarball: see checksums.ini
Note that FriCAS has switched to using Git and the primary repository is now the one at GitHub, but the homepage remains at Sourceforge:
and we still get source tarballs from Sourceforge since those available at GitHub are not the full source archives we need.
Our last update was to Fricas 1.3.5 in #25962 in February 2019.
To try this ticket from your Sage root directory, with
git-trac-command
installed:git trac try 27309
SAGE_SPKG="sage-spkg -o" ./sage -i fricas
(or use./configure --enable-download-from-upstream-url
first)./sage -t --optional=fricas,sage src/sage/interfaces/fricas.py
CC: @slel
Component: packages: optional
Keywords: FriCAS, upgrade
Author: Frédéric Chapoton
Branch:
b811a1d
Reviewer: Matthias Koeppe, Samuel Lelièvre
Issue created by migration from https://trac.sagemath.org/ticket/27309
The text was updated successfully, but these errors were encountered: