eocene wrote:
I note the logs still say
date: Tue Apr 28 21:42:28 2015 +0000 summary: BUG_MSG
Are the https changes not playing well with your setup?
Something has broken my hg access. I just noticed that my hg update job has been failing for a while, but I haven't made any changes to it ages. $ hg incoming abort: error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581) Can anyone help? Jeremy
Jeremy wrote:
eocene wrote:
I note the logs still say
date: Tue Apr 28 21:42:28 2015 +0000 summary: BUG_MSG
Are the https changes not playing well with your setup?
Something has broken my hg access. I just noticed that my hg update job has been failing for a while, but I haven't made any changes to it ages.
$ hg incoming abort: error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)
Can anyone help?
I see that I get the same thing if I have cacerts in .hgrc. (It would seem that I normally use hostfingerprints instead. It's been long enough that I don't remember whether I had any good reason for that...)
eocene wrote:
Jeremy wrote:
[...] Something has broken my hg access. I just noticed that my hg update job has been failing for a while, but I haven't made any changes to it ages.
$ hg incoming abort: error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)
Can anyone help?
I see that I get the same thing if I have cacerts in .hgrc.
My .hgrc does not mention cacerts. All it does is set my name and enable the mq and graphlog extensions.
(It would seem that I normally use hostfingerprints instead. It's been long enough that I don't remember whether I had any good reason for that...)
Maybe I should use host fingerprints too. How do you set that up? Regards, Jeremy Henty
participants (2)
-
eocene＠gmx.com -
onepoint＠starurchin.org