- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 535
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 to pynac-0.7.2 #21963
Comments
This comment has been minimized.
This comment has been minimized.
Branch: u/rws/upgrade_to_pynac_0_7_1 |
Author: Ralf Stephan |
Commit: |
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.
comment:8
Hi ralf, I think that with this pynac the giac spkg must be a dependency. Indeed, I have tried to build sage on a system which have also a version of giac that I am not allowed to remove (and no control of how it was built). In my case it was bernard parisse's binary package installed by root. So this version of libgiac was built with all options and with libao support, but the libao headers were not installed on my system. But now when building sage, pynac found this unexpected giac and the built was broken because of libao problems. Then installing also the giac spkg and the built of sage is going further (although I have not finshed yet) |
comment:9
Thanks for the effort Frédéric. Giac is not a standard package so can be no dependency. Pynac needs to detect such Giac versions that cannot be linked to. As I think this is more tricky we will disable Giac again and reenable in a later version when a solution is found. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:12
Problems in the Singular interface were found. A new version is necessary. |
comment:13
Replying to @rwst:
I don't know the procedure for giac to become a standard package, but it may be the more natural solution. I can see that Francois Bissey is already updating giac often in sage-on-gentoo: About the broken built I can give more details:
and the pynac built broke there:
Now I am testing the following:
so it doesn't seem to be linked with this external giac? |
comment:14
Bloody I inspected After thinking about it I find curious that you have |
comment:15
There are other small minor problems with |
comment:16
That would be awesome. The next release will take some time anyway. |
comment:17
Replying to @kiwifb:
It seems that a broken libtool is the cause: https://lists.fedoraproject.org/pipermail/devel/2010-November/146343.html The other alternative, removing or changing the |
comment:18
So the safe method seems in |
comment:19
Possibly, but I think there is something broken in the system where the problem was shown. Applications and the If it doesn't currently work that way, whoever built the package logic had it wrong. |
comment:21
Replying to @frederichan-IMJPRG:
I am not surprised.
ABI problem, yes that's hard.
That looks a good idea to me.
I am the one who actually said it should happen that way at the sage binary package level. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:26
Dependency needs to include |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Reviewer: François Bissey |
This comment has been minimized.
This comment has been minimized.
comment:29
The bot will take care of testing debian/ubuntu I guess. But yes one of the next step will be more robust detection of a working |
comment:30
Thanks. Unfortunately I didn't switch on the Giac support in Pynac in this ticket so anything Giac (with it being standard package now) will have to wait for the next Pynac release. |
comment:31
Replying to @rwst:
That's OK. In my opinion there are two more things to do before switching |
Changed branch from u/rws/upgrade_to_pynac_0_7_1 to |
Pynac-0.7.2:
Giac GCD if available); this fixes Infinite loop in gcd() via pynac-0.2.1 #10284; it means that Singular is now another Pynac dependencyreenable unconditional use of Giac if available (Enable Pynac's Giac support #21885)Tarball: https://github.com/pynac/pynac/releases/download/pynac-0.7.2/pynac-0.7.2.tar.bz2
Needs to specifically tested on Debian/Ubuntu because of #21885.Component: packages: standard
Author: Ralf Stephan
Branch/Commit:
6130c95
Reviewer: François Bissey
Issue created by migration from https://trac.sagemath.org/ticket/21963
The text was updated successfully, but these errors were encountered: