-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
opensuse-tumbleweed: python3 build fails because of openssl #34273
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
|
comment:3
We should probably explicitly install |
comment:5
We should probably get the more detailed configure check from Python: New commits:
|
Commit: |
comment:6
or rather https://github.com/python/cpython/blob/3.10/configure.ac#L5845 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Author: Matthias Koeppe |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits: |
This comment has been minimized.
This comment has been minimized.
comment:16
This fixes it. Let's get it in |
comment:18
I ran the test and got: I am new to this business, and let me ask some naive questions. What was the sign of failure (of
which seems not much different from the excerpt in the ticket description... How do I check if |
comment:19
Thanks for testing! The crucial line in python3's configure output is this:
... which has changed from "no". I should have added a link to a failing build for reference. In https://github.com/sagemath/sage/actions, selecting "CI Linux", there is a completed run for 9.7.beta7, https://github.com/sagemath/sage/actions/runs/2777704621 Selecting "docker / linux (opensuse-tumbleweed, standard)" from the sidebar, one gets to https://github.com/sagemath/sage/runs/7619552751, which shows the end of the failing build of the
What happened there is that Python did not build the Our script https://github.com/sagemath/sage-prod/blob/develop/build/pkgs/python3/spkg-build.in#L120 then checks again for the required modules and exits with an error.
I would say it is not necessary to do more testing than what our build script does. |
comment:20
Replying to @mkoeppe:
Okay. Now I understand the situation better. So the success of the tox test has shown that your branch works well (otherwise python build script would have failed). The relevant github workflow is still running. So let us wait for the result to double-check. The branch itself seems good as far as I can judge. |
comment:21
Another test would be to install It is quite out of my technical reach though. Have you tried it? |
comment:22
Yes, I tested this. If you want to test it, you can just |
comment:23
Replying to @mkoeppe:
Ah, easy. I did it, and the configure worked correctly. |
comment:24
Replying to @kwankyu:
It would take too long to get the result. As this is simply double-checking the correct result I got locally, I will skip it. Then, positive review to this ticket. |
Changed reviewer from https://github.com/mkoeppe/sage/runs/7682738998 to Kwankyu Lee |
comment:25
Thank you! |
Changed branch from u/mkoeppe/opensuse_tumbleweed__python3_build_fails_because_of_openssl to |
Our OpenSUSE system package info leads to the installation of LibreSSL, which is not compatible with the python3 build.
Our configure script does not know that.
We update the distro file and add an additional check to openssl spkg-configure.m4
To test:
tox -e docker-opensuse-tumbleweed-standard -- V=1 python3
CC: @sagetrac-tmonteil @dimpase
Component: packages: standard
Author: Matthias Koeppe
Branch/Commit:
d46f190
Reviewer: Kwankyu Lee
Issue created by migration from https://trac.sagemath.org/ticket/34273
The text was updated successfully, but these errors were encountered: