You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Testing 0.12 as Docker image, some issues occured to me.
First of all, when using the tagged image, this happens:
$ docker run -v (pwd):/data reuse
/opt/venv/lib/python3.8/site-packages/requests/__init__.py:89: RequestsDependencyWarning: urllib3 (1.25.11) or chardet (4.0.0) doesn't match a supported version!
warnings.warn("urllib3 ({}) or chardet ({}) doesn't match a supported "
# SUMMARY
* Bad licenses:
* Deprecated licenses:
* Licenses without file extension:
* Missing licenses:
* Unused licenses:
* Used licenses: Apache-2.0, CC-BY-SA-4.0, CC0-1.0, GPL-3.0-or-later
* Read errors: 0
* Files with copyright information: 76 / 76
* Files with license information: 76 / 76
Congratulations! Your project is compliant with version 3.0 of the REUSE Specification :-)
When building, some errors occur that might point to the origin of the problem:
$ docker build -t reuse --no-cache .
[...]
Collecting idna<3,>=2.5 (from requests==2.23.0->-r requirements.txt (line 10))
Downloading https://files.pythonhosted.org/packages/a2/38/928ddce2273eaa564f6f50de919327bf3a00f091b5baba8dfa9460f3a8a8/idna-2.10-py2.py3-none-any.whl (58kB)
ERROR: requests 2.23.0 has requirement chardet<4,>=3.0.2, but you'll have chardet 4.0.0 which is incompatible.
Installing collected packages: chardet, binaryornot, boolean.py, MarkupSafe, Jinja2, license-expression, six, python-debian, urllib3, certifi, idna, requests, setuptools, setuptools-scm
Running setup.py install for MarkupSafe: started
Running setup.py install for MarkupSafe: finished with status 'done'
Found existing installation: setuptools 41.2.0
Uninstalling setuptools-41.2.0:
Successfully uninstalled setuptools-41.2.0
[...]
The text was updated successfully, but these errors were encountered:
Testing 0.12 as Docker image, some issues occured to me.
First of all, when using the tagged image, this happens:
When building, some errors occur that might point to the origin of the problem:
The text was updated successfully, but these errors were encountered: