Skip to content
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

Closed
mantepse opened this issue Aug 31, 2016 · 31 comments
Closed

Update FriCAS to 1.3.2 (current) #21377

mantepse opened this issue Aug 31, 2016 · 31 comments

Comments

@mantepse
Copy link
Contributor

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

@mantepse
Copy link
Contributor Author

Changed keywords from none to FriCAS

@mantepse

This comment has been minimized.

@mantepse mantepse changed the title Update FriCAS to 1.3.0 (current) Update FriCAS to 1.3.1 (current) Feb 16, 2017
@mantepse mantepse modified the milestones: sage-7.4, sage-7.6 Feb 16, 2017
@fchapoton
Copy link
Contributor

Commit: d8be4f4

@fchapoton
Copy link
Contributor

Branch: u/chapoton/21377

@fchapoton
Copy link
Contributor

comment:2

I made a branch, removing one patch that failed to apply. Maybe this patch must be kept.


New commits:

d8be4f4trac 21377 update fricas

@fchapoton fchapoton modified the milestones: sage-7.6, sage-8.1 Sep 5, 2017
@mantepse
Copy link
Contributor Author

mantepse commented Sep 5, 2017

comment:3

Note that it's meanwhile 1.3.2. No idea whether there are significant changes.

@fchapoton

This comment has been minimized.

@fchapoton fchapoton changed the title Update FriCAS to 1.3.1 (current) Update FriCAS to 1.3.2 (current) Sep 5, 2017
@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Sep 5, 2017

Changed commit from d8be4f4 to 8aa26de

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Sep 5, 2017

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

8aa26deupdate fricas to 1.3.2

@fchapoton
Copy link
Contributor

comment:7

This installs correctly and passes the "# optional fricas" doctests. Can someone double check please ?

@mantepse
Copy link
Contributor Author

mantepse commented Sep 6, 2017

comment:8

I am currently compiling!

@mantepse
Copy link
Contributor Author

mantepse commented Sep 6, 2017

comment:9

Hm, when trying to do sage -i fricas with this ticket, I get an error saying that it couldn't be downloaded...

How should I try this?

@mantepse
Copy link
Contributor Author

mantepse commented Sep 6, 2017

comment:10

I think I figured it out: download and put it into upstream

@fchapoton
Copy link
Contributor

comment:11

you need to put yourself the tar file in $SAGEHOME/upstream

@mantepse
Copy link
Contributor Author

mantepse commented Sep 6, 2017

comment:12

I actually have most tests failing now, because of bad indentation. For example:

File "src/sage/interfaces/fricas.py", line 1104, in sage.interfaces.fricas.FriCASElement._sage_
Failed example:
    a = fricas('(1 + sqrt(2))^5'); a                              # optional - fricas
Expected:
       +-+
    29\|2  + 41
Got:
    +-+
    29 \|2  + 41

However, I cannot tell whether the tests passed before the switch to FriCAS 1.3.2.

@hemmecke
Copy link
Contributor

hemmecke commented Sep 6, 2017

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.

@mantepse
Copy link
Contributor Author

mantepse commented Sep 9, 2017

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.

@mantepse
Copy link
Contributor Author

comment:15

I can confirm it works and fixes part of #23782

@mantepse
Copy link
Contributor Author

Author: Frédéric Chapoton

@mantepse
Copy link
Contributor Author

Reviewer: Martin Rubey

@jdemeyer
Copy link

Replying to @mantepse:

(with ads, but automatic download after a few seconds)

I'm not sure that this will be acceptable for the release manager.

@mantepse
Copy link
Contributor Author

comment:18

Replying to @jdemeyer:

Replying to @mantepse:

(with ads, but automatic download after a few seconds)

I'm not sure that this will be acceptable for the release manager.

Are you saying that sourceforge is not acceptable anymore?

@rwst
Copy link

rwst commented Sep 14, 2017

comment:19

Replying to @mantepse:

Are you saying that sourceforge is not acceptable anymore?

https://en.wikipedia.org/wiki/SourceForge#Country_restrictions

They seem to at least willing to improve the site that declined after 2012:
https://www.reddit.com/r/sysadmin/comments/4n3e1s/the_state_of_sourceforge_since_its_acquisition_in/

@mantepse
Copy link
Contributor Author

comment:20

Is https://github.com/fricas/fricas acceptable? But I have no idea how to package from there.

@hemmecke
Copy link
Contributor

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.)
Ask on https://groups.google.com/forum/#!forum/fricas-devel how one can package from the source tree.

@mantepse
Copy link
Contributor Author

comment:22

OK, I shot myself into the foot here. No, I'm sure we should want the sourceforge version here. PLEASE!

@rwst
Copy link

rwst commented Sep 14, 2017

comment:23

Replying to @hemmecke:

Note that https://github.com/fricas/fricas is a only source repository.

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.

@jdemeyer
Copy link

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.

@vbraun
Copy link
Member

vbraun commented Sep 15, 2017

Changed branch from u/chapoton/21377 to 8aa26de

@mantepse
Copy link
Contributor Author

comment:26

This is wonderful, wonderful, wonderful! Thank you!

@mantepse
Copy link
Contributor Author

Changed commit from 8aa26de to none

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants