Re: invalid certificate chain during port-fetch

2019-12-28 Thread Ryan Schmidt
On Dec 28, 2019, at 14:33, René J.V. Bertin wrote: > On Saturday December 28 2019 14:10:29 Ryan Schmidt wrote: > >>> but don't understand why the fallback doesn't work on Mac. Maybe a >>> different exception is raised there? >>> >>> Anyway, I think the fallback makes sense in this kind of

Re: invalid certificate chain during port-fetch

2019-12-28 Thread René J . V . Bertin
On Saturday December 28 2019 14:10:29 Ryan Schmidt wrote: >> but don't understand why the fallback doesn't work on Mac. Maybe a different >> exception is raised there? >> >> Anyway, I think the fallback makes sense in this kind of situation, and it >> should handle bootstrap errors gracefully.

Re: invalid certificate chain during port-fetch

2019-12-28 Thread Ryan Schmidt
On Dec 28, 2019, at 02:57, René J.V. Bertin wrote: > On Friday December 27 2019 21:32:26 Ryan Schmidt wrote: > > Hi, > > Thanks for looking into this! > >> You didn't mention what instructions you're referring to > > Only because there are several threads about this issue on S-E and I was

Re: Is it possible to use cmake and python portgroup together?

2019-12-28 Thread Joshua Root
On 2019-12-28 23:24 , Ruben Di Battista wrote: > I’m revamping the ports of PySide2 and FreeCad with all the > dependencies, and I’d like to build Shiboken2 with cmake (in order to > provide the config file), but still I need the creation of the various > python ports etc… Can I use both? Or do I

Is it possible to use cmake and python portgroup together?

2019-12-28 Thread Ruben Di Battista
I’m revamping the ports of PySide2 and FreeCad with all the dependencies, and I’d like to build Shiboken2 with cmake (in order to provide the config file), but still I need the creation of the various python ports etc… Can I use both? Or do I need to replicate the stub port management done in

Re: invalid certificate chain during port-fetch

2019-12-28 Thread René J . V . Bertin
On Friday December 27 2019 21:32:26 Ryan Schmidt wrote: Hi, Thanks for looking into this! >You didn't mention what instructions you're referring to Only because there are several threads about this issue on S-E and I was on a different machine when I wrote to the ML.. And you must have seen