🌐 AI搜索 & 代理 主页
Skip to content

Conversation

@radarhere
Copy link
Collaborator

@radarhere radarhere commented Jun 17, 2022

A few changes.

  1. I went to create a GitHub Actions workflow to demonstrate why my subsequent changes are necessary, but then I thought - why not just add a GitHub Actions workflow here? So that is the first change in this PR.

  2. When I run that, https://github.com/radarhere/trusty/runs/6934202098, I see

E: Package 'python3.5-tk' has no installation candidate

I also get https://github.com/radarhere/trusty/runs/6934257084

E: Unable to locate package python3.6-dev

and https://github.com/radarhere/trusty/runs/6934295021

E: Unable to locate package python3.3-dev

So instead, I've changed Python 3.3, 3.5 and 3.6 to be compiled from source.

  1. I then found that OpenSSL wasn't installing - https://github.com/radarhere/trusty/runs/6934734891

ERROR: cannot verify www.openssl.org's certificate, issued by '/C=US/O=Let's Encrypt/CN=R3':
Issued certificate has expired.
To connect to www.openssl.org insecurely, use `--no-check-certificate'.

Instead, I've added a local copy of openssl, to avoid downloading it altogether. I've also updated OpenSSL to 1.1.1o.

  1. I've updated Python versions

The successful run can be seen at https://github.com/radarhere/trusty/actions/runs/2515112535

@matthew-brett matthew-brett merged commit 76567f2 into matthew-brett:64 Jun 18, 2022
@asenyaev
Copy link

asenyaev commented Jun 24, 2022

Hi guys! It seems this PR changes the Python 3.6 work.

I uses this to test OpenCV Python packages, and anything was fine a week and half ago, but I faced failures in Python 3.6 workflows (link). I even cannot run docker container with the same configuration.

By the way, if to try to find Python 3.6 in a docker image, whereis python command gives an output:

python: /usr/bin/python3.4m /usr/bin/python3.4 /usr/bin/python3.4m-config /usr/bin/python3.4-config /etc/python3.4 /usr/lib/python3.4 /usr/lib/python2.7 /usr/bin/X11/python3.4m /usr/bin/X11/python3.4 /usr/bin/X11/python3.4m-config /usr/bin/X11/python3.4-config /usr/local/lib/python3.4 /usr/include/python3.4m /usr/include/python3.4 /opt/cp39/bin/python3.9 /opt/cp39/bin/python3.9-config /opt/cp310/bin/python3.10-config /opt/cp310/bin/python3.10 /opt/cp35m/bin/python3.5-config /opt/cp35m/bin/python3.5m /opt/cp35m/bin/python3.5 /opt/cp35m/bin/python3.5m-config /opt/cp27mu/bin/python /opt/cp27mu/bin/python2.7-config /opt/cp27mu/bin/python2.7 /opt/cp311/bin/python3.11-config /opt/cp311/bin/python3.11 /opt/cp37m/bin/python3.7m-config /opt/cp37m/bin/python3.7m /opt/cp37m/bin/python3.7-config /opt/cp37m/bin/python3.7 /opt/cp27m/bin/python /opt/cp27m/bin/python2.7-config /opt/cp27m/bin/python2.7 /opt/cp36m/bin/python3.6m-config /opt/cp36m/bin/python3.6-config /opt/cp36m/bin/python3.6m /opt/cp36m/bin/python3.6 /opt/cp33m/bin/python3.3 /opt/cp33m/bin/python3.3m-config /opt/cp33m/bin/python3.3-config /opt/cp33m/bin/python3.3m /opt/cp38/bin/python3.8 /opt/cp38/bin/python3.8-config

I debugged a bit and found out that if I define PYTHON_VERSION=3.6, UNICODE_WIDTH=32 and run ./usr/bin/choose_python.sh script, exit code is 1, but changing only python version (PYTHON_VERSION=3.7), passes the script successfully.

Upd: there is different output of ${py_bin} variable inside bash script.

  • Python 3.6: /usr/bin/python3.6 (which doesn't exist), the correct path is /opt/cp36m/bin/python3.6
  • Python 3.7: /opt/cp37m/bin/python3.7

@radarhere
Copy link
Collaborator Author

Hi. Taking a look at opencv-python, I find that your copy of multibuild is some months behind devel. If I update it to include multi-build/multibuild#433, that changes the default 64-bit test image to focal instead of trusty. That seems to resolve the problem - https://github.com/radarhere/opencv-python/actions/runs/2555591944

So to that end, I've created opencv/opencv-python#684

@asenyaev
Copy link

Thank you!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants