Hi there. I am in the unfortunate situation where the system I am using has a firewall to the outside with a self-signed certificate. It is beyond my control.
I've managed to by-pass this issue in many other projects whose env is managed by conda by simply catting the offending certificate to the .../site-packages/certifi/cacert.pem used by the code (twine would be an example)
I've had no such luck with hatch.
Part of the problem is that I do not know which cacert it's looking at, and I have not found a way to set a debug or verbose flag that shows me exacly what is making the call that fails.
I've individuated 3 cacert.pem files in the conda environment using find, and catting the self signed certificate has not solved the issue, so I am assuming it's looking somewhere else.
Can anyone help?
Thanx
Hi there. I am in the unfortunate situation where the system I am using has a firewall to the outside with a self-signed certificate. It is beyond my control.
I've managed to by-pass this issue in many other projects whose env is managed by conda by simply catting the offending certificate to the .../site-packages/certifi/cacert.pem used by the code (twine would be an example)
I've had no such luck with hatch.
Part of the problem is that I do not know which cacert it's looking at, and I have not found a way to set a debug or verbose flag that shows me exacly what is making the call that fails.
I've individuated 3 cacert.pem files in the conda environment using find, and catting the self signed certificate has not solved the issue, so I am assuming it's looking somewhere else.
Can anyone help?
Thanx