-
-
Notifications
You must be signed in to change notification settings - Fork 480
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: Maxima 5.44.0 #30063
Comments
Dependencies: #22191 |
Commit: |
comment:3
Patches need to be removed or updated. Last 10 new commits:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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:8
Removing
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:10
On macOS,
|
comment:11
This is
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:13
Builds OK now on macOS. Haven't tested anything else |
comment:14
Tests run at https://github.com/mkoeppe/sage/actions/runs/174422230 |
comment:15
Replying to @sagetrac-git:
don't they have an option not to build docs? |
comment:16
Unfortunately they don't. |
comment:17
These are the test failures I get downstream (using system maxima):
The first one needs a readjustment of the number of removed lines in https://github.com/sagemath/sagetrac-mirror/blob/develop/src/sage/interfaces/maxima_abstract.py#n183 The ones in The other two seem harmless. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:19
Replying to @antonio-rojas:
I have fixed the first one by a method that I hope to be more robust. |
comment:20
Replying to @antonio-rojas:
This is now https://sourceforge.net/p/maxima/bugs/3643/ |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Reviewer: Emmanuel Charpentier |
comment:44
Adding my name (as I should have initially...), but keeping it at |
comment:45
Replying to @mkoeppe:
I agree. But |
comment:46
Replying to @seblabbe:
Damn ! I keep forgetting this. Old age ? Incipient Alzheimer's ? Done, anyway. |
Changed reviewer from Emmanuel Charpentier to Emmanuel Charpentier, github.com/mkoeppe/sage/actions/runs/208788708, github.com/mkoeppe/sage/actions/runs/208788707 |
comment:48
All clean on debian and ubuntu, waiting for more results |
comment:49
Replying to @sagetrac-tmonteil:
Nice solution!
Would it be worth finding out when this regression was introduced in Maxima and try to add a patch to fix it? |
comment:50
Replying to @mkoeppe:
I would change the default ./configure outcomes of not finding gcc, gfortran, gmp, etc to Error. |
comment:51
Replying to @pjbruin:
It goes far beyond my skills, as i never wrote a single line of lisp. The best i can do is to report the regression upstream and follow its evolution to untag the corresponding doctest once it is fixed. I am not sure this regression should prevent us to update Maxima. |
comment:52
You can also open a new ticket for tracking that upstream report so we don't lose it (as opposed to only noticing the doctest change if Maxima fixes this, if anyone even tests the "known bug" doctests much). I agree that if there is significant improvement introduced, then in practice we have often upgraded on a utilitarian view of things. |
comment:53
Replying to @kcrisman:
Follow-up for tracking this issue: #30389 |
comment:54
Replying to @kcrisman:
Possibly related : #30379 and the fossil tickets mentioned therein... |
comment:55
Replying to @mkoeppe:
FWIW, worked again in upgrading to 9.2.beta9. |
Changed reviewer from Emmanuel Charpentier, github.com/mkoeppe/sage/actions/runs/208788708, github.com/mkoeppe/sage/actions/runs/208788707 to Emmanuel Charpentier, Matthias Koeppe |
Changed keywords from none to upgrade, maxima |
This comment has been minimized.
This comment has been minimized.
Changed branch from u/tmonteil/upgrade_maxima_to_5_44_0 to |
Changed commit from |
Upstream tarball: see
upstream_url
inbuild/pkgs/maxima/checksums.ini
.Previous update: #26625 Update maxima to 5.42.2
Follow-up bug: #30389
Depends on #22191
CC: @dimpase @kiwifb @timokau @saraedum @slel @antonio-rojas @kcrisman @nbruin @paulmasson
Component: packages: standard
Keywords: upgrade, maxima
Author: Matthias Koeppe, Thierry Monteil
Branch:
21e2fea
Reviewer: Emmanuel Charpentier, Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/30063
The text was updated successfully, but these errors were encountered: