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.2 (current) #21377
Comments
Changed keywords from none to FriCAS |
This comment has been minimized.
This comment has been minimized.
Commit: |
Branch: u/chapoton/21377 |
comment:2
I made a branch, removing one patch that failed to apply. Maybe this patch must be kept. New commits:
|
comment:3
Note that it's meanwhile 1.3.2. No idea whether there are significant changes. |
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:
|
comment:7
This installs correctly and passes the "# optional fricas" doctests. Can someone double check please ? |
comment:8
I am currently compiling! |
comment:9
Hm, when trying to do How should I try this? |
comment:10
I think I figured it out: download and put it into |
comment:11
you need to put yourself the tar file in $SAGEHOME/upstream |
comment:12
I actually have most tests failing now, because of bad indentation. For example:
However, I cannot tell whether the tests passed before the switch to FriCAS 1.3.2. |
comment:13
I guess the "+-+" part got a bit shifted when you copied the result into the ticket. The difference is the space after 29. This has recently been added. |
comment:14
I am not sure how to proceed - on the one hand, I think it makes sense to merge this, because I do not know what made the output break (I do not mean the additional space) - it was broken before the upgrade, too. Frederic, can you confirm that the tests pass on your computer? It's strange that the space introduced in FriCAS would not show up on your system. |
comment:15
I can confirm it works and fixes part of #23782 |
Author: Frédéric Chapoton |
Reviewer: Martin Rubey |
Replying to @mantepse:
I'm not sure that this will be acceptable for the release manager. |
comment:19
Replying to @mantepse:
https://en.wikipedia.org/wiki/SourceForge#Country_restrictions They seem to at least willing to improve the site that declined after 2012: |
comment:20
Is https://github.com/fricas/fricas acceptable? But I have no idea how to package from there. |
comment:21
Note that https://github.com/fricas/fricas is a only source repository. As far as I know, the release tarball is not identical to the git version that is tagged with the version number. The release tarball contains some precompiled stuff. (I'm not 100% sure since I compile myself from source.) |
comment:22
OK, I shot myself into the foot here. No, I'm sure we should want the sourceforge version here. PLEASE! |
comment:23
Replying to @hemmecke:
So is https://github.com/pynac/pynac. The maintainer just uploads a suitable tarball when doing a release. This means you need to do at least one release in the repo. |
comment:24
I am not the release manager. I am only saying that it might be a problem for the release manager, just to save you some time before the release manager looks at this ticket. |
Changed branch from u/chapoton/21377 to |
comment:26
This is wonderful, wonderful, wonderful! Thank you! |
Changed commit from |
subject says it all, see http://fricas.sourceforge.net/
https://groups.google.com/forum/#!topic/fricas-devel/jjn0P3H0N8g
I assume that this version needs less patching.
Upstream source tarball:
https://sourceforge.net/projects/fricas/files/fricas/1.3.2/fricas-1.3.2-full.tar.bz2/download
(with ads, but automatic download after a few seconds)
CC: @dkrenn @mantepse @hemmecke @rwst
Component: packages: experimental
Keywords: FriCAS
Author: Frédéric Chapoton
Branch:
8aa26de
Reviewer: Martin Rubey
Issue created by migration from https://trac.sagemath.org/ticket/21377
The text was updated successfully, but these errors were encountered: