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
The following irritating message is produced whenever urllib3 is invoked, most notably while performing an emerge --sync:
/usr/lib/python3.10/site-packages/urllib3/__init__.py:34: NotOpenSSLWarning: urllib3 v2.0 only supports OpenSSL 1.1.1+, currently the 'ssl' module is compiled with 'LibreSSL 3.8.0'. See: https://github.com/urllib3/urllib3/issues/3020
The message references urllib3/urllib3#3020 as users of MacOS were getting a similar message due to their ssl modules being compiled with LibreSSL also, albeit much older versions (2.8.3).
Although this is only a warning and software that depends on the library still seems to work as expected, I was wondering if this should be addressed at all, whether we should simply ignore the warning entirely, suppress it, upgrade any particular packages, try to patch it, etc.
Thanks
The text was updated successfully, but these errors were encountered:
The warning was added by upstream as a compromise to allow LibreSSL to work at all, before this it was an explicit error. To drop the warning the package would have to have a non-upstreamable patch that would need to be rebased every time that ::gentoo modifies the ebuild. Given that I have been ignoring the warning, it doesn't cause any harm other than console spam that I have noticed.
The following irritating message is produced whenever
urllib3
is invoked, most notably while performing anemerge --sync
:The message references urllib3/urllib3#3020 as users of MacOS were getting a similar message due to their ssl modules being compiled with LibreSSL also, albeit much older versions (2.8.3).
Although this is only a warning and software that depends on the library still seems to work as expected, I was wondering if this should be addressed at all, whether we should simply ignore the warning entirely, suppress it, upgrade any particular packages, try to patch it, etc.
Thanks
The text was updated successfully, but these errors were encountered: