Open pombredanne opened 3 years ago
The trouble was caused by PyYAML. The version in https://raw.githubusercontent.com/nexB/scancode-toolkit/v21.2.9/requirements.txt is 3.12
and that can only be installed on python 3.6.
https://raw.githubusercontent.com/nexB/scancode-toolkit/v21.2.9/requirements.txt
PyYAML==3.12
If you want to use python:3.9.1 you can use the following setup with a requirements.txt
.
I created a DockerFile based on python:buster
FROM python:buster
RUN /usr/local/bin/python -m pip install --upgrade pip
RUN pip install scancode-toolkit[full]
RUN pip freeze
Copy - pasted the requirements output to a file and now using it to install pinned versions of the dependencies.
FROM python:buster
RUN /usr/local/bin/python -m pip install --upgrade pip
COPY docker/requirements.txt /app/requirements.txt
RUN pip install scancode-toolkit[full] -c /app/requirements.txt
Now the PyYAML has version 5.4.1.
PyYAML==5.4.1
Attached is the requirements.txt file. requirements.txt
@JeroenKnoops thanks... that's a relatively easy one to fix as https://github.com/nexB/saneyaml/ is the one that has the direct dep on PyYAML and using a wider range of versions should be a no brainer ( and a good time to rev up saneyaml too)
I think this issue should be closed
See https://github.com/philips-software/license-scanner/blob/b590ea0985c83daab0a913c1d3c4e2eb34a87d9f/docker/requirements.txt
@JeroenKnoops commented yesterday https://github.com/oss-review-toolkit/ort/pull/3613#issuecomment-777057402
The task consist in reviewing the requirements and why the standard ones were not working there.