Latest upstream release: 2020.4.5.1 Current version/release in rawhide: 2018.10.15-8.fc32 URL: https://pypi.python.org/pypi/certifi Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/7995/ Also, please enable upstream release monitoring status at https://src.fedoraproject.org/rpms/python-certifi .
Our certifi is basically patched out. So I don't ruch to do this update. Feel free to beta me to it.
I'm not sure what you mean by "patched out", but it's detected as old version by mitmproxy which declares dependency on >=2019.9.11, but finds 2018.10.15 and complains. I'd prefer to avoid patching version requirements if possible.
By patched out I mean that in reality whatever version of certifi we have, it gives /etc/pki/tls/certs/ca-bundle.crt. If we update it, it will still do the same and the only difference will be the version number. > mitmproxy which declares dependency on >=2019.9.11 Any idea what is the reason fo them to do this? > I'd prefer to avoid patching Understood. Let's update it then. The patch needs to be updated as well.
https://src.fedoraproject.org/rpms/python-certifi/pull-request/4