Changeset View
Changeset View
Standalone View
Standalone View
requirements.txt
vcversioner | vcversioner | ||||
click | click | ||||
file-magic | python-magic >= 0.4.13 | ||||
anlambert: I would keep file_magic by default here as python-magic is not packaged in Debian stretch… | |||||
Done Inline ActionsThe problem is that the python-magic in Stretch has a bug that affects us (T861). vlorentz: The problem is that the python-magic in Stretch has a bug that affects us (T861). | |||||
Not Done Inline ActionsMight be related to a bug I also observed in the webapp, I used a dirty workaround that seems to do the job (see https://forge.softwareheritage.org/source/swh-web/browse/master/swh/web/browse/utils.py$71). anlambert: Might be related to a bug I also observed in the webapp, I used a dirty workaround that seems… | |||||
Done Inline ActionsI don't thing so, the bug T861 always happens for a given content. vlorentz: I don't thing so, the bug T861 always happens for a given content. | |||||
Not Done Inline ActionsEffectively, so backporting the python3-magic deb package from testing to stretch is required before production deployment. I could also benefit from it in the webapp and remove my dirty hack. anlambert: Effectively, so backporting the python3-magic deb package from testing to stretch is required… | |||||
pyld | pyld | ||||
xmltodict | xmltodict |
I would keep file_magic by default here as python-magic is not packaged in Debian stretch (python3-magic deb package corresponds to file_magic).
Otherwise, a backport package for python-magic must be created for successfull deployment to production environment