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 the sage notebook #20047
Comments
This comment has been minimized.
This comment has been minimized.
comment:3
Don't have any more time tonight but I've merged all the things in question and will package soon. Sorry for some extra merge commits, btw. |
This comment has been minimized.
This comment has been minimized.
Branch: u/kcrisman/ticket/20047 |
New commits:
|
Commit: |
This comment has been minimized.
This comment has been minimized.
Author: Karl-Dieter Crisman |
comment:7
I think I did everything correctly, try it out! Be sure to test that the notebook help works etc. |
Changed branch from u/kcrisman/ticket/20047 to u/jdemeyer/ticket/20047 |
comment:10
It doesn't install for me:
|
comment:11
Looks like the dependencies weren't packaged properly or something was included that shouldn't. For future I am guessing we are talking about http://python-future.org/. |
comment:12
|
comment:13
Compared to 0.11.6.1 I think all the dependency upgrade are gratuitous. All that was merged are the PR for the tickets in the summary. Sure it is good to keep on top but I don't think any of them are strictly necessary. |
comment:14
No, no upgrades are required. But I don't know exactly how to (automatically, that is) revert such things. I guess I can do it manually by unpacking a previous tarball. I think that the |
comment:15
I can repackage sagenb-0.11.7 by reverting to |
This comment has been minimized.
This comment has been minimized.
Reviewer: Jeroen Demeyer |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:18
Sorry, still doesn't work. |
comment:19
It does work. However, if you tested an old version of this ticket, you need to delete the previous installation of |
comment:20
Just tested it and SageNB seems to work fine. I did find a serious bug sagemath/sagenb#368 but given that it's also in the current sagenb, it shouldn't block this ticket. |
Changed dependencies from #20030 to none |
Changed branch from u/jdemeyer/ticket/20047 to |
#20030, #20016 and #20094 need a matching change in
sagenb
.Upstream package is at http://sage.ugent.be/www/jdemeyer/sage/sagenb-0.11.7.tar
CC: @kcrisman
Component: packages: standard
Author: Karl-Dieter Crisman
Branch/Commit:
a77ff01
Reviewer: Jeroen Demeyer
Issue created by migration from https://trac.sagemath.org/ticket/20047
The text was updated successfully, but these errors were encountered: