#27309 closed enhancement (fixed)
Update FriCAS to 1.3.6
| Reported by: | Martin Rubey | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | sage-9.2 |
| Component: | packages: optional | Keywords: | FriCAS, upgrade |
| Cc: | Samuel Lelièvre | Merged in: | |
| Authors: | Frédéric Chapoton | Reviewers: | Matthias Koeppe, Samuel Lelièvre |
| Report Upstream: | N/A | Work issues: | |
| Branch: | b811a1d (Commits, GitHub, GitLab) | Commit: | |
| Dependencies: | Stopgaps: |
Status badges
Description (last modified by )
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 27309SAGE_SPKG="sage-spkg -o" ./sage -i fricas(or use./configure --enable-download-from-upstream-urlfirst)./sage -t --optional=fricas,sage src/sage/interfaces/fricas.py
Change History (26)
comment:1 Changed 4 years ago by
| Milestone: | sage-8.7 → sage-8.8 |
|---|
comment:2 Changed 3 years ago by
| Milestone: | sage-8.8 |
|---|
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 Changed 3 years ago by
| Cc: | Samuel Lelièvre added |
|---|---|
| Description: | modified (diff) |
| Milestone: | → sage-9.1 |
Fricas 1.3.6 was released. Release announcement:
comment:5 Changed 3 years ago by
| Milestone: | sage-9.1 → sage-9.2 |
|---|
comment:6 Changed 2 years ago by
| Description: | modified (diff) |
|---|
comment:7 Changed 2 years ago by
| Branch: | → u/chapoton/27309 |
|---|---|
| Commit: | → 29d0e0264e934c1ca0225511e1b8c6439b950366 |
| Status: | new → needs_review |
New commits:
| 29d0e02 | update fricas to 1.3.6
|
comment:8 Changed 2 years ago by
| Commit: | 29d0e0264e934c1ca0225511e1b8c6439b950366 → 086cbf0a5b0a76aa3e2413d884d6f22145ee3119 |
|---|
Branch pushed to git repo; I updated commit sha1. New commits:
| 086cbf0 | fix fricas doctest
|
comment:10 Changed 2 years ago by
| Description: | modified (diff) |
|---|
comment:11 Changed 2 years ago by
| Description: | modified (diff) |
|---|
In build/pkgs/fricas/checksums.ini maybe change:
-tarball=fricas-VERSION-full.tar.bz2 +tarball=fricas-VERSION.tar.gz
comment:13 Changed 2 years ago by
I see:
upstream_url=https://github.com/fricas/fricas/archive/VERSION.tar.gz
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:14 Changed 2 years ago by
| Status: | needs_review → needs_work |
|---|
comment:15 Changed 2 years ago by
In that case do we need in checksums.ini the following (with updated checksums):
tarball=fricas-VERSION-full.tar.bz2 ... upstream_url=https://sourceforge.net/projects/fricas/files/fricas/VERSION/fricas-VERSION-full.tar.bz2/download
Or are these Sourceforge download urls problematic?
comment:16 Changed 2 years ago by
| Description: | modified (diff) |
|---|
comment:18 Changed 2 years ago by
| Commit: | 086cbf0a5b0a76aa3e2413d884d6f22145ee3119 → b811a1dc6e9c2c790627f9d1d773252209e4ac08 |
|---|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
| b811a1d | update fricas to 1.3.6
|
comment:20 Changed 2 years ago by
| Description: | modified (diff) |
|---|
comment:21 Changed 2 years ago by
| Description: | modified (diff) |
|---|
comment:22 Changed 2 years ago by
| Authors: | Martin Rubey → Frédéric Chapoton |
|---|
comment:23 Changed 2 years ago by
| Reviewers: | → Matthias Koeppe |
|---|---|
| Status: | needs_review → positive_review |
Works for me on macOS.
comment:24 Changed 2 years ago by
| Reviewers: | Matthias Koeppe → Matthias Koeppe, Samuel Lelièvre |
|---|
Success on Debian too:
$ ./sage -i fricas && ./sage -t --optional=fricas,build,dochtml,sage --all All tests passed!
comment:25 Changed 2 years ago by
| Branch: | u/chapoton/27309 → b811a1dc6e9c2c790627f9d1d773252209e4ac08 |
|---|---|
| Resolution: | → fixed |
| Status: | positive_review → closed |
comment:26 Changed 2 years ago by
| Commit: | b811a1dc6e9c2c790627f9d1d773252209e4ac08 |
|---|
I now have problems with "sage -i fricas", which does not seem to be able to find the tarball in the mirrors..
Ticket retargeted after milestone closed (if you don't believe this ticket is appropriate for the Sage 8.8 release please retarget manually)